Altering received parameter in Contact

List overview All Threads
Download

newer

older

Planing the release of Kamailio...

Kamailio TCP/TLS Connection...

David Cunningham

29 Jan 2019 29 Jan '19

5:28 a.m.

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@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

Attachments:

attachment.html (text/html — 1.4 KB)

Show replies by date

Mojtaba

29 Jan 29 Jan

9:49 a.m.

Hello David, Maybe this would be useful. https://lists.kamailio.org/pipermail/sr-users/2015-November/090595.html With best regards.Mojtaba On Tue, 29 Jan 2019, 06:00 David Cunningham, <dcunningham(a)voisonics.com> wrote:

...

YASIN CANER

11:01 a.m.

Hello, I am not sure so you should test contact_alias function on lab , if you can. First ,set contact alias and remove received parameters from contact header. on reply , use handle contact alias. Kamailio care alias to find right transport protocol. http://kamailio.org/docs/modules/5.2.x/modules/nathelper.html#nathelper.set… Good luck. Yasin CANER ________________________________ From: sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of David Cunningham <dcunningham(a)voisonics.com> Sent: Tuesday, January 29, 2019 5:28 AM To: Kamailio (SER) - Users Mailing List Subject: [SR-Users] Altering received parameter in Contact 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@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

Daniel-Constantin Mierla

12:07 p.m.

Hello, you can disable appending the received parameter to Contact header via a modparam, see: - https://www.kamailio.org/docs/modules/stable/modules/registrar.html#registr… Cheers, Daniel On 29.01.19 03:28, 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@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(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

Alex Balashov

3:29 p.m.

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.… 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.… 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:

...

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)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/

David Cunningham

30 Jan 30 Jan

12:50 a.m.

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(a)evaristesys.com> wrote:

...

includes

a Contact header like this: Contact: <sip:123456789@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(a)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

3:06 a.m.

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(a)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(a)evaristesys.com> wrote:

includes

a Contact header like this: Contact: <sip:123456789@xx.xx.102.10

:5061;transport=tls>;expires=3600;received="sip:xx.xx.102.10:36051;transport=TLS"

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(a)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

Alex Balashov

3:05 a.m.

I don't see any issues with it, no... On Wed, Jan 30, 2019 at 01:06:40PM +1300, David Cunningham 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(a)evaristesys.com> wrote:

includes

a Contact header like this: Contact: <sip:123456789@xx.xx.102.10

:5061;transport=tls>;expires=3600;received="sip:xx.xx.102.10:36051;transport=TLS"

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(a)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

...

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)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/

David Cunningham

5:27 a.m.

Great, thanks for letting me know. On Wed, 30 Jan 2019 at 13:10, Alex Balashov <abalashov(a)evaristesys.com> wrote:

...

I don't see any issues with it, no... On Wed, Jan 30, 2019 at 01:06:40PM +1300, David Cunningham wrote:

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(a)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(a)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.…

>> >> 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.…

>> >> 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@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(a)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

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)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

Daniel-Constantin Mierla

3:55 p.m.

Actually I am a bit more skeptical than Alex on this one and I tend to say that messing with that avp value it is a wrong approach. The value of the received_avp is saved in the location table and used later for sending traffic to that device, so if you remove the transport from there, practically you make Kamailio to use UDP instead of the correct transport, even if that transport is still in the contact address -- obviously, traffic will fail to be routed to the device unless the device is listening on same port for UDP. More than that, when building the Contact headers for 200ok of REGISTER, the value might not be taken from the avp, but from the location table records. For sure that is done in case the user has many devices, because the 200ok has all the Contacts of that device, not only the one for that specific REGISTER request (this is required by SIP specs). Because I haven't developed this part of the code, I cannot say for sure, but again, it is my expectation based on SIP specs and what is done during save() and lookup() of location records. So I strongly recommend at least to test properly before deploying to production or look at the related C code in registrar and usrloc modules to confirm the behaviour you expect. What is for sure is that by setting the modparam received_param to empty, the received parameter is not added to Contact headers of 200ok. It is not impacting at all what Kamailio has to do internally during save() location. The parameter for received_avp is for telling to kamailio what variable to use to store a string build from source ip/port/proto for some operations during save(). Cheers, Daniel On 30.01.19 03:27, David Cunningham wrote:

...

Great, thanks for letting me know. On Wed, 30 Jan 2019 at 13:10, Alex Balashov <abalashov(a)evaristesys.com <mailto:abalashov@evaristesys.com>> wrote: I don't see any issues with it, no... On Wed, Jan 30, 2019 at 01:06:40PM +1300, David Cunningham wrote:

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

<dcunningham(a)voisonics.com <mailto:dcunningham@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(a)evaristesys.com <mailto:abalashov@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.…

>> >> 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.…

>> >> 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@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(a)lists.kamailio.org

<mailto:sr-users@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(a)lists.kamailio.org <mailto:sr-users@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

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@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(a)lists.kamailio.org <mailto:sr-users@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 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

2123

days inactive

2124

days old

sr-users@lists.kamailio.org

Manage subscription

9 comments

5 participants

tags (0)

participants (5)

Alex Balashov
Daniel-Constantin Mierla
David Cunningham
Mojtaba
YASIN CANER