Hi, I have a situation where Sprout claims that it's sending a REGISTER packet to my app server, but the packet never actually hits the wire, eventually leading to a timeout. Everything up to that point appears to be working correctly. This is the relevant part of the log, and it all looks fine:
21-12-2016 16:04:44.114 UTC Info pjutils.cpp:938: Resolved destination URI > sip:xyz002.test-instance.mydomain.com;transport=tcp;mode=mmtel to 1 > servers > 21-12-2016 16:04:44.114 UTC Debug pjsip: tsx0x7efd9041c Transaction > created for Request msg REGISTER/cseq=1 (tdta0x7efd903a0d30) > 21-12-2016 16:04:44.114 UTC Debug pjutils.cpp:1224: Sending request > 21-12-2016 16:04:44.114 UTC Debug pjsip: tsx0x7efd9041c Sending Request > msg REGISTER/cseq=1 (tdta0x7efd903a0d30) in state Null > 21-12-2016 16:04:44.114 UTC Debug pjsip: endpoint Request msg > REGISTER/cseq=1 (tdta0x7efd903a0d30): skipping target resolution because > address is already set > 21-12-2016 16:04:44.114 UTC Verbose pjsip: tcpc0x7efd9041 TCP client > transport created > 21-12-2016 16:04:44.114 UTC Verbose pjsip: tcpc0x7efd9041 TCP transport > 172.31.xx.xx:59739 is connecting to 172.16.0.42:5101... > 21-12-2016 16:04:44.114 UTC Verbose common_sip_processing.cpp:136: TX 2894 > bytes Request msg REGISTER/cseq=1 (tdta0x7efd903a0d30) to TCP > 172.16.0.42:5101: > --start msg-- > > REGISTER sip:xyz002.test-instance.mydomain.com;transport=tcp;mode=mmtel > SIP/2.0^M > Via: SIP/2.0/TCP > 172.31.xx.xx:59739;rport;branch=z9hG4bKPjwlXMqSj4uLIW3rq6vSs14jUYBgF2Okw5^M > Max-Forwards: 70^M > From: <sip:scscf.ec2-xx-xx-xx-xx.eu-west-1.compute.amazonaws.com > >;tag=eYh3aPqYus73O95cOyIptXcCGRJKHNNd^M > To: <sip:[email protected]>^M > Contact: <sip:scscf.ec2-xx-xx-xx-xx.eu-west-1.compute.amazonaws.com:5054 > >;transport=TCP^M > Call-ID: 831M8e9sLA6p56rIp3ljhaI3q16qSLjX^M > CSeq: 1 REGISTER^M > Expires: 60^M > P-Visited-Network-ID: example.com^M > P-Charging-Function-Addresses: ccf=pri_ccf_address^M > Content-Type: multipart/mixed;boundary="Mbh3iM5WF5XkgRsmXZaAleiBNod4cPT9"^M > Content-Length: 2186^M > ^M > ^M > --Mbh3iM5WF5XkgRsmXZaAleiBNod4cPT9^M > ^M > REGISTER > sip:scscf.ec2-xx-xx-xx-xx.eu-west-1.compute.amazonaws.com:5054;transport=TCP > SIP/2.0^M > Via: SIP/2.0/TCP > 172.31.xx.xx:35157;rport=35157;received=172.31.xx.xx;branch=z9hG4bKPjulgKKi4fabLsCXLLfro-NNpwTrQBpW8H^M > Via: SIP/2.0/TCP > 172.31.xx.xx:39660;rport=39660;received=172.31.xx.xx;branch=z9hG4bKPjTs.q-46EoIXQp85hUbN6f3nkfAwpLHdJ^M > Path: <sip:8vgwPTbL06@clearwater-instance:5058;transport=TCP;lr;ob>^M > Via: SIP/2.0/UDP > 176.252.xx.xx:5060;rport=5060;received=176.252.xx.xx;branch=z9hG4bK529669122^M > From: <sip:[email protected]>;tag=822670698^M > To: <sip:[email protected]>^M > ...etc > > --end msg-- > 21-12-2016 16:04:44.130 UTC Debug pjutils.cpp:1660: Logging SAS Call-ID > marker, Call-ID 712457068 > ... > 21-12-2016 16:04:46.114 UTC Verbose pjsip: tcpc0x7efd9041 TCP transport > connect timeout timed out > The destination address - 172.16.0.42:5101 - is correct. From the host where sprout is running I can ping this IP address and a telnet to that host:port successfully connects to the app server, so there doesn't appear to be anything prohibiting the connection. Unfortunately, a packet capture doesn't detect that this REGISTER packet is actually being sent on any network interface. Can anyone suggest what might be the problem or how I may be able to debug this? I'm using Far'Fetched in case it matters.
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
