On Oct 20, 2008, at 9:37 AM, Orsic, Milo (Milo) wrote:
Hi Christer,
IMHO outbound should specifies "alternative paths". Here is what I
mean by "alternative paths".
Assume that China Airline has two counters (contacts), one only
English speaking the other only Chinese spiking. It doesn't matter
if you took either the escalator or the elevator to the English
speaking counter (the elevator and escalator are alternatives
paths). However, if the elevator gets you to English speaking
counter and the escalator gets you to Chinese speaking counter -
they are not alternatives.
Hence, you have two choices, i.e. either
1. the two alternatives get you to the same counter, or
2. make the second counter also English speaking.
My choices is 1. (e.g. I don't want to be constrained that the
alternative contact addresses must be registered with the same
feature tags).
The English and Chinese counters are different instances, with
different capabilities tags. They are not the sort of things that
Outbound considers alternate flows.
Of course, with SIP, you'd be cloned for each counter, with one clone
put on the elevator, one clone put on on the escalator, and the
original you discarded into the bit void.
--
Dean
_______________________________________________
Sip mailing list https://www.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
