netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: More nf_conntrack_sip questions
Date: Fri, 05 Dec 2008 19:08:09 +0100	[thread overview]
Message-ID: <49396E09.9070607@trash.net> (raw)
In-Reply-To: <49396DDD.9080308@trash.net>

Patrick McHardy wrote:
> Philip Prindeville wrote:
>> Patrick McHardy wrote:
>>> Philip Prindeville wrote:
>>>> I did a little investigation into my one-way voice issue, and 
>>>> noticed that if I don't do voice-menus (i.e. where the Asterisk box 
>>>> itself generates the first outbound INVITE, then passes-through the 
>>>> 2nd INVITE once a handset picks up) then I get two-way voice (i.e. 
>>>> with sending the call directly to the phone).  (In this topology, my 
>>>> Asterisk box is also my firewall/NATting router...)
>>>>
>>>> If I enable the voice menus in the inbound dialplan, however, it can 
>>>> hear the voice menus, but not the called-party when they pick up 
>>>> their phone (extension).
>>>>
>>>> So someone (either the SIP conntrack module on the Asterisk border 
>>>> firewall or else the SBC at the ILEC) is failing to look into the 
>>>> 2nd INVITE (i.e. we're not rewriting it properly as it goes by, or 
>>>> the SBC is failing to see it).
>>>
>>>
>>> What module options are you using for the SIP helper and how is call
>>> setup in asterisk configured (directrtpsetup, canreinvite, ...)?
>>>
>>
>> For the PSTN's switch:
>>
>>  CanReinvite  : Yes
> 
> I vaguely recall some problem in the implementation of this feature,
> something with missing bridging of the RTP streams that was still
> necessary under some circumstances. Might be worth to try turning
> it off.

Actually I think it was directrtpsetup. Still worth trying though.

> What about the module options?

  reply	other threads:[~2008-12-05 18:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 22:36 More nf_conntrack_sip questions Philip Prindeville
2008-12-05 16:21 ` Patrick McHardy
2008-12-05 18:00   ` Philip Prindeville
2008-12-05 18:07     ` Patrick McHardy
2008-12-05 18:08       ` Patrick McHardy [this message]
2008-12-05 18:10       ` Philip Prindeville
2008-12-05 18:13         ` Patrick McHardy
2008-12-05 18:16           ` Philip Prindeville
2008-12-05 18:19             ` Patrick McHardy
2008-12-05 18:32               ` Philip Prindeville
2008-12-05 18:39                 ` Patrick McHardy
2008-12-07  0:31                   ` Philip Prindeville
2008-12-07 16:06                     ` Patrick McHardy
2008-12-08  0:28                       ` Philip Prindeville

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=49396E09.9070607@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=philipp_subx@redfish-solutions.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).