Hi, Thanks for raising this!
What version of Clearwater are you running? I ask because we've made some changes to this fairly recently to correctly parse the parameters in the Contact header (e.g. https://github.com/Metaswitch/sprout/commit/de7ec101c63280f4c231c4fec480274f8fcaa1c4). If you're not running the up-to-date version of Clearwater then can you upgrade and see if this issue persists. If you are running up-to-date Clearwater (the current version is International Cricket Captain) then can you give me more details as to the exact REGISTER scenario you're using, and attach the debug logs from Sprout so that I can try and reproduce the issue on my system. The sprout logs are produced in /var/log/sprout/sprout*.txt. By default the logging level is set to log level 2, which only includes errors and very high level events. To enable debug logs, change the log level to 5 by writing log_level=5 to /etc/clearwater/user_settings (creating it if it doesn't exist already), and restart sprout (using service sprout stop - monit automatically restarts it). Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tek Gee Sent: 09 July 2014 22:34 To: [email protected] Subject: [Clearwater] SIP Client not able to register with CW due to different Contact header Hi, Please could you help me with the below issue, the SIP client am using is not able to register with CW. Though the CW sends a 200OK to the register, the client doesn't accept it and keeps sending REGISTER as it doesnt like the 200OK it received. The reason I got from the SIP client developers was " The problem is most likely that the server adds the transport=udp in the wrong place in the contact. It should remain a URI parameter." [2013/12/10 16:54:21] Dec 10 16:52:12.810 6.4.20.162:5060>>>> Send to 6.4.71.86:8060 [2013/12/10 16:54:21] REGISTER sip:example.com SIP/2.0 [2013/12/10 16:54:21] Accept: application/reginfo+xml, application/rlmi+xml, application/sdp, application/simple-message-summary, application/watcherinfo+xml, message/sipfrag, multipart/mixed [2013/12/10 16:54:21] Via: SIP/2.0/UDP 6.4.20.162:5060 ;branch=z9hG4bK60b1c87c1fb06a89f;rport [2013/12/10 16:54:21] Route: <sip:6.4.71.86:8060;lr> [2013/12/10 16:54:21] Max-Forwards: 70 [2013/12/10 16:54:21] From: <sip:[email protected]>;tag=7a1d1acc78 [2013/12/10 16:54:21] To: <sip:[email protected]> [2013/12/10 16:54:21] Call-ID: 24cc062b641c4110 [2013/12/10 16:54:21] CSeq: 1186841651 REGISTER [2013/12/10 16:54:21] Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, PRACK, REFER, SUBSCRIBE, UPDATE [2013/12/10 16:54:21] Allow-Events: refer, vq-rtcpxr [2013/12/10 16:54:21] Authorization: Digest username="[email protected] ",realm="example.com",uri="sip:example.com ",nonce="",response="",algorithm=MD5 [2013/12/10 16:54:21] Contact: *<sip:[email protected]:5060;transport=udp>* ;expires=3600;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-088039F7183D>" [2013/12/10 16:54:21] Supported: 100rel, answermode, eventlist, gruu, histinfo, outbound, path, replaces, tdialog, timer [2013/12/10 16:54:21] Content-Length: 0 [2013/12/10 16:54:21] [2013/12/10 16:54:21] Dec 10 16:52:12.840 6.4.20.162:5060<<<< Recv from 6.4.71.86:8060 [2013/12/10 16:54:21] SIP/2.0 200 OK [2013/12/10 16:54:21] Service-Route: <sip:10.0.2.15:5054 ;transport=TCP;lr;orig> [2013/12/10 16:54:21] Via: SIP/2.0/UDP 6.4.20.162:5060 ;rport=5060;received=10.0.2.2;branch=z9hG4bK60b1c87c1fb06a89f [2013/12/10 16:54:21] Call-ID: 24cc062b641c4110 [2013/12/10 16:54:21] From: <sip:[email protected]>;tag=7a1d1acc78 [2013/12/10 16:54:21] To: <sip:[email protected] >;tag=z9hG4bKPjB3CstzB2s3dJ001qhYwztgvKCqIcRiEE [2013/12/10 16:54:21] CSeq: 1186841651 REGISTER [2013/12/10 16:54:21] Supported: outbound [2013/12/10 16:54:21] *Contact: <sip:[email protected]:5060 <http://sip:[email protected]:5060>>*;expires=3600;*transport=udp* ;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-088039F7183D>" [2013/12/10 16:54:21] Require: outbound [2013/12/10 16:54:21] Path: sip:[email protected]:5058 ;transport=TCP;lr;ob [2013/12/10 16:54:21] P-Associated-URI: <sip:[email protected]> [2013/12/10 16:54:21] Content-Length: 0 Thanks _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
