Hello , Yes, it seems I have not mentioned the full messages flow here. Here I explain, On receiving REFER, AS imediately sends NOTIFY(202 Accepted). Then AS can sends from following (RFC 3515, 2.4.5 The Body of the NOTIFY) depending on Call Flow In case of some Error follwoing: - SIP/2.0 503 Service Unavailable - SIP/2.0 603 Declined
In case Call is tried to C (sending INVITE to C) - SIP/2.0 100 Trying and when the call is answered: - SIP/2.0 200 OK After the NOTIFY(200 OK), AS sends the BYE to A. In case there is race and A also sends BYE on receving,NOTIFY(200 OK) it's discarded at lower level and AS is not informed. But still I am not understanding making Media Inactive for A. For B we can play some music (by MRF) when C is ringing. -- Thanks & Regards Parveen Verma On Wed, Feb 26, 2014 at 10:33 PM, Brett Tate <br...@broadsoft.com> wrote: > Hi Paul, > > Yes; I likely misinterpreted the meaning of "NOTIFY (200 OK)" within the > question. > > I also agree that some devices behave as you and Parveen mentioned. I'm > not aware of the behavior explicitly documented within an RFC. RFC 5359 > does document it that way for attended transfer; however it doesn't > document a transfer failure recovery. > > Thanks, > Brett _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
