headers
Peter Apian-Bennewitz | 4 Feb 2009 23:33
Picon
Favicon

Via: rport rewriting in siproxd 0.7.1

Hi,

problem:
login with twinkle via siproxd to callcentric.com fails with "network 
failure" on callcentric's side. Running twinkle without siproxd works.

SIP provider's answer:
callcentric's support says siproxd is not following RFC3581 regarding 
the rport parameter. As far as I understand RFC3581 this is correct, 
even if the Via header in question is only the second Via (not the 
topmost) that callcentric's server sees.

data:
The header of the outgoing REQUEST SIP packet with the MD5 hash, leaving 
my gateway, after siproxd processing, looks like:

    Via: SIP/2.0/UDP
    84.56.215.75:5060;branch=z9hG4bKb508ec9eb039c974bd1cccba6117cc33
    Via: SIP/2.0/UDP 192.168.0.11;rport;branch=z9hG4bKcykecwos
    From: <sip:XXX@...>;tag=mkqua
    To: <sip:XXX@...>
    Call-ID: tmvgrhodrsbtzae <at> mylocalname
    CSeq: 935 REGISTER
    Contact: <sip:XXX@...>
    Proxy-Authorization: Digest username="XXX", realm="callcentric.com",
    nonce="88a438c17e962decdb3091df2c300169", uri="sip:callcentric.com",
    response="XXXX", algorithm=MD5
    Allow: INVITE
    Allow: ACK
    Allow: BYE
(Continue reading)

Permalink | Reply | 1 comment |
headers
Thomas Ries | 6 Feb 2009 17:53
Picon

Re: Via: rport rewriting in siproxd 0.7.1

Hello Peter,

I will have a look at it when I get some time, thanks for reporting.

Currently the use_rport configuration parameter does only tell siproxd
to add an rport header, if does not affect processing of existing
headers. Siproxd does (currently) not honor an existing rport header.

So let's put RFC3581 onto the TODO list...

Regards,
/Thomas

On  4 Feb, Peter Apian-Bennewitz wrote:
> Hi,
> 
> problem:
> login with twinkle via siproxd to callcentric.com fails with "network 
> failure" on callcentric's side. Running twinkle without siproxd works.
> 
> SIP provider's answer:
> callcentric's support says siproxd is not following RFC3581 regarding 
> the rport parameter. As far as I understand RFC3581 this is correct, 
> even if the Via header in question is only the second Via (not the 
> topmost) that callcentric's server sees.
> 
> data:
> The header of the outgoing REQUEST SIP packet with the MD5 hash,
> leaving my gateway, after siproxd processing, looks like:
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tamer Higazi | 9 Feb 2009 18:44

problem getting asterisk behind NAT to run with sipproxd

Hi people!
Asterisk PBX (version 1.6.5): I have Asterisk behind a NAT (192.168.1.2)
SIP Phone: A client behind NAT (192.168.1.3)
Softphone: One other client somewhere in the internet (also behind an NAT).

they want to speak with each other, and if they do, there is no sound.

if softphone in the internet is no more behind a NAT router, it can hear
SIP Phone but SIP Phone is not able to hear Softphone.

siproxd is installed on the same machine where the asterisk PBX is
installed, and I don't know how to configure it properly as well how the
sip.conf of the asterisk PBX should have to look like.

For any support I would thank you gladly.

Tamer

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
Permalink | Reply | 1 comment |
headers
Thomas Ries | 9 Feb 2009 20:32
Picon

Re: problem getting asterisk behind NAT to run with sipproxd

Likely you are trying to use siproxd in a way it is not intended for.

Siproxd can be used to masquerade asterisk as UAC (asterist connected to
an external SIP provider - "SIP Trunk") but not 
See the siproxd online documentation chapter 7.5 "Masquerading an
Asterisk box".

What you describe would be some kind of "far side NAT traversal", having
Asterisk as SIP registrar and a remote UA isolated via NAT; this does
not work with siproxd. You can place siproxd to the remote UA
(softphone) in a "Standard Scenario" or "siproxd in front of NAT router"
scenario.

Regards,
/Thomas

On  9 Feb, Tamer Higazi wrote:
> Hi people!
> Asterisk PBX (version 1.6.5): I have Asterisk behind a NAT (192.168.1.2)
> SIP Phone: A client behind NAT (192.168.1.3)
> Softphone: One other client somewhere in the internet (also behind an
> NAT).
> 
> they want to speak with each other, and if they do, there is no sound.
> 
> if softphone in the internet is no more behind a NAT router, it can
> hear SIP Phone but SIP Phone is not able to hear Softphone.
> 
> siproxd is installed on the same machine where the asterisk PBX is
> installed, and I don't know how to configure it properly as well how
(Continue reading)

Permalink | Reply | 0 comments |

Gmane