Re: [SR-Users] Uri transformations stopped working after upgrade from 3.3 to 4.1.6.

On 30/09/14 11:46, Julia Boudniatsky wrote: $(tu{uri.uparam,cic}) gets ERROR wrong format, $(tu{uri.uparam}) return : phone So, uparam return the value of parameter "user" . Right, I forgot what I implemented and misread the docs. You should add a transformation to return the user paramete

Re: [SR-Users] Uri transformations stopped working after upgrade from 3.3 to 4.1.6.

$(tu{uri.uparam,cic}) gets ERROR wrong format, $(tu{uri.uparam}) return : phone So, uparam return the value of parameter "user" . I solved a problem by usage $(tu{param.value,cic,;}) BR Julia On Tue, Sep 30, 2014 at 12:09 PM, Daniel-Constantin Mierla < mico...@gmail.com> wrote: > Hello, >

Re: [SR-Users] Uri transformations stopped working after upgrade from 3.3 to 4.1.6.

Hello, On 30/09/14 10:41, Julia Boudniatsky wrote: Hello, Some Uri transformations stopped working after upgrade from 3.3 to 4.1.6. *To: ;user=phone>* _In v3.3_ $tu({uri.params}) return:cic=012;csel=noind $tu({uri.param,cic}) return: 012 _

[SR-Users] Uri transformations stopped working after upgrade from 3.3 to 4.1.6.

Hello, Some Uri transformations stopped working after upgrade from 3.3 to 4.1.6. *To: http://noind@10.25.153.150:5060>;user=phone>* *In v3.3* $tu({uri.params}) return: cic=012;csel=noind $tu({uri.param,cic}) return:012 *In v4.1.6* $tu({uri.params}) r