Changes between Version 3 and Version 4 of Ticket #1049


Ignore:
Timestamp:
Apr 7, 2014 9:31:30 AM (5 years ago)
Author:
bennylp
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1049 – Description

    v3 v4  
    33 - when BYE is issued against peer which doesn't exist; in this case, the DISCONNECTED state will be issued after the BYE transaction times out, 32 seconds after it is issued 
    44 - when BYE is answered with failure final response; in this case, most likely call will stay as is. Note that 408 and 481 response would cause call to be terminated though. 
    5  - ~~~when 200/OK for CANCEL is received, but the final response for the INVITE transaction never arrives; in this case, call will remain as is indefinitely (!)~~~ (done in #796) 
     5 - ~~~when 200/OK for CANCEL is received, but the final response for the INVITE transaction never arrives; in this case, call will remain as is indefinitely (!)~~~ (done in #503) 
    66 - when ACK is not received yet for 200/OK, UAS is not able to send BYE (see #1712). The stack ideally should send the BYE automatically once ACK is received 
    77 
     
    99 - sending BYE if call isn't disconnected after CANCEL is issued, possibly using a timer: 
    1010    - it is possible that the CANCEL request and 200/OK to INVITE had crossed each other in the wire; in this case, the call will get CONNECTED and the CANCEL will be rejected with 481 (please check this in the spec) 
    11     - ~~~peer may have been malfunctioning, not disconnecting the call even after sending 200/OK response to CANCEL. We may need to have a timer for this.~~~ (done in #796) 
     11    - ~~~peer may have been malfunctioning, not disconnecting the call even after sending 200/OK response to CANCEL. We may need to have a timer for this.~~~ (done in #503) 
    1212 - retry sending the BYE if previous ones fail and call remains connected. If this keeps happening (the BYE request gets rejected), we'll probably need to hard-terminate the call, that is to forcefully terminate the call without relying for the BYE to succeed. 
    1313 - when ACK is not received yet for 200/OK, UAS is not able to send BYE (see #1712). The stack ideally should send the BYE automatically once ACK is received