[OpenSIPS-Users] cut a string at special char

2014-05-21 Thread Mike Claudi Pedersen
is there a transformation that allows me to cut a str at a spcial char like @ or * i need this to be able to cut a certain pice from a string sometime its +0212345678*234 and sometimes its +021122345678*234 and this makes it hard to use the {s.substr,x,y} transformation a 2nd question. in special

Re: [OpenSIPS-Users] cut a string at special char

2014-05-21 Thread Liviu Chircu
Hello Mike, 1) the best solution for this is the "s.select" transformation [1] 2) if you want to extract the user from the Diversion URI, you can use the "uri.user" transformation [2] [1]: http://www.opensips.org/Documentation/Script-Tran-1-12#toc6 [2]: http://www.opensips.org/Documentation/Sc

Re: [OpenSIPS-Users] cut a string at special char

2014-05-21 Thread Răzvan Crainea
Hi, Mike! Pay attentions that you can not simply write the $fU variable. Instead, you should re-construct the From URI with the correct username and replace the whole URI using uac_replace_from() function[3]. [3] http://www.opensips.org/html/docs/modules/1.12.x/uac#id293710 Best regards, Ra

Re: [OpenSIPS-Users] how to construct a new uri from 2 variables

2014-05-21 Thread kostenftw
im trying to do it like this but i get an error i cant see or figure out, had it working when only using SIP: and 2 avps, but with this i cant seem to get the config running, is there any limits to how i can format this? $ru = "sip:" + $tU + "*" + $avp(COID) "@" + $avp(COIP); when i use xlog i ge

Re: [OpenSIPS-Users] how to construct a new uri from 2 variables

2014-05-21 Thread kamika
You forgot plus sign here: $ru = "sip:" + $tU + "*" + $avp(COID) "@" + $avp(COIP); Must be like this $ru = "sip:" + $tU + "*" + $avp(COID) + "@" + $avp(COIP); -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/how-to-construct-a-new-uri-from-2-variables-

Re: [OpenSIPS-Users] how to construct a new uri from 2 variables

2014-05-21 Thread kostenftw
thank you thank you thank you ! i stared myself blind, and cimply couldnt find the error, is there any good codehandler to write the config in, for bugfinding etc? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/how-to-construct-a-new-uri-from-2-variables-

Re: [OpenSIPS-Users] how to construct a new uri from 2 variables

2014-05-21 Thread kamika
I use WinSCP and PsPAD as an editor. Seems to me ok when use Perl syntax editor. Regards; -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/how-to-construct-a-new-uri-from-2-variables-tp7591444p7591482.html Sent from the OpenSIPS - Users mailing list archi

[OpenSIPS-Users] strange active dialogs

2014-05-21 Thread Jorge Ortea
Hi all, when I execute 'opensipsctl fifo dlg_list' shows this: dialog:: hash=206:862937179 state:: 2 user_flags:: 0 timestart:: 0 timeout:: 0 callid:: 786344563@A.B.C.D from_uri:: sip:x@MyDomain to_uri:: sip:y@MyDomain caller_tag:: 356538242 ca

[OpenSIPS-Users] [Event] OpenSIPS Summit 2014, Chicago

2014-05-21 Thread Bogdan-Andrei Iancu
It's almost that time again! The first of two OpenSIPS summits has been scheduled for *4th of August 2014, at InterContinental Chicago, Chicago, IL, USA*. This Summit will coincide with annual FreeSwitch Cluecon conference being held Aug 5th - 7th at the same location. This year's summit wil

Re: [OpenSIPS-Users] strange active dialogs

2014-05-21 Thread Liviu Chircu
Hello Jorge, Just as RFC3261 says, 1XX responses create "early dialogs", while 2XX final responses create "dialogs". OpenSIPS follows the same rules, only that it considers that the "true" lifetime of a dialog begins when the callee picks up his/her phone. That is why those fields are still un

[OpenSIPS-Users] Use of MemCache to Store Static Routing Info?

2014-05-21 Thread Will Bazdarich
Thanks in advance for looking, I have a simple set up here in NorAM that does LNP look ups as well as some simple routing logic based on the Originating and Terminating state from the LERG database. I have been thinking that it is overkill and more resource intensive than necessary to store the