Bad port when using rport
Hello all, Our FS server is on a public IP on a dedicated server at one location and all clients are behind nat or vpn from other locations. We have a few "road warrior" clients when our employees travel. I'm seeing the following from one of the client devices. I'm not sure of any of the details of the router (or have anyway to control it) but for some reason the rport is sent with an invalid port number. Notice the 8 at the end of the port number is duplicated. I'm seeing the same behavior from both a Bria client and Zoiper. Is there any way to work around this? An excerpt from Wireshark: 466 2011-08-17 11:36:04.432912 80.34.4.95 206.125.40.171 SIP Request: REGISTER sip:x.x.x.x Internet Protocol, Src: 80.34.4.95 (80.34.4.95), Dst: 206.125.40.171 (x.x.x.x) User Datagram Protocol, Src Port: 56238 (56238), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:x.x.x.x SIP/2.0 Message Header Via: SIP/2.0/UDP 80.34.4.95:562388;rport;branch=z9hG4bKPjSAbzV32ywqJ8xWjWLx81Ml6oQcNlrM.s Max-Forwards: 70 From: "XXXX" <sip:1001@x.x.x.x>;tag=rPFQBJFIKAQpE88mHeiZ7ic59suQY70w To: "XXXX" <sip:1001@x.x.x.x> Call-ID: awr-KAMoJpMYEt2mqkOkknkRrCXUj.Jv CSeq: 27137 REGISTER User-Agent: Bria iPhone 1.2.12 Contact: "XXXX" <sip:1001@80.34.4.95:562388> Expires: 900 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Content-Length: 0
This is what you received from the far end? That looks horribly broken. Time to find out what device and what firewall. -MC On Wed, Aug 17, 2011 at 10:21 AM, Spencer Thomason < spencer@5ninesolutions.com> wrote:
Hello all, Our FS server is on a public IP on a dedicated server at one location and all clients are behind nat or vpn from other locations. We have a few "road warrior" clients when our employees travel. I'm seeing the following from one of the client devices. I'm not sure of any of the details of the router (or have anyway to control it) but for some reason the rport is sent with an invalid port number. Notice the 8 at the end of the port number is duplicated. I'm seeing the same behavior from both a Bria client and Zoiper. Is there any way to work around this?
An excerpt from Wireshark:
466 2011-08-17 11:36:04.432912 80.34.4.95 206.125.40.171 SIP Request: REGISTER sip:x.x.x.x
Internet Protocol, Src: 80.34.4.95 (80.34.4.95), Dst: 206.125.40.171 (x.x.x.x) User Datagram Protocol, Src Port: 56238 (56238), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:x.x.x.x SIP/2.0 Message Header Via: SIP/2.0/UDP 80.34.4.95:562388 ;rport;branch=z9hG4bKPjSAbzV32ywqJ8xWjWLx81Ml6oQcNlrM.s Max-Forwards: 70 From: "XXXX" <sip:1001@x.x.x.x
;tag=rPFQBJFIKAQpE88mHeiZ7ic59suQY70w To: "XXXX" <sip:1001@x.x.x.x> Call-ID: awr-KAMoJpMYEt2mqkOkknkRrCXUj.Jv CSeq: 27137 REGISTER User-Agent: Bria iPhone 1.2.12 Contact: "XXXX" <sip:1001@80.34.4.95:562388> Expires: 900 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS 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
participants (2)
-
Michael Collins
-
Spencer Thomason