[SR-Users] Altering received parameter in Contact

[David Cunningham]

Hi Alex,

We already had this line in our kamailio.cfg:
modparam( "nathelper|registrar", "received_avp", "$avp(RECEIVED)" )

We do need to change the received parameter conditionally depending on the
user agent, and the following seems to work:
if ( $ua =~ "ewb2bua" ) {
    avp_subst( "$avp(RECEIVED)", "/(.*);transport=TLS/\1/i" );
}

Can you see any issues with this?

Thank you!


On Wed, 30 Jan 2019 at 10:50, David Cunningham <dcunningham at voisonics.com>
wrote:

> Hello everyone who replied, and thank you for your advice! We will try the
> suggestions given.
>
>
> On Wed, 30 Jan 2019 at 01:34, Alex Balashov <abalashov at evaristesys.com>
> wrote:
>
>> Hi David,
>>
>> Well, the registrar's 200 OK should include the very Contact binding
>> that was stored for the given AOR, and for a TLS registrant, that's
>> going to unavoidably contain the ;transport=TLS attribute, because TLS
>> is not the default presumed transport in the absence of a ;transport
>> attribute.
>>
>> If the issue is specifically with the occurrence of ;transport=TLS in
>> the 'received' parameter, that can be modulated here:
>>
>>
>> https://kamailio.org/docs/modules/5.2.x/modules/registrar.html#registrar.p.received_param
>>
>> And if it needs to be controlled on a situational/per-registration
>> basis, one can use the AVP:
>>
>>
>> https://kamailio.org/docs/modules/5.2.x/modules/registrar.html#registrar.p.received_avp
>>
>> If you set it to empty for a registration from a certain type of device,
>> the parameter will not be populated and thus not reflected back to the
>> registering UA.
>>
>> -- Alex
>>
>> On Tue, Jan 29, 2019 at 03:28:38PM +1300, David Cunningham wrote:
>>
>> > Hello,
>> >
>> > I'm hoping someone can give advice on altering the received parameter in
>> > the Contact header on a reply. The situation is that a customer is
>> > REGISTERing using TLS, and our Kamailio replies with a 200 OK that
>> includes
>> > a Contact header like this:
>> >
>> > Contact: <sip:123456789 at xx.xx.102.10
>> >
>> :5061;transport=tls>;expires=3600;received="sip:xx.xx.102.10:36051;transport=TLS"
>> >
>> > The customer's device apparently had an issue with this, and the device
>> > manufacturer advises that they need the ";transport=TLS" on the received
>> > parameter removed. This sounds like a strange requirement, but it's what
>> > we've been told. Does anyone know how to alter this in a Kamailio
>> > configuration?
>> >
>> > Our system uses www_authorize to authenticate and is running Kamailio
>> 4.2.1.
>> >
>> > Thanks in advance for any help!
>> >
>> > --
>> > David Cunningham, Voisonics Limited
>> > http://voisonics.com/
>> > USA: +1 213 221 1092
>> > New Zealand: +64 (0)28 2558 3782
>>
>> > _______________________________________________
>> > Kamailio (SER) - Users Mailing List
>> > sr-users at lists.kamailio.org
>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Alex Balashov | Principal | Evariste Systems LLC
>>
>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
> --
> David Cunningham, Voisonics Limited
> http://voisonics.com/
> USA: +1 213 221 1092
> New Zealand: +64 (0)28 2558 3782
>


-- 
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190130/5d198d89/attachment.html>