Re: [SR-Users] possible bug on {param.value,name}

Hello Daniel, Yes, initially my question was about the tcpops returning an error, but then i realized i was passing the parameter as it was returned by $var(conid) = $(hdr(Route){uri.param,wsconnid}) Which had an extra ">" at the end. But the problem wasn't really with the tcpops function, but

Re: [SR-Users] possible bug on {param.value,name}

The email written by you, to which I replied, had: """ but now i'd really like to understand why $var(whatever) which contains "4" would result in: ERROR: [core/sr_module.c:1638]: get_int_fparam(): Could not convert PV to int ERROR: tcpops [tcpops_mod.c:374]: w_tcp_conid_state(): invalid parame

Re: [SR-Users] possible bug on {param.value,name}

Not really, the question was about $var(conid) = $(hdr(Route){uri.param,wsconnid}) which returns an extra ">" from: Route: if i print $var(conid) i would get: May 3 19:24:45 ip-10-231-32-37 /usr/sbin/kamailio[10015]: ERROR:

Re: [SR-Users] possible bug on {param.value,name}

The question was about the tcpops function, because that one printed the logs. Cheers, Daniel On 04.05.21 15:15, David Villasmil wrote: > I was using it like: > > $var(conid) = $(hdr(Route){uri.param,wsconnid}{s.int }) > > Regards, > > David Villasmil > email: david.villasmil.w...@g

Re: [SR-Users] possible bug on {param.value,name}

I was using it like: $var(conid) = $(hdr(Route){uri.param,wsconnid}{s.int}) Regards, David Villasmil email: david.villasmil.w...@gmail.com phone: +34669448337 On Tue, May 4, 2021 at 7:24 AM Daniel-Constantin Mierla wrote: > Hello, > > you have to show how you use the function and pass the pa

Re: [SR-Users] possible bug on {param.value,name}

Hello, you have to show how you use the function and pass the parameters to it. Cheers, Daniel On 04.05.21 00:27, David Villasmil wrote: > That did the trick (and adding the s.init) > > $var(conid) = $(hdr(Route){nameaddr.uri}{uri.param,wsconnid}{s.int > }); > > Now, i understand u

Re: [SR-Users] possible bug on {param.value,name}

That did the trick (and adding the s.init) $var(conid) = $(hdr(Route){nameaddr.uri}{uri.param,wsconnid}{s.int}); Now, i understand uri.param returning and extra ">". but now i'd really like to understand why $var(whatever) which contains "4" would result in: ERROR: [core/sr_module.c:1638]: get

Re: [SR-Users] possible bug on {param.value,name}

You should try something like this: $var(wsconnid) = $(hdr(Route){nameaddr.uri}{uri.param,wsconnid}) First you need to extract the URI, and then the URI parameter. The param.value transformation is expecting a true param list, not uri or nameaddress. Regards, Ovidiu Sas On Mon, May 3, 2021 at 3:

[SR-Users] possible bug on {param.value,name}

Hello guys, I'm possible using this wrong, but here it is; I need to get a previously set parameter to rr, named "wsconnid": $var(wsconnid) = $(hdr(Route){param.value,wsconnid}) xlog("L_ERR", "Connection ID parameter: $var(wsconnid)"); And i'm getting: May 3 19:24:45 ip-10-231-32-37 /usr/sbin/