The x-sipX-nonat URL parameter is added by the NAT traversal subsystem of sipXecs and SIP endpoints should be capable of simply ignoring those. I have tested this with many, many SIP endpoints and they all are capable of handling this properly. Are you finding that these are causing problems with one of your SIP endpoints? cheers, bob ________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Wen Jun Sent: Thursday, December 03, 2009 4:12 AM To: [email protected] Subject: [sipx-users] INVITE Request from SIPX Hi, I am simulating a call between two of my SIP clients ( caller 1000 and callee 1500) through SIPX. Both of them were well registered in SIPX. One abnormal thing is the INVITE Request Line from SIP Proxy to callee was change to caller INVITE sip:[email protected]:46858;x-sipX-nonat SIP/2.0 rather than expected callee INVITE sip:1...@xxxxx. I have no idea what's the behaviors of SIPX on this and in the captured log of call between Eyebeam, the request line were same of callee number. Is there anything wrong on my SIP client ? Pls refer to the call log with details. Thanks in advance. Regards, Jun ------------------------------------------------------------------------ ---------- UDP message sent (757 bytes): INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 192.168.2.2:46858;branch=z9hG4bK-6853-1-16 From: 1000 <sip:[email protected]>;tag=1 To: 1500 <sip:[email protected]> Call-ID: [email protected] CSeq: 2 INVITE Contact: sip:[email protected]:46858;UDP Proxy-Authorization: Digest username="1000",realm="sipx.net",uri="sip:192.168.2.6:5060",nonce="1e990 ccbb370e10b2ded32f9fd99acd34b1776c1",response="778c0f0537f56b7daa4023877 4b 7edab",algorithm=MD5 Max-Forwards: 70 Subject: Performance Test Content-Type: application/sdp Content-Length: 199 v=0 o=sipx 53655765 2353687637 IN IP4 4 192.168.2.2 s=- c=IN IP4 4 192.168.2.2 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 ----------------------------------------------- 2009-12-03 16:28:49:799.954 UDP message received [221] bytes : SIP/2.0 100 Trying From: 1000 <sip:[email protected]>;tag=1 To: 1500 <sip:[email protected]> Call-Id: [email protected] Cseq: 2 INVITE Via: SIP/2.0/UDP 192.168.2.2:46858;branch=z9hG4bK-6853-1-16 Content-Length: 0 ----------------------------------------------- 2009-12-03 16:28:49:828.684 UDP message received [1156] bytes : INVITE sip:[email protected]:46858;x-sipX-nonat SIP/2.0 Record-Route: <sip:192.168.2.6:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMQ%60%60%21fc7e f8cf7966d3653e1516abe9cc419b> Via: SIP/2.0/UDP 192.168.2.6;branch=z9hG4bK-sipXecs-9a6a43b8a61c6e1fdaadf21ab43b019c2e07 Via: SIP/2.0/UDP 192.168.2.6;branch=z9hG4bK-sipXecs-9a5bb3a2258a22b51d7dc9473cab172cc171~ d91e8c9d1ba1106312b7fe08ea2293a6 Via: SIP/2.0/UDP 192.168.2.2:46858;branch=z9hG4bK-6853-1-16 From: 1000 <sip:[email protected]>;tag=1 To: 1500 <sip:[email protected]> Call-Id: [email protected] Cseq: 2 INVITE Contact: <sip:[email protected]:46858;x-sipX-nonat>;UDP Proxy-Authorization: Digest username="1000",realm="sipx.net",uri="sip:192.168.2.6:5060",nonce="1e990 ccbb370e10b2ded32f9fd99acd34b1776c1",response="778c0f0537f56b7daa4023877 4b 7edab",algorithm=MD5 Max-Forwards: 18 Subject: Performance Test Content-Type: application/sdp Content-Length: 199 Date: Thu, 03 Dec 2009 08:28:49 GMT v=0 o=sipx MVP 53655765 2353687637 IN IP4 4 192.168.2.2 s=- c=IN IP4 4 192.168.2.2 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
