[Spce-user] Contact header Replace - MOdify
lorenzo.mangani at gmail.com
Sun Jul 13 05:34:08 EDT 2014
Rather than helping you break the switch and staying cryptic - what are
those endpoints specifically, and do you have some traces to share for
successful and failing calls?
HOMER / PCAPTURE DEV TEAM
Desk: +31 20 8080468 / +1 202-632-7227
Mobile: +31 6 4603-2730
QXIP BV - Capture Engineering
Amsterdam, The Netherlands
get at pcapture.com
On Sun, Jul 13, 2014 at 11:28 AM, Leopoldo Iglesia <liglesia at por-aire.es>
> There is no other way with this endpoints, as the network manager told.
> I have to swap Sip header fields.
> But, I already created a custom tt2 with Contact=<sip:$Ri> ... and no
> modifications at all when calling.
> Don´t know why.
> El 13/07/2014 11:23, Lorenzo Mangani escribió:
> SEMS supports modifying the Contact header as shown in their example
> sbcprofile.conf (which will likely be the wrong approach as well as the
> easiest way to demolish your routing when not done properly) but since the
> underlying SIP issue is not clear to you either apparently so far, I would
> strongly suggest investigating other options first - having the Caller ID
> in the contact header surely outlines an issue with your setup/endpoints
> and not the CE. This being said:
> Lorenzo Mangani
> HOMER / PCAPTURE DEV TEAM
> Desk: +31 20 8080468 / +1 202-632-7227
> Mobile: +31 6 4603-2730
> QXIP BV - Capture Engineering
> Amsterdam, The Netherlands
> get at pcapture.com
> On Sun, Jul 13, 2014 at 11:04 AM, Leopoldo Iglesia <liglesia at por-aire.es>
>> I´m trying to modify Contact header info in SEMS config, but no working.
>> I´m with 2.8 sipwise.
>> I need to change, cause the endpoint requires from user ID to decode
>> Caller ID on the contact header.
>> Sip issues... don´t know why is done this way, but I need to change it.
>> Other operators are doing so, so it seems SBC can do it.
>> Any help on this?
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
> Spce-user mailing list
> Spce-user at lists.sipwise.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Spce-user