Hi Tarun, I am seeing this problem from a user-perspective. Since, these are user-initiated moves (HOLD/RESUME), should we wait for user to hang on the call? I believe we have standard procedure to tear-down call once user hangs up.
Also, since there are several proxies involved and as suggested down the line there could be a scenario of active proxy going down and slave taking over, the session could be back (I agree this could be bad user experience, since there will be delay in RESUMING call). IMO, this is already a solved problem with user intervention. Opinions are welcome. Thanks, Manju -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tarun2 Gupta Sent: Friday, 08 June, 2012 3:50 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
