It is implemented in our A5020 softswitch. Regards, Nadine.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Kyzivat Sent: vrijdag 16 november 2007 4:03 To: [EMAIL PROTECTED] Cc: [email protected] Subject: Re: [Sip-implementors] how to prevent forking? 라스토기 wrote: > Request-Disposition of RFC 3841 prevents or guides forking. Hope it helps .... I've never heard of anyone implementing that. Has anybody? Thanks, Paul > Vipul Rastogi > Engineer, Business Management Team > Telecommunication Network Business > Samsung Electronics CO, LTD > Suwon P.O.BOX 105, 416 > Korea 442-600 > MO 010-9530-0354 > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Friday, November 16, 2007 9:06 AM > Subject: Re: [Sip-implementors] how to prevent forking? > > >> From: "Anshuman S. Rawat" <[EMAIL PROTECTED]> >> >> I am not aware of any standard mechanism of how to prevent forking and >> googling didn't help. Could anyone please point me to a relevant rfc/draft >> of how to do this? >> >> 1) Send the REFER within an existing dialog. >> >> 2) Send the REFER to a URI known to be a GRUU. >> >> 3) Send the REFER to a URI which has been provided by a UA as its >> Contact URI. >> >> Dale >> _______________________________________________ >> 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 > _______________________________________________ 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
