Hi,

See Request-Disposition:

RFC 3841.


Anshuman S. Rawat wrote:
> Hi All,
>
> While reading RFC 4488 (Suppression of SIP REFER Method Implicit 
> Subscription), I came across this line (in section 5)
>
> "The REFER-Issuer SHOULD use standardized mechanisms for ensuring the REFER 
> request does not fork."
>
> 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?
>
> Thanks,
> Anshuman 
>
> _______________________________________________
> 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

Reply via email to