Thanks for the link.
I read the thread carefully but was troubled by the attribution of the trouble to the provider.
What i was seeing from the logs was that the error was occurring on packet coming from the
phone.
This is what I saw coming from the phone and the log entries associated with the SIP info request
Phone number obscured with xxxx's
Offending packet
_______________________
Frame 162: 1383 bytes on wire (11064 bits), 1383 bytes captured (11064 bits)
Ethernet II, Src: XiamenYe_f5:0a:d8 (00:15:65:f5:0a:d8), Dst: Vmware_be:23:72 (00:50:56:be:23:72)
Internet Protocol Version 4, Src: 10.10.10.103, Dst: 10.10.10.1
Transmission Control Protocol, Src Port: 12170, Dst Port: 5060, Seq: 2511, Ack: 672, Len: 1317
Session Initiation Protocol (INFO)
Request-Line: INFO sip:
[email protected]:5060;transport=tcp SIP/2.0
Message Header
Via: SIP/2.0/TCP 10.10.10.103:12170;branch=z9hG4bK1940972820
From: <sip:
[email protected]:5060>;tag=1615478443
SIP from address: sip:
[email protected]:5060
SIP from tag: 1615478443
To: <sip:
[email protected]>;tag=a50cdd07
SIP to address: sip:
[email protected]
SIP to tag: a50cdd07
Call-ID: ServuKFNHVkxQDTQW_BceQ..
CSeq: 8 INFO
Sequence Number: 8
Method: INFO
Contact: <sip:
[email protected]:12170;transport=TCP>
Contact URI: sip:
[email protected]:12170;transport=TCP
Contact URI User Part: 332
Contact URI Host Part: 10.10.10.103
Contact URI Host Port: 12170
Contact URI parameter: transport=TCP
Content-Type: application/csta+xml
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T58 58.80.0.25 001565f50ad8
Content-disposition: signal;handling=required
Content-Length: 718
Message Body
<?xml version="1.0" encoding="utf-8"?>\n
<FailedEvent xmlns="
http://www.ecma-international.org/standards/ecma-323/csta/ed5">\n
\t<monitorCrossRefID>0</monitorCrossRefID>\n
\t<failedConnection>\n
\t\t<callID>32771</callID>\n
\t\t<deviceID>sip:
[email protected]:5060</deviceID>\n
\t</failedConnection>\n
\t<failingDevice>\n
\t\t<deviceIdentifier>sip:
[email protected]:5060</deviceIdentifier>\n
\t</failingDevice>\n
\t<callingDevice>\n
\t\t<deviceIdentifier>1xxxxxxx559</deviceIdentifier>\n
\t</callingDevice>\n
\t<calledDevice>\n
\t\t<deviceIdentifier>sip:
[email protected]:5060</deviceIdentifier>\n
\t</calledDevice>\n
\t<lastRedirectionDevice>\n
\t\t<notKnown />\n
\t</lastRedirectionDevice>\n
\t<localConnectionInfo>null</localConnectionInfo>\n
\t<cause>callCancelled</cause>\n
</FailedEvent>\n
________________________________________________________
Log entries for this packet
18/04/2018 20:21:13:324 | 7 | Parsing XML: <?xml version="1.0" encoding="utf-8"?>
<FailedEvent xmlns="
http://www.ecma-international.org/standards/ecma-323/csta/ed5">
<monitorCrossRefID>0</monitorCrossRefID>
<failedConnection>
<callID>32771</callID>
<deviceID>sip:
[email protected]:5060</deviceID>
</failedConnection>
<failingDevice>
<deviceIdentifier>sip:
[email protected]:5060</deviceIdentifier>
</failingDevice>
<callingDevice>
<deviceIdentifier>1xxxxxxx559</deviceIdentifier>
</callingDevice>
<calledDevice>
<deviceIdentifier>sip:
[email protected]:5060</deviceIdentifier>
</calledDevice>
<lastRedirectionDevice>
<notKnown />
</lastRedirectionDevice>
<localConnectionInfo>null</localConnectionInfo>
<cause>callCancelled</cause>
</FailedEvent>
18/04/2018 20:21:13:324 | 7 | Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 1xxxxxxx559 ^@ ../../rutil/ParseBuffer.hxx:230
18/04/2018 20:21:13:324 | 7 | Event: FailedEvent has updated CstaConn{pcid=32771,caller=,C:0.0;connst=null}
