Changes between Initial Version and Version 1 of Ticket #1627


Ignore:
Timestamp:
Feb 26, 2013 12:26:10 PM (11 years ago)
Author:
nanang
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1627 – Description

    initial v1  
    1 A known use case is that application wants to be notified via on_tsx_state_changed() when asynchronous send operation of the initial INVITE fails, e.g: caused by transport disconnection. 
     1When a call is disconnected, SIP invite module will call {{{on_call_state(DISCONNECTED)}}} first before {{{on_tsx_state_changed()}}}. However, in PJSUA, the {{{on_call_state(DISCONNECTED)}}} will reset PJSUA call states and the next incoming {{{on_tsx_state_changed()}}} will not be forwarded to the application, as it will not make sense for the application to still receive {{{on_tsx_state_changed()}}} after the call is disconnected (and the PJSUA call states are resetted). 
     2 
     3An easy or low-risk workaround will be 'manually' invoking {{{on_tsx_state_changed()}}} from {{{on_call_state(DISCONNECTED)}}}.