> -----Original Message----- > From: Dean Willis [mailto:[EMAIL PROTECTED] > Sent: Monday, November 17, 2008 10:18 AM > > What IS important is that we understand that no such feature can be > made to work with an SBC that is actively disrupting it. We already > wrote specs that said "Don't do this", and they did it anyhow, so why > should we expect them to cooperate the next time? Rational or not, > there are reasons for most of this behavior.
There are reasons people change Call-ID's, and reasons people change To-URI, From-URI, contact-URI, SDP, etc. Absolutely. If you need some mechanism Foo, and the purpose or use or syntax of Foo goes against the wishes of the owner of an SBC, then be prepared for Foo to not work or be changed. That is kinda the point of an SBC after all: control. When it comes to a "call identifier string", which is unique for each high-level "call", I don't think that goes against the wishes of most SBC owners, or B2BUA owners. It just can't identify the IP-Address/hostname/port of the UA or anything really, should not be a URI, should not be in a body, and should not be overly long. -hadriel _______________________________________________ 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
