VIA header not being correctly set

[seanwg]

Hi,

Recently got a Nokia E65 phone. I have VoIP working perfectly with it with a number of Sip Servers.

I am attempting to get the E65 to register to a Lucent/Alcatel IMS. The E65 is being NAT'd router, and succesfully detects its external IP. I can see this in the Contact/SDP info in the initial Invite.

It is however incorrectly (from what I understand of the VIA header) setting the VIA header.

The E65s External IP & Port after NAT is:
Z:48374

The E65s Internal IP & Port
10.0.69.65:5060

Reading the RFCs - the VIA header on a Register should look like:

Via: SIP/2.0/UDP Z:48380;rport;branch=...

It doesn't however. Looking at the REGISTER request, it has:

Via: SIP/2.0/UDP 10.0.69.65:5060;branch=z9hG4bK7ksvl47qi0jvnnao94mqbab;rport

Is this correct?

I've looked at the REGISTER requests from a couple of other phones, and they all set the Via header correctly after doing with a NAT? Or is there an option to not include the VIA option in there?


User Datagram Protocol, Src Port: 48374 (48374), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: REGISTER sip:sip.X.Y SIP/2.0
Message Header
Via: SIP/2.0/UDP 10.0.69.65:5060;branch=z9hG4bK7ksvl47qi0jvnnao94mqbab;rport
From: <sip:+X@sip.X.Y>;tag=k07kibbp69hc7g560dub
To: <sip:+X@sip.X.Y>
Contact: <sip:+X@Z:48374>;expires=3600
CSeq: 1319 REGISTER
Call-ID: -GJ9bu0loIcnTMdYk3e9hcQbZzQIBa
Supported: sec-agree
User-Agent: Nokia RM-208 1.0633.18.01
Max-Forwards: 70
Content-Length: 0
sean@Sean ~ %

[nly]

This has been changed in later software packages. When the SIP proxy supports RFC3581 (the rport parameter), the value of Via URI is not used for anything. Supporting RFC3581 is practically an essential requirement for a SIP proxy if there is a NAT on the route. This is fixed in in VoIP Rel. 2.1.

[seanwg]

Hi
When is 2.1 going to be available?

Interestingly enough, the RPORT being supplied by the SIP Stack in the e65?

Sean