[Spce-user] Contact header Replace - MOdify

[Leopoldo Iglesia]

I know, but there is no propperly implemented endopoint, cause all are 
the same way, endpoints are provided by the ftth operator and all 
behaves the same way. This is why I need to do this, and, i tried with 
Contact=........ but no modification at all.

If a put a middleware instance I´ll have the same problem, the how-to do 
it ;)

El 13/07/2014 11:56, Lorenzo Mangani escribió:
> Leopoldo,
>
> This sounds quite honestly insane - I know of GPON FTTH endpoints 
> (triple-play boxes etc) handling this properly, so it is not a general 
> issue to justify such approach, rather the endpoint handling this as a 
> direct IP call due to its config possibly - but call presentation is 
> an ENDPOINT preference at the end of the day, it does not justify for 
> killing a standard on the server. If you already tried using/sending 
> the proper Caller-ID presentation headers (as Daniel pointed, also in 
> previous instances of this case) I would suggest handling this 
> horrible exception outside of the CE (start a separate middleware 
> Kamailio instance to try take care of this unlikely transformation 
> towards the peer, or use another b2bua toward the endpoints) without 
> jeopardizing the SPCE core functionality and without breaking SIP for 
> all the properly implemented endpoints.
>
>
>
> 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 <mailto:get at pcapture.com>
>
>
>
>
>
> On Sun, Jul 13, 2014 at 11:37 AM, Leopoldo Iglesia 
> <liglesia at por-aire.es <mailto:liglesia at por-aire.es>> wrote:
>
>     they are GPON specific FTTH endpoints, no way to mod them.
>     Provider specific.
>
>     Call work, but caller ID is taken from Contact, so NGCP-LB is
>     displayed. I need wo swap From  - Contact fields to manage this issue.
>
>
>     El 13/07/2014 11:34, Lorenzo Mangani escribió:
>>     Leopoldo,
>>
>>     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?
>>
>>     Best,
>>
>>     Lorenzo Mangani
>>
>>     HOMER / PCAPTURE DEV TEAM
>>     Desk: +31 20 8080468 / +1 202-632-7227 <tel:%2B1%20202-632-7227>
>>     Mobile: +31 6 4603-2730
>>
>>     QXIP BV - Capture Engineering
>>     Amsterdam, The Netherlands
>>     get at pcapture.com <mailto:get at pcapture.com>
>>
>>
>>
>>
>>
>>     On Sun, Jul 13, 2014 at 11:28 AM, Leopoldo Iglesia
>>     <liglesia at por-aire.es <mailto:liglesia at por-aire.es>> wrote:
>>
>>         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ó:
>>>         Leopoldo,
>>>
>>>         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:
>>>
>>>         #Contact=<sip:$Ri>
>>>
>>>         Link:
>>>         https://github.com/sipwise/sems/blob/master/apps/sbc/etc/transparent.sbcprofile.conf
>>>
>>>
>>>         Best,
>>>
>>>         Lorenzo Mangani
>>>
>>>         HOMER / PCAPTURE DEV TEAM
>>>         Desk: +31 20 8080468 <tel:%2B31%2020%208080468> / +1
>>>         202-632-7227 <tel:%2B1%20202-632-7227>
>>>         Mobile: +31 6 4603-2730 <tel:%2B31%206%204603-2730>
>>>
>>>         QXIP BV - Capture Engineering
>>>         Amsterdam, The Netherlands
>>>         get at pcapture.com <mailto:get at pcapture.com>
>>>
>>>
>>>
>>>
>>>
>>>         On Sun, Jul 13, 2014 at 11:04 AM, Leopoldo Iglesia
>>>         <liglesia at por-aire.es <mailto:liglesia at por-aire.es>> wrote:
>>>
>>>             Hi!
>>>
>>>             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?
>>>
>>>             Thanks
>>>
>>>
>>>
>>>             _______________________________________________
>>>             Spce-user mailing list
>>>             Spce-user at lists.sipwise.com
>>>             <mailto:Spce-user at lists.sipwise.com>
>>>             http://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>
>>
>>         _______________________________________________
>>         Spce-user mailing list
>>         Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>         http://lists.sipwise.com/listinfo/spce-user
>>
>>
>
>
>     _______________________________________________
>     Spce-user mailing list
>     Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>     http://lists.sipwise.com/listinfo/spce-user
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140713/5aa43181/attachment-0001.html>