Changes between Initial Version and Version 2 of Ticket #1049


Ignore:
Timestamp:
Apr 7, 2014 9:24:39 AM (10 years ago)
Author:
bennylp
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1049

    • Property Backported unset
    • Property Milestone changed from Known-Issues-and-Ideas to release-2.x

  • Ticket #1049 – Description

    initial v2  
    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. 
    55 - 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 (!) 
     6 - 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 
    67 
    78In all cases above, it is desirable to have the application receives the DISCONNECTED event immediately and let PJSUA-LIB handle the call under the hood. Several scenarios that must be handled by PJSUA-LIB include: 
    … …  
    1011    - 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. 
    1112 - 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. 
     13 - 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 
     14