On 11/20/08 2:40 PM, Hadriel Kaplan wrote:
-----Original Message-----
From: Adam Roach [mailto:[EMAIL PROTECTED]
I'm not saying "stop changing Call-IDs." It's true that that's what I
*want* to happen, but it's not the only way this can be made to work.
I'm saying "if you must, for business reasons, change Call-IDs going
into and out of a network, make sure you perform the same mapping into
and out of the network when you see the dialog event package." Again,
this is something with value for the carrier itself, as it allows new
services (such as call completion).
Ohhh. But that's not the problem. At least I hope that's not what people are
talking about. Most B2BUA's will map them back just fine. The issue is your
message may not go through *that same* B2BUA.
If the message is in-dialog, no problem.
If the message is out-of-dialog but uses the Contact-URI to route to, no problem (because the b2bua's replace that to be themselves).
But those B2BUAs are all in the same administrative domain. Given that
fact, there are solutions to the problem, such as synchronized minimal
state -- or, preferably, stateless reversible dialog identifier
transformations. These things are pretty easy to implement at B2BUAs.
And, if the market finds a use for the dialog event package, you'll need to.
I mean, really. You're smart. If someone offers you enough money to make
this work in your product, you'll figure it out.
/a
_______________________________________________
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
