Hi Dale Thanks for the response.
Referring to RFC 5359, my question is regarding F15 containing sipfrag body with "SIP/2.0 488 Not acceptable". 1) Do any commercial UACs use this sipfrag body in un-attended transfer case. If yes, could anybody point me to some UE like this. 2) What kind of actions can a UAC take in F15 containing sipfrag body with failure response case like "SIP/2.0 4xx " ???? Thanks Gagandeep Bajaj -----Original Message----- From: Dale Worley [mailto:[email protected]] Sent: Saturday, February 27, 2010 4:55 AM To: Bajaj, Gagandeep Cc: [email protected] Subject: Re: [Sip-implementors] Unattended Call Transfer (I assume you are referring to RFC 5359 section 2.4.) On Fri, 2010-02-26 at 14:17 +0530, Bajaj, Gagandeep wrote: > Bob sends NOTIFY "terminated" (15th message) to inform Alice that he has > successfully connected with Carol. Beware that it in F15, it is not "Subscription-State: terminated" that indicates that the transfer was successful, but rather the "SIP/2.0 200 OK" in the sipfrag body. > 1) Why after doing an unattended transfer and sending BYE to Bob, > Alice would be interested in the last NOTIFY? Because Alice should not send BYE to Bob, but rather wait for Bob to send BYE (when the dialog to Carol becomes established). > 3) If say NOTIFY "terminated" body contains "Failure response to > Bob-Carol INVITE", what action Alice takes (generally seen) ?? The UA can show the call to Bob as "on hold" in the user interface, so that the user can connect to the call and attempt to do something useful. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
