SIP RFC 6432 Non-Compliance: CANCEL packet - Printable Version +- Yealink Forums (http://forum.yealink.com/forum) +-- Forum: IP Phone Series (/forumdisplay.php?fid=4) +--- Forum: T4x Series (/forumdisplay.php?fid=31) +--- Thread: SIP RFC 6432 Non-Compliance: CANCEL packet (/showthread.php?tid=40759) |
SIP RFC 6432 Non-Compliance: CANCEL packet - Luke Escude - 04-06-2017 02:10 AM The handsets are displaying a Missed Call even though a CANCEL packet "answered elsewhere" was sent to the phones. This only occurs on PJSIP, not old SIP, because of the Reason Code header containing Q.850 (instead of just cause=200, it contains both) According to RFC 6432 (https://tools.ietf.org/html/rfc6432 ) the presence of this header should not affect normal operation. I have attached a screenshot of a PCAP of the q.850 header. The desired outcome would be to NOT mark a Missed Call, in accordance with RFC 6432 |