Elwell, John wrote:
Vijay,
This deals with straightforward forking scenarios.
OK; good.
What about a proxy that is scripted to fork in parallel to two
destinations, and then, if they both fail to answer, fork to a third
destination? Or a proxy that is scripted to forward to one
destination, and then, if it fails to answer after a certain time,
fork to a second location without cancelling the request at the first
destination?
Presumably, if the proxy understands the "Proxy-Require: sipsec"
option tag, it will follow the normative behavior of returning
the destinations in a 3xx instead of launching into the fork dance.
If it is a legacy proxy, it should reject the CONNECT request
on encountering a "Proxy-Require: sipsec" option tag.
Thanks.
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: [EMAIL PROTECTED],bell-labs.com,acm.org}
WWW: http://www.alcatel-lucent.com/bell-labs
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
