[Spce-user] Contact header Replace - MOdify

[Leopoldo Iglesia]

They are Ericcson  ONT, and i must do this way, if not, no SIP phone 
service available.

I know it´s not the way, but... Two more operators are working like 
this, making the SBC changing this fields.

This sipwise instance will only work with this endpoints.. I know.. but 
It has to be this way. It´s a shared network and.. I must adopt this issues.

El 13/07/2014 11:43, Daniel Grotti escribió:
> Leopoldo,
> you're a playing with a broken endpoint that's completely far away 
> from the SIP specification.
> Again, there is no need to change the contact. Changing contact will 
> break your NGCP.
>
> Daniel
>
>
>
>
> On 07/13/2014 11:37 AM, Leopoldo Iglesia 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
>>> 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 / +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: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
>> http://lists.sipwise.com/listinfo/spce-user
>
>
>
> _______________________________________________
> Spce-user mailing list
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140713/b7391f6e/attachment.html>