From: Juergen Schmidt <abcdmail@freenet.de>
To: netfilter@vger.kernel.org
Subject: Re: sip helper doesn't match on calls to myself
Date: Thu, 10 Nov 2016 19:27:59 +0100 [thread overview]
Message-ID: <a2fd4690-63c9-36a9-d5eb-8d00ae79b149@freenet.de> (raw)
In-Reply-To: <a3cf2e4b-1345-1efc-b211-5fea64438baf@freenet.de>
On 11/09/2016 at 05:01 PM, Juergen Schmidt wrote:
> Hello!
>
> I've got the following problem: If I'm calling myself, the incoming call
> isn't matched by the sip helper rules, but the rules w/o sip helper. I
> would have expected, that both calls are matched by the sip helper rules.
>
>
> In detail:
>
> Given is an asterisk server, one extension (C610 IP with 3 phones, which
> can handle 2 lines at the same time) and a trunk to the provider.
>
> The extension calls the own number, which provides the following scenario:
>
> outgoing call: extension -> asterisk -> provider
>
> and
>
> incoming call: provider -> asterisk -> extension
>
>
> *Important*: the provider uses independent media servers. This means:
> the signaling server and the media servers have different IP addresses.
>
Addition:
The problem *only* happens if at the same time a third (outgoing) call
is initiated (via ring group) - which is *not answered* but closed at
the moment the call is accepted internally.
If the third (-> outgoing) call via ring group is omitted, things work
as expected.
Calls in detail:
outgoing call: extension -> asterisk -> provider
incoming call: provider -> asterisk -> extension
outgoing call* via ring group: asterisk -> provider -> ext. destination
answer the incoming call
outgoing call* is exited.
* triggered by incoming call
Thanks,
Juergen
next prev parent reply other threads:[~2016-11-10 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 16:01 sip helper doesn't match on calls to myself Juergen Schmidt
2016-11-10 18:27 ` Juergen Schmidt [this message]
2016-11-11 13:17 ` Juergen Schmidt
-- strict thread matches above, loose matches on Subject: below --
2016-11-08 19:01 Juergen Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a2fd4690-63c9-36a9-d5eb-8d00ae79b149@freenet.de \
--to=abcdmail@freenet.de \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.