On Tuesday 17 June 2014 14:41:03 Joel White wrote:
> case /"^\*\*[0-9]{5}$":
>
> break;
Switch/case works with regexps? My guess would be you are matching literal
"^\*\*[0-9]{5}$" when using it withing a switch($rU) block. Try
if($rU=~"\*\*[0-9]{5}$")
{
}
else if($rU=~)
{
}
...
else
{
}
instea
Can you try with "^\\*\\*[0-9]{5}$" or "^[*]{2}[0-9]{5}$"?
I don't remember by hart how backspace escape is interpreted in the case
statement and have no time for the moment to check the code.
Cheers,
Daniel
On 17/06/14 14:41, Joel White wrote:
case /"^\*\*[0-9]{5}$":
break;
On Mon, Jun 1
Have you looked at the sip traffic, is there an INVITE coming with ** in
the r-uri username?
I know some phones use * for some of their internal feature control.
Cheers,
Daniel
On 17/06/14 14:42, Joel White wrote:
I was not able to make that work yesterday. Could it possibly be an
issue with
I was not able to make that work yesterday. Could it possibly be an issue
with the Polycom dialing rules on the phone itself?
I want to setup some feature codes prefixed with an asterisk
On Tue, Jun 17, 2014 at 8:41 AM, Joel White wrote:
> case /"^\*\*[0-9]{5}$":
>
> break;
>
>
> On Mon, Jun
case /"^\*\*[0-9]{5}$":
break;
On Mon, Jun 16, 2014 at 8:50 AM, Daniel-Constantin Mierla wrote:
> Can you give an example where you try to use it?
>
> In regular expressions you have to escape it with backslash if you want to
> match the character.
>
> Cheers,
> Daniel
>
>
> On 16/06/14 14:21
Can you give an example where you try to use it?
In regular expressions you have to escape it with backslash if you want
to match the character.
Cheers,
Daniel
On 16/06/14 14:21, Joel White wrote:
I am having an issue using an asterisk * in the kamailio routing. How
would I implement this?
I am having an issue using an asterisk * in the kamailio routing. How
would I implement this?
Thank you in advance
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-
