Via: rport support (RFC3581)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Register to a SIP server via Wifi (behind NAT)
2. Make a call to another phone

What is the expected output? What do you see instead?
1. "rport" should be included in "Via" header in INVITE packet

What version of the product are you using? On what operating system?
1. Any version

Which SIP server are you using? What happens with PBXes?
1. Asterisk
2. PBXes not tested

Which type of network are you using?
1. Wifi with private IP assigned
2. SIP server is on the Internet with public IP

Please provide any additional information below.

Original issue reported on code.google.com by tommy.ht...@gmail.com on 25 Feb 2010 at 3:15

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 21 Mar 2010 at 10:15

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

hhm, the request my proxy receives, do have rport parameters on the via header.

perhaps the rport is added by the NAT gateway?

<sip:droid@ims.bangert.dk>;tag=z9hG4bK20018618
REGISTER sip:ims.bangert.dk SIP/2.0
Via: SIP/2.0/TCP 10.223.33.93:35424;rport;branch=z9hG4bK45388
Max-Forwards: 70
To: <sip:droid@ims.bangert.dk>
From: <sip:droid@ims.bangert.dk>;tag=z9hG4bK20018618
Call-ID: 603517269502@10.223.33.93
CSeq: 1 REGISTER
Contact: <sip:droid@10.223.33.93:35424;transport=tcp>
Expires: 3600
User-Agent: Sipdroid/1.5.5 beta/Nexus One
Content-Length: 0

Original comment by thilo.ba...@gmail.com on 30 Jul 2010 at 8:34

[GoogleCodeExporter]

Original comment by thilo.ba...@gmail.com on 25 Aug 2010 at 2:35

• Changed title: Via: rport support (RFC3581)

[GoogleCodeExporter]

RFC 3581 says the INVITE includes the header value "rport" but the addressed 
server (or proxy) inserts the port number on which the INV was received when 
responding.

Original comment by WilF...@gmail.com on 17 Apr 2011 at 1:21