Opened 7 years ago

Last modified 7 years ago

#1651 closed defect

Incoming CANCEL request isn't reported in any callbacks — at Version 2

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-2.2
Component: pjsip Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported: no

Description (last modified by bennylp)

Incoming CANCEL request currently is not reported in any callbacks, not even on_tsx_state() (or on_call_tsx_state() in pjsua). This makes it impossible for application to review some headers in the request, most notably the Reason header (RFC 3326).

This happens because CANCEL is responded automatically by the INVITE session (including generation of 487 to INVITE), and due to how the flow is arranged, application will see the 200/OK response to CANCEL first in the callback, and then 487 to INVITE, before the CANCEL request itself. But pjsua application will not see the CANCEL request at all because by the time the CANCEL request is reported, call has been disconnected and further events from the INVITE session has been suppressed.

Change History (2)

comment:1 Changed 7 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 7 years ago by bennylp

  • Description modified (diff)
Note: See TracTickets for help on using tickets.