Yes,
My requirement is to clear the call since the immediate proxy is down and
not responding.
This will be done eventually by UAS. Because peer has to send 487
(RECOMMENDED) response to pending transactions.
15.1.2 UAS Behavior
The UAS MUST still respond to any pending requests received for that
dialog. It is RECOMMENDED that a 487 (Request Terminated) response
be generated to those pending requests.
As per RFC 5404 this is not exact scenario, but your scenario can be
associate with this and preferred is to send BYE.
Here Bob after sending Re-INVITE wants to terminate call, so send BYE.
3.2.3. UA Receives 200 OK for re-INVITE (Established State) While in
the Mortal State
State Alice Bob State
| |
| INVITE F1 |
|----------------------->|
Pre | 180 Ringing F2 | Pre
|<-----------------------|
Ear | | Ear
| 200 OK F3 |
|<-----------------------|
Mora | ACK F4 | Mora
|----------------------->|
Est | Both Way RTP Media | Est
|<======================>|
| |
| re-INVITE F5 |
|<-----------------------|
| 200 F7 BYE F6 |
|--------- ----------|
| \ / | Mort
| X |
| / \ |
|<-------- --------->| *race*
Mort | 200 F8 ACK F9 |
| (BYE) (re-INV) |
|--------- ----------|
| ^ \ / |
| | X |
| | / \ |
|<-------- --------->|
| | ^ |
| | Timer K | |
| | V |
| | Timer J | Morg
| V |
Morg | |
| |
Note: As noted in Section 3.1.4, implementation issues are outside
the scope of this document, but the following tip is provided for
avoiding race conditions of this type. The UAC can delay sending a
BYE F6 until the re-INVITE transaction F5 completes. Implementors
can decouple the actions of the user (e.g., hanging up) from the
actions of the protocol (the sending of BYE F6), so that the UA can
behave like this. In this case, it is the implementor's choice as to
how long to wait.
Regards,
Ravi Kumar
-----Original Message-----
From: Tarun2 Gupta [mailto:[email protected]]
Sent: Friday, June 08, 2012 2:36 PM
To: Ravi Kumar; 'SIP'
Subject: RE: [Sip-implementors] ReInvite times out, should a Cancel be sent
or not
Ravi
My requirement is to clear the call since the immediate proxy is down and
not responding. My Application is sending Cancel for the ReInvite
immediately followed by Bye.
So the correct behavior is to just send a Bye in case of a timeout?
Regards,
Tarun Gupta
Aricent
-----Original Message-----
From: Ravi Kumar [mailto:[email protected]]
Sent: Friday, June 08, 2012 2:21 PM
To: Tarun2 Gupta; 'SIP'
Subject: RE: [Sip-implementors] ReInvite times out, should a Cancel be sent
or not
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
============================================================================
===
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
