>>>>> Stephan Steiner <[EMAIL PROTECTED]> wrote: > I have a SIP PBX which works in B2BUA mode and I've noted that when it comes > to dealing with Header fields, it doesn't stick to the table 2 in chapter > 20.1 of RFC 3261. Specifically, it is modifying some header fields which > according to that table may not be modifed by a proxy. I contacted the > manufacturer and they claim that since a B2BUA isn't a proxy, they don't > have to follow the rules established in the RFC Right.
> and I'm having a hard time > countering that since to me, a B2BUA is a proxy seeing as it does what a > proxy does (even if the RFC doesn't spell that out) Wrong. > but I'm wondering: > Is there any type of UAS to which the header processing rules mentioned > before do not apply? Is B2BUA really a loophole to not do things a proxy > should do just because it isn't a real proxy per definition (even though it > basically does the same things.. it just does more than a proxy does)? Yes, it can change RURI, do hunting of multiple destination sequence, rewrite bodies, interrupt a call if it is too long, & so on & so forth. -- Valentin Nechayev PortaOne Inc., Software Engineer mailto:[EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
