> How should the call be terminated. Should a Cancel be sent for ReInvite > followed by a Bye or Bye alone would suffice? At our end, A sends a > Cancel for ReInvite followed by Bye. Is it incorrect behavior? Can you > please give me some normative references to support your answer.
Since no 1xx was received, send only BYE. However if decide not to follow the normative RFC 3261 section 9.1 statement concerning CANCEL, I recommend not uselessly retrying CANCEL within this situation because it adds even more useless network traffic. RFC 3261 section 9.1: "If no provisional response has been received, the CANCEL request MUST NOT be sent; rather, the client MUST wait for the arrival of a provisional response before sending the request." RFC 3261 section 12.2.1.2: "If the response for a request within a dialog is a 481 (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the UAC SHOULD terminate the dialog. A UAC SHOULD also terminate a dialog if no response at all is received for the request (the client transaction would inform the TU about the timeout.) For INVITE initiated dialogs, terminating the dialog consists of sending a BYE." RFC 3261 section 14.1 "Note that, as stated in Section 12.2.1.2, if the non-2xx final response is a 481 (Call/Transaction Does Not Exist), or a 408 (Request Timeout), or no response at all is received for the re-INVITE (that is, a timeout is returned by the INVITE client transaction), the UAC will terminate the dialog." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
