On Wed, 2009-03-25 at 03:29 -0400, Hadriel Kaplan wrote: > IMO the UAC has no right to know any such thing. It has no rights - > it's not a human. The calling human has a right to know the far-end > called human it got delivered to. But they don't care nor have a > right to know the *host* element it got delivered to, or host elements > it forked to but did not succeed at, etc. It's none of their > business, frankly. > > And if we're thinking the far-end terminating Enterprise or provider > will want to tell some originating Enterprise or provider what's going > on inside their network, well... once again we all live in different > worlds. :)
I'm sure we live in different worlds. But there are considerable situations where the UAC's owner, or the enterprise or service provider supervising the UAC has rights to know quite a bit. The obvious case is when the owner has contracted with the transit network to provide particular intelligent routing services -- they're going to want to be able to verify that the transit network is performing as contracted. To construct a more interesting case, one that will be a reasonable business case within a year or two: - a UAC within an enterprise network - a transit network from the enterprise to a provider of intelligent call routing - the provider of intelligent call routing - another transit network from the provider to a destination enterprise - a UAS within the destination enterprise network Each of the last 4 operations may want to hide the details of its network, but the originator of the call should have the right (assuming that it's contracting for these services) to monitor the four connections between these networks. Dale _______________________________________________ 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
