Daniel,
I just did some tests the same way as Duarte’s and the parameter I think you mentioned ({uri.uparam}:
“Return the value of user parameter”) does not work as expected:
URI sip:123456789;test=param;phone-context=abcd@1.1.1.1;user=phone
$(var(URI){uri. uparam}) = "phone"
URI sip:123456789;test=param;phone-context=abcd@1.1.1.1
$(var(URI){uri. uparam}) = ""
Am I missing something?
--
Julien
De : sr-users <sr-users-bounces@lists.kamailio.org> au nom de Duarte Rocha <duarterocha91@gmail.com>
Répondre à : "Kamailio (SER) - Users Mailing List" <sr-users@lists.kamailio.org>
Date : lundi 18 novembre 2019 à 14:19
À : Daniel-Constantin Mierla <miconda@gmail.com>
Cc : "Kamailio (SER) - Users Mailing List" <sr-users@lists.kamailio.org>
Objet : Re: [SR-Users] Problem with URI transformations
As far as i know, the URI transformations only provide the "user" parameter, not the user part parameters.
What i'm trying to do i build an object for Diversion and Contact. To do that i'm trying to parse the header and URI into it's elements.
URI Example : <sip:123456;parameter=hello;parameter2=hey@1.1.1.1;kamailio=test>
Elements :
User : 123456
User Parameters : parameter=hello;parameter2=hey
Domain : 1.1.1.1
URI Parameters = kamailio=teste
To achieve this i'm using uri.user , uri.domain , uri.port and uri.params.
uri.user will normally return "123456;parameter=hello;parameter2=hey" and after that i mannually split the user and teh user params. However, in the event of a TEL_URI with user=phone on uri.params, "parameter=hello;parameter2=hey" won't
be present in the uri.user.
It seems like i should be doing a special case for when user=phone is present. What do you think ?
A segunda, 18/11/2019, 12:29, Daniel-Constantin Mierla <miconda@gmail.com> escreveu: