Bogdan, On Wed, Feb 11, 2009 at 10:27 AM, Bogdan-Andrei Iancu <[email protected]> wrote: > Hi Victor, > > I think this "limitation" is part of the mechanism :). > > it is the same as for secure sip and TLS - if you get on the path a node > with not TLS support, the call will fail. In this case, if a hop does not > understand SIP identity and changes the message, the call will be denied.
You are right. Just for the sake of completeness for other readers: draft-elwell-sip-e2e-identity-important provides a good description for the above mentioned limitations http://tools.ietf.org/html/draft-elwell-sip-e2e-identity-important-02#section-3.5 Regards, -- Victor Pascual Ávila _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
