On Wed, Aug 18, 2010 at 11:38 AM, Heather L. Sanders <hlsan...@svsu.edu> wrote: > The 'From' header info and the 'PAI' header info are flipped around in > 4.2.1.
I found the offending code and only way to fix this for everyone is to invent yet another setting to set the From header to a fixed value. In my case setting up toplink.de ITSP, the PAI needed to be caller id and From header had to be ITSP registration info. In your case, you need PAI to be ITSP registration info and From to original caller. Did I get that right? I'm sure you said this, just triple checking. Anyway, I'll have a fix maybe today but definitely this week. Heather can I give you an RPM to try before I publish to official repo? Aside: What is clearly needed here is a more flexible way to rewrite incoming and outgoing SIP messages in sipXbridge other than invent a new hard-to-understand setting for every ITSP. In sipXbridge's case only, RFC compliant or not, just put the control in admin's hands. I know it's more complicated than just rewriting SIP messages and this gets into call flow, and I know Ranga refactored sipXbridge in 4.3 regarding RFC compliance and backdooring non-compliance, so I'm probably over simplying the issue. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
