[SR-Users] Error parsing parameter value

[Duarte Rocha]

Yes, i think both ways are correct

The only problem is that i want to have the real value using {uri.param}
which would be "<urn:uid:00000000000000>".
However it only returns <urn:uid:00000000000000>, without the quotes.

A terça, 8/10/2019, 15:54, Daniel-Constantin Mierla <miconda at gmail.com>
escreveu:

> The example you gave with the value of +sip.instance between double quotes
> is valid, I have seen it many times like this.
>
> On the other hand, other parameters of Contact header can usually be
> without quoted value, like:
>
> Contact:<sip:user at domain>;reg-id=1
>
> Both types can be in the header at the same time.
>
> Is the value with double quotes making troubles somewhere?
>
> Cheers,
> Daniel
> On 08.10.19 16:38, Duarte Rocha wrote:
>
> Thank you for your answer.
> The green example was just for testing. My real example is similar to
> yellow on a header parameter since i have a client sending me the value of
> sip.instance between quotes and i can't identify the value when it is
> quoted.
>
> Example : Contact:<sip:user at domain>
> ;+sip.instance="<urn:uid:00000000000000>"
>
> It seems to me be a valid sip parameter, but if it's not i'll warn the
> client
>
> A terça, 8/10/2019, 15:29, Daniel-Constantin Mierla <miconda at gmail.com>
> escreveu:
>
>> Hello,
>>
>> the values of parameters can be quoted or unquoted, depending on the
>> format (e.g., URI parameters have to be unquoted). If they start with a
>> quote, then it has to be terminated with the same quote and then the value
>> is in between the quotes. The {param} transformation is using the same
>> parser as for parameters in SIP message.
>>
>> Now, I am not sure if quote is allowed in an unquoted parameters like
>> green, the grammar in SIP specs has to be checked...
>>
>> Cheers,
>> Daniel
>> On 08.10.19 16:09, Duarte Rocha wrote:
>>
>> Hi David.
>>
>> I want to ble able to print : yellow = "twelve".
>> In the green example the "" are printed, but on the yellow example it is
>> not.
>>
>> Cheers
>>
>> A terça, 8/10/2019, 12:36, Duarte Rocha <duarterocha91 at gmail.com>
>> escreveu:
>>
>>> Greetings,
>>>
>>>
>>>
>>> I'm testing some parameters actions and i found a weird behaviour
>>>
>>>
>>>
>>> This is my code for the test :
>>>
>>>
>>>
>>> $var(Parameter_List) = "blue=twelve;green=twe\"lve\";yellow=\"twelve\"";
>>>
>>> xerr("Parameter List = $var(Parameter_List)");
>>>
>>> xerr("Value of Parameter blue =
>>> $(var(Parameter_List){param.value,blue})");
>>>
>>> xerr("Value of Parameter green =
>>> $(var(Parameter_List){param.value,green})");
>>>
>>> xerr("Value of Parameter yellow =
>>> $(var(Parameter_List){param.value,yellow})");
>>>
>>>
>>>
>>>
>>>
>>> The printed logs are the following :
>>>
>>> ERROR: <script>: Parameter List =
>>> blue=twelve;green=twe"lve";yellow="twelve"
>>>
>>> ERROR: <script>: Value of Parameter blue = twelve
>>>
>>> ERROR: <script>: Value of Parameter green = twe"lve"
>>>
>>> ERROR: <script>: Value of Parameter yellow = twelve
>>>
>>>
>>>
>>> I have also tried setting the string as :
>>>
>>> $var(Parameter_List) = 'blue=twelve;green=twe"lve";yellow="twelve"';
>>>
>>> But the results were similar
>>>
>>> The "" are not recognized in some scenarios. Is this intended behaviour
>>> or should i submit it as a bug?
>>>
>>>
>>>
>>>
>>>
>>> Best Regards,
>>>
>>>
>>>
>>> Duarte Rocha
>>>
>>>
>>>
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing Listsr-users at lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat
>>
>> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191008/eb4174d2/attachment.html>