Difference between revisions of "DUM Ending an Invite Session"

From reSIProcate
Jump to navigation Jump to search
 
Line 1: Line 1:
* To send a CANCEL to cancel for a UAC INVITE (for which a dialog creating response has NOT yet been recieved) and cancel all potential legs of the invite - use the InviteSessionHandle->getAppDialogSet()->end() call.
+
* To send a CANCEL to cancel for a UAC INVITE (for which a dialog creating response has NOT yet been recieved) and cancel all potential legs of the invite - use the AppDialogSet::end() or endCommand() call.
  
 
* To send a BYE for one particular leg of an early UAC INVITE (for which a 200 response has NOT yet been recieved) - use the InviteSessionHandle->end() call.
 
* To send a BYE for one particular leg of an early UAC INVITE (for which a 200 response has NOT yet been recieved) - use the InviteSessionHandle->end() call.

Latest revision as of 11:46, 3 May 2021

  • To send a CANCEL to cancel for a UAC INVITE (for which a dialog creating response has NOT yet been recieved) and cancel all potential legs of the invite - use the AppDialogSet::end() or endCommand() call.
  • To send a BYE for one particular leg of an early UAC INVITE (for which a 200 response has NOT yet been recieved) - use the InviteSessionHandle->end() call.
WARNING - sending a BYE to an early dialog, does not cancel the original Invite Transaction 
        - if you are done with the invite entirely, then you MUST call AppDialogSet::end() 
          in order to properly dispose of the invite transaction state to avoid memory leaks
  • To send a BYE for an established Invite Session (for which a 200 response has been recieved) - use the InviteSessionHandle->end() call.