Thanks Brian,

 

That’s enabled it to register and place calls.

 

Craig

 

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian West
Sent: Sunday, 24 August 2008 12:01 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Registration issue with Polycom

 

The problem is the Polycom is behind NAT.  Right?  It has nothing to do with the contact header... 

 

Add this to your sofia profile:

 

<param name="NDLB-force-rport" value="true"/>

 

/b

 

 

On Aug 23, 2008, at 5:01 AM, Craig Guy wrote:



Hi Brian,

 

I suspect that FS may not like the contact header in the sip REGISTER request.  The source port of the REGISTER is 5076, the contact header also specifies port 5076, and there is no mention of port 5060 anywhere in the REGISTER message itself.  Note that the Polycom has appended ‘methods=’ to the contact header.  I’m not familiar enough with the RFC to know if this is valid for the contact header, but I won’t rule out that this additional stuff on the contact header is causing FS to discard it and use port 5060 instead of the requested 5076.

 

Neither of my Snom or Billion contact headers are formatted this way.  I might see if I can find a Polycom firmware update and see if that changes the header. 

 

Craig

 

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian West
Sent: Saturday, 23 August 2008 9:52 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Registration issue with Polycom

 

I'm going to gues that nat is involved... and the polycom doesn't rfc3581 so you'll need to turn on NDLB-force-rport on the sip profile so we respond on the port we received the initial inbound registration from.  Notice it comes in from 5076.. yet we 401 it to 5060....   This is the reason the polycom is number two on my list.

 

/b

 

On Aug 22, 2008, at 8:43 PM, Craig Guy wrote:




Hi,

 

I’ve got an issue trying to register a Polycom IP320 against FS 1.0.1, as below the Polycom is coming from and registering with a contact port 5076, however FS is sending the 401 to port 5060.  Any ideas?  I have a Snom registering successfully as 1000 from behind a different NAT.  Any ideas?

 

#

U 203.23.223.109:5076 -> 4.53.88.29:5060

REGISTER sip:4.53.88.29 SIP/2.0.

Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bK7db8749a8ECDE4D3.

From: "Craig Guy" <sip:1001@4.53.88.29>;tag=914B0517-5EB6FA00.

CSeq: 1 REGISTER.

Contact: <sip:1001@203.23.223.109:5076>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER".

User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.2.0049.

Max-Forwards: 70.

Expires: 3600.

Content-Length: 0.

.

 

#

U 4.53.88.29:5060 -> 203.23.223.109:5060

SIP/2.0 401 Unauthorized.

Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bK7db8749a8ECDE4D3;received=203.23.223.109.

From: "Craig Guy" <sip:1001@4.53.88.29>;tag=914B0517-5EB6FA00.

To: <sip:1001@4.53.88.29>;tag=7U95e600jSH5e.

CSeq: 1 REGISTER.

User-Agent: FreeSWITCH-mod_sofia/1.0.1-exported.

Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH.

Supported: 100rel, timer, precondition, path, replaces.

WWW-Authenticate: Digest realm="4.53.88.29", nonce="b59a58b1-bdc6-4487-b346-12838168039d", algorithm=MD5, qop="auth".

Content-Length: 0.

.

 

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

 

Brian West

sip:brian@freeswitch.org