Opened 14 years ago

Last modified 13 years ago

#503 closed defect

Handle the case when CANCEL is responded with 200/OK but 487 is not sent — at Initial Version

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


RFC 3261 Section 9.1:

"Note that both the transaction corresponding to the original request and the CANCEL transaction will complete independently. However, a UAC canceling a request cannot rely on receiving a 487 (Request Terminated) response for the original request, as an RFC 2543-compliant UAS will not generate such a response. If there is no final response for the original request in 64*T1 seconds (T1 is defined in Section, the client SHOULD then consider the original transaction cancelled and SHOULD destroy the client transaction handling the original request."

Currently PJSIP relies on 487 response being received, hence if it's not the INVITE/dialog will get stucked forever.

Change History (0)

Note: See TracTickets for help on using tickets.