Hi Tarun,
If your intention is to ternimate call then CANCEL request is not required
to send, because CANCEL request will cancel INVITE transaction (for
re-invite will not cause call termination).
Also as per RFC CANCEL request is to cancel INVITE transaction and in your
case it has timeout then which transaction your application wants to cancel.
Because timeout means peer has not processed request and UAC should not
expect any response.
RFC 3261
14.1 UAC Behavior
If a UA receives a non-2xx final response to a re-INVITE, the session
parameters MUST remain unchanged, as if no re-INVITE had been issued.
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.
For INVITE initiated dialogs, terminating the dialog consists of
sending a BYE.
Is your application after sending CANCEL request it is waiting for response
to CANCEL request and Re-INVITE request? Or send CANCEL request and then
immediate send BYE request?
Regards,
Ravi Kumar
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Tarun2
Gupta
Sent: Friday, June 08, 2012 1:20 PM
To: SIP
Subject: [Sip-implementors] ReInvite times out, should a Cancel be sent or
not
Hi
Consider the following scenario:
1. A and B are in stable call.
2. A presses hook-flash, ReInvite for hold sent.
3. A - B call put on hold.
4. A presses hook-flash again, ReInvite for resume sent.
5. B does not respond (it is down) and ReInvite times out.
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.
Regards,
Tarun Gupta
Aricent
============================================================================
===
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
============================================================================
===
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
