Changes between Initial Version and Version 1 of Ticket #302


Ignore:
Timestamp:
May 30, 2007 4:30:17 AM (17 years ago)
Author:
bennylp
Comment:

Fixed in r1319

The behavior now is, when cancel is requested and the INVITE transaction has not received any provisional response:

  1. INVITE transaction ceases retransmission.
  2. When provisional response is received after this, CANCEL will be sent, and the session will terminate after remote sends 487 to the INVITE transaction.
  3. When no response (to INVITE transaction) is ever received, the INVITE transaction will time out after 64*T1 from the original transmission, and the callback is called.
  4. When 200 (to INVITE transaction) is received, the session will be established and no CANCEL will be sent.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #302

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed
    • Property Summary changed from Behavior in cancelling INVITE session when no provisional response has been received to Behavior in cancelling INVITE session when no provisional response has been received (thanks Esbjörn Dominique)

  • Ticket #302 – Description

    initial v1  
    44 
    55This is the part where pjsip is not compliant. 
     6 
     7Currently the invite session will just terminate the session immediately (CANCEL is not sent), so if any response is ever received, this will cause erroneous behavior.