Hi, INVITE messages that are passed from Perimeta to Sprout are sometimes failing with PJSIP syntax errors like this:
12-10-2014 23:51:34.590 UTC Error pjsip: sip_transport. Error processing 1935 bytes packet from TCP 172.31.12.131:16187 : PJSIP syntax error exception when parsing 'Request Line' header on line 1 col 2: v=0 It seems that the usual first line of an INVITE message - "INVITE sip:x...@example.com SIP/2.0" - is being dropped or lost from the incoming message. I started noticing this in Omar Sharif Bridge and noticed it again today after I upgraded to Pacman. Although I can't say for sure if it did or didn't happen in previous releases. Attached is a Perimeta log, packets captures and Sprout log. It shows the outbound INVITE from Perimeta looking ok, the incoming packet in Clearwater looking ok, but the INVITE is mangled by the time it gets to Sprout. I also see a similar problem with some ACK messages: 12-10-2014 23:51:14.976 UTC Error pjsip: sip_transport. Error processing 1873 bytes packet from TCP 172.31.12.131:16187 : PJSIP syntax error exception when parsing '9f9' header on line 3 col 0: ACK sip:6505550...@example.com SIP/2.0 Via: SIP/2.0/TCP 172.31.12.131:5054 ;branch=z9hG4bK+026450efe9bd543d06cda901075ba5e71+sip+1+a64de9f9 9f9 From: <sip:6505550...@example.com>;tag=172.31.12.131+1+f89a617c+fd93093c To: sip:6505550...@example.com My Perimeta and Clearwater instances are in the same ec2 subnet. Is there anything I can do to configure this problem away? thanks Steve
09-10-2014 03:35:04.130 UTC Verbose pjsip: tcps0x7f69d407 TCP connection closed 09-10-2014 03:35:04.130 UTC Debug connection_tracker.cpp:91: Connection 0x7f69d4072b18 has been destroyed 09-10-2014 03:35:04.130 UTC Verbose pjsip: tcps0x7f69d407 TCP transport destroyed with reason 70016: End of file (PJ_EEOF) 09-10-2014 03:35:07.427 UTC Error pjsip: sip_transport. Error processing 1853 bytes packet from TCP 172.31.12.131:13228 : PJSIP syntax error exception when parsing 'Request Line' header on line 1 col 2: v=0^M o=6505550207 136833367048338 136833367048338 IN IP4 172.31.12.131^M s=-^M c=IN IP4 172.31.12.131^M t=0 0^M m=audio 16690 RTP/AVP 0 8 101^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M m=video 16694 RTP/AVP 34 99 98^M a=rtpmap:99 MP4V-ES/90000^M a=rtpmap:98 H263-1998/90000^M a=fmtp:99 profile-level-id=3^M a=fmtp:98 CIF=1;QCIF=1^M INVITE sip:6505550...@example.com SIP/2.0^M Via: SIP/2.0/TCP 172.31.12.131:5054;branch=z9hG4bK+9cca828a588a1e2794db23991d5e1bb71+sip+1+a64deafc^M From: <sip:6505550...@example.com>;tag=172.31.12.131+1+b11d0a73+d85da41b^M To: sip:6505550...@example.com^M CSeq: 20 INVITE^M Expires: 180^M Route: <sip:ec2-54-79-19-17.ap-southeast-2.compute.amazonaws.com:5054;transport=TCP;lr;orig>^M Content-Length: 331^M Call-Info: <sip:172.31.12.131:5054>;method="NOTIFY;Event=telephone-event;Duration=2000"^M Supported: replaces, outbound^M P-Charging-Vector: icid-value=850408e553e0567b4eaf2594d3830bfb^M Contact: <sip:6505550207@131.203.101.233:50661;transport=tcp>;+sip.instance="<urn:uuid:a64e1192-ad89-4ccf-968a-d7a99dfdd2f5>"^M Record-Route: <sip:172.31.12.131:5054;transport=tcp;lr>^M Content-Type: application/sdp^M P-Served-User: sip:6505550...@example.com^M P-Asserted-Identity: sip:6505550...@example.com^M Call-ID: 0gQAAC8WAAACBAAALxYAAHypekjFTiM001M4wVeknlQ-@172.31.12.131^M Max-Forwards: 69^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO^M User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)^M P-Visited-Network-ID: example.com^M Accept: application/sdp, application/dtmf-relay^M ^M v=0^M o=6505550207 75269305883327 75269305883327 IN IP4 172.31.12.131^M s=-^M c=IN IP4 172.31.12.131^M t=0 0^M m=audio 16698 RTP/AVP 0 8 101^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M m=video 16702 RTP/AVP 34 99 98^M a=rtpmap:99 MP4V-ES/90000^M a=rtpmap:98 H263-1998/90000^M a=fmtp:99 profile-level-id=3^M a=fmtp:98 CIF=1;QCIF=1^M -- end of packet. ~
**** Call correlator: 0X010077E15435F39D **** 9-October-2014, 03:35:07.042+00:00. **** MMF editing was applied to an outbound message. MMF editing has been applied to an outbound message. Logged below are the edit sequence that was applied and the message before any edits were made. Edit Sequence: Route_Register_to_ICSCF Edit Sequence Truncated?: 0 Message before editing: INVITE sip:6505550...@example.com SIP/2.0 From: <sip:6505550...@example.com>;tag=172.31.12.131+1+b11d0a73+d85da41b To: sip:6505550...@example.com CSeq: 20 INVITE Expires: 180 Route: <sip:ec2-54-79-19-17.ap-southeast-2.compute.amazonaws.com:5054;transport=TCP;lr;orig> Content-Length: 331 Call-Info: <sip:172.31.12.131:5054>;method="NOTIFY;Event=telephone-event;Duration=2000" Supported: replaces, outbound P-Charging-Vector: icid-value=850408e553e0567b4eaf2594d3830bfb Contact: <sip:6505550207@131.203.101.233:50661;transport=tcp>;+sip.instance="<urn:uuid:a64e1192-ad89-4ccf-968a-d7a99dfdd2f5>" Record-Route: <sip:172.31.12.131:5054;transport=tcp;lr> Content-Type: application/sdp P-Served-User: sip:6505550...@example.com P-Asserted-Identity: sip:6505550...@example.com Call-ID: 0gQAAC8WAAACBAAALxYAAHypekjFTiM001M4wVeknlQ-@172.31.12.131 Max-Forwards: 69 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: Linphone/3.7.0 (belle-sip/1.3.0) P-Visited-Network-ID: example.com Accept: application/sdp, application/dtmf-relay v=0 o=6505550207 75269305883327 75269305883327 IN IP4 172.31.12.131 s=- c=IN IP4 172.31.12.131 t=0 0 m=audio 16698 RTP/AVP 0 8 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=video 16702 RTP/AVP 34 99 98 a=rtpmap:99 MP4V-ES/90000 a=rtpmap:98 H263-1998/90000 a=fmtp:99 profile-level-id=3 a=fmtp:98 CIF=1;QCIF=1 **** Call correlator: 0X010077E15435F39D **** 9-October-2014, 03:35:07.042+00:00. **** Outgoing SIP message sent. Outgoing SIP message sent: INVITE sip:6505550...@example.com SIP/2.0 Via: SIP/2.0/TCP 172.31.12.131:5054;branch=z9hG4bK+9cca828a588a1e2794db23991d5e1bb71+sip+1+a64deafc From: <sip:6505550...@example.com>;tag=172.31.12.131+1+b11d0a73+d85da41b To: sip:6505550...@example.com CSeq: 20 INVITE Expires: 180 Route: <sip:ec2-54-79-19-17.ap-southeast-2.compute.amazonaws.com:5054;transport=TCP;lr;orig> Content-Length: 331 Call-Info: <sip:172.31.12.131:5054>;method="NOTIFY;Event=telephone-event;Duration=2000" Supported: replaces, outbound P-Charging-Vector: icid-value=850408e553e0567b4eaf2594d3830bfb Contact: <sip:6505550207@131.203.101.233:50661;transport=tcp>;+sip.instance="<urn:uuid:a64e1192-ad89-4ccf-968a-d7a99dfdd2f5>" Record-Route: <sip:172.31.12.131:5054;transport=tcp;lr> Content-Type: application/sdp P-Served-User: sip:6505550...@example.com P-Asserted-Identity: sip:6505550...@example.com Call-ID: 0gQAAC8WAAACBAAALxYAAHypekjFTiM001M4wVeknlQ-@172.31.12.131 Max-Forwards: 69 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: Linphone/3.7.0 (belle-sip/1.3.0) P-Visited-Network-ID: example.com Accept: application/sdp, application/dtmf-relay v=0 o=6505550207 75269305883327 75269305883327 IN IP4 172.31.12.131 s=- c=IN IP4 172.31.12.131 t=0 0 m=audio 16698 RTP/AVP 0 8 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=video 16702 RTP/AVP 34 99 98 a=rtpmap:99 MP4V-ES/90000 a=rtpmap:98 H263-1998/90000 a=fmtp:99 profile-level-id=3 a=fmtp:98 CIF=1;QCIF=1 **** Call correlator: 0X010077E15435F39D **** 9-October-2014, 03:35:39.042+00:00. **** Adjacency receives inbound message.
_______________________________________________ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/listinfo/clearwater
