Hi,
I am working on getting my two SIP phones behind firewall to talk to each other. One client is SPA 921 and the other client is xlite; and I am force rport for all SIP requests from clients. When xlite sends a INVITE request to openser, openser tries to send to SPA 921, but the PORT is still 5060, instead of 22848. Therefore, Openser keeps resending INVITE to SPA 921 but never reaches it. Both linksys and xlite do send preiodic SUBSCRIBE/NOTIFY to Openser. Is there anything else I am missing?
U 48.133.23.45:21395 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.100:53722;branch=z9hG4bK-d87543-683f775fdd79a93d-1--d 87543-;rport. Max-Forwards: 70. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF O. Content-Type: application/sdp. Supported: timer. User-Agent: X-Lite release 1011s stamp 41150. Content-Length: 371. . v=0. o=- 9 2 IN IP4 192.168.1.100. s=CounterPath X-Lite 3.0. c=IN IP4 192.168.1.100. t=0 0. m=audio 5416 RTP/AVP 107 119 100 106 0 105 98 8 101. a=fmtp:101 0-15. a=rtpmap:107 BV32/16000. a=rtpmap:119 BV32-FEC/16000. a=rtpmap:100 SPEEX/16000. a=rtpmap:106 SPEEX-FEC/16000. a=rtpmap:105 SPEEX-FEC/8000. a=rtpmap:98 iLBC/8000. a=rtpmap:101 telephone-event/8000. a=sendrecv.
U 48.133.200.20:5060 -> 48.133.23.45:21395 SIP/2.0 100 Giving a try. Via: SIP/2.0/UDP 192.168.1.100:53722;branch=z9hG4bK-d87543-683f775fdd79a93d-1--d 87543-;rport=21395;received=48.133.23.45. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Record-Route: sip:48.133.200.20;lr=on;ftag=12709c02. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE,
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Record-Route: sip:48.133.200.20;lr=on;ftag=12709c02. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE,
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Record-Route: sip:48.133.200.20;lr=on;ftag=12709c02. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE,
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Record-Route: sip:48.133.200.20;lr=on;ftag=12709c02. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE,
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Record-Route: sip:48.133.200.20;lr=on;ftag=12709c02. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE,
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 sip%3A1005@48.133.23.45 SIP/2.0. Record-Route: sip:48.133.200.20;lr=on;ftag=12709c02. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: sip:2000@48.133.23.45:21395. To: "1005"<sip:1005@48.133.23.45 sip%3A1005@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE,
U 48.133.23.45:21395 -> 48.133.200.20:5060 SUBSCRIBE sip:2000@48.133.23.45 sip%3A2000@48.133.23.45 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.100:53722;branch=z9hG4bK-d87543-d900ee1c55767008-1--d 87543-;rport. Max-Forwards: 70. Contact: sip:2000@48.133.23.45:21395. To: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>. From: "2000"<sip:2000@48.133.23.45 sip%3A2000@48.133.23.45>;tag=8b347a51. Call-ID: MzY3NGIwNTJlMWY5Njg2MmM5YmI1NTIxNTRjZjljYzM.. CSeq: 1 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF O. Supported: timer. User-Agent: X-Lite release 1011s stamp 41150. Event: message-summary. Content-Length: 0. .
U 48.133.23.45:22840 -> 48.133.200.20:5060 NOTIFY sip:48.133.23.45 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-2c2e52f6;rport. From: "1005" <sip:1005@48.133.23.45 sip%3A1005@48.133.23.45
;tag=a45646112863dco0.
To: sip:48.133.23.45. Call-ID: ad4c4ce-bb2b86f4@192.168.1.101. CSeq: 1017 NOTIFY. Max-Forwards: 70. Event: keep-alive. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. .
Any suggestion will be helpful.
JB
El Wednesday 09 July 2008 03:39:38 Juan Backson escribió:
Hi,
I am working on getting my two SIP phones behind firewall to talk to each other. One client is SPA 921 and the other client is xlite; and I am force rport for all SIP requests from clients.
It seems innecesary since Xlite adds by itself "rport" parameter.
When xlite sends a INVITE request to openser, openser tries to send to SPA 921, but the PORT is still 5060, instead of 22848.
Why should it be 22848? the destination or source port? "22848" appears never in your trace. Why do you know it should be port 22848?
Therefore, Openser keeps resending INVITE to SPA 921 but never reaches it.
What I see is:
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
Extrange.
Both linksys and xlite do send preiodic SUBSCRIBE/NOTIFY to Openser. Is there anything else I am missing?
That doesn't matter now.
If 22848 is the configured SIP port for the client, you should be sure that it first registered with that port.
Then I don't understand who is who here (sorry I missed the first part of the discussion and maybe you specified it):
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
Why the invite is bouncing from one UA to the other? Or one is OpenSER?
-----Original Message----- From: users-bounces@lists.openser.org [mailto:users-bounces@lists.openser.org] On Behalf Of Iñaki Baz Castillo ibc@in.ilimit.es Sent: Mittwoch, 9. Juli 2008 11:32 To: users@lists.openser.org Subject: Re: [OpenSER-Users] INVITE NAT problem
El Wednesday 09 July 2008 03:39:38 Juan Backson escribió:
Hi,
I am working on getting my two SIP phones behind firewall to talk to each other. One client is SPA 921 and the other client is xlite; and I am force rport for all SIP requests from clients.
It seems innecesary since Xlite adds by itself "rport" parameter.
When xlite sends a INVITE request to openser, openser tries to send to SPA 921, but the PORT is still 5060, instead of 22848.
Why should it be 22848? the destination or source port? "22848" appears never in your trace. Why do you know it should be port 22848?
Therefore, Openser keeps resending INVITE to SPA 921 but never reaches it.
What I see is:
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 SIP/2.0.
Extrange.
Both linksys and xlite do send preiodic SUBSCRIBE/NOTIFY to Openser. Is there anything else I am missing?
That doesn't matter now.
-
Diego Costantini -
Iñaki Baz Castillo -
Juan Backson