Re: [SR-Users] Issue in Dialplan Module

[Logeshwaran G]

Issue Resolved.. Thanks a lot For you Inputs.

INSERT INTO dialplan(id, dpid, pr, match_op, match_exp, match_len,
subst_exp, repl_exp, attrs) VALUES (2, "1", "2", 1, "^000[0-9]+\\$ ", 0,
"^000([0-9]+)$", "", " ");

Thanks & Kind Regards,
Logeshwaran G

On Thu, Aug 10, 2017 at 10:13 AM, Logeshwaran G 
wrote:

> Hi,
> I have changed the rules as you mentioned
>
> INSERT INTO dialplan(id, dpid, pr, match_op, match_exp, match_len,
> subst_exp, repl_exp, attrs) VALUES (1, "1", "1", 1, "^000[0-9]+$ ", 0,
> "^000([0-9]+)$", "\\1", " ");
>
> Eventhough its failing.
>
> Thanks & Kind Regards,
> Logeshwaran G
>
> On Wed, Aug 9, 2017 at 5:05 PM, Daniel Tryba  wrote:
>
>> On Wed, Aug 09, 2017 at 01:34:13PM +0530, Logeshwaran G wrote:
>> > I have given the below query,
>> >
>> > INSERT INTO dialplan(id, dpid, pr, match_op, match_exp, match_len,
>> > subst_exp, repl_exp, attrs) VALUES (1, "1", "1", 1, "^000[0-9]+$ ", 0,
>> > "^000([0-9]+)$", "\1", " ");
>> >
>> > But the Rule is tking as "1"
>>
>> See
>> https://dev.mysql.com/doc/refman/5.7/en/string-literals.html
>> "Within a string, certain sequences have special meaning unless the
>> NO_BACKSLASH_ESCAPES SQL mode is enabled. Each of these sequences begins
>> with a backslash (\), known as the escape character. MySQL recognizes
>> the escape sequences shown in Table 9.1, “Special Character Escape
>> Sequences”. For all other escape sequences, backslash is ignored. That
>> is, the escaped character is interpreted as if it was not escaped. For
>> example, \x is just x. These sequences are case sensitive. For example,
>> \b is interpreted as a backspace, but \B is interpreted as B. "
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Issue in Dialplan Module

[Daniel Tryba]

On Wed, Aug 09, 2017 at 01:34:13PM +0530, Logeshwaran G wrote:
> I have given the below query,
> 
> INSERT INTO dialplan(id, dpid, pr, match_op, match_exp, match_len,
> subst_exp, repl_exp, attrs) VALUES (1, "1", "1", 1, "^000[0-9]+$ ", 0,
> "^000([0-9]+)$", "\1", " ");
> 
> But the Rule is tking as "1"

See
https://dev.mysql.com/doc/refman/5.7/en/string-literals.html
"Within a string, certain sequences have special meaning unless the
NO_BACKSLASH_ESCAPES SQL mode is enabled. Each of these sequences begins
with a backslash (\), known as the escape character. MySQL recognizes
the escape sequences shown in Table 9.1, “Special Character Escape
Sequences”. For all other escape sequences, backslash is ignored. That
is, the escaped character is interpreted as if it was not escaped. For
example, \x is just x. These sequences are case sensitive. For example,
\b is interpreted as a backspace, but \B is interpreted as B. "

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Issue in Dialplan Module

[Logeshwaran G]

Hi ,

Please find the below logs , The call is not placing Its in Trying state.

To: 
From: ;tag=e4269c5e
Via: SIP/2.0/UDP 192.168.3.5:6090
;branch=z9hG4bK-d87543-161839468-1--d87543-;rport
Call-ID: e01ac670234a8675
CSeq: 3 REGISTER
Contact: ;expires=0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3004t stamp 16741
Authorization: Digest
username="",realm="209.95.52.97",nonce="WYlDhVmJQlmWGnZELD+8UBwWgX2NmBdu",uri="sip:209.95.52.97",response="2b4efd8c09e8ce2de0a56fab38157c72",algorithm=MD5
Content-Length: 0


10:18:23.5
SENDING TO: 209.95.52.97:5060
REGISTER sip:209.95.52.97 SIP/2.0
To: 
From: ;tag=e4269c5e
Via: SIP/2.0/UDP 192.168.3.5:6090
;branch=z9hG4bK-d87543-161839468-1--d87543-;rport
Call-ID: e01ac670234a8675
CSeq: 3 REGISTER
Contact: ;expires=0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3004t stamp 16741
Authorization: Digest
username="",realm="209.95.52.97",nonce="WYlDhVmJQlmWGnZELD+8UBwWgX2NmBdu",uri="sip:209.95.52.97",response="2b4efd8c09e8ce2de0a56fab38157c72",algorithm=MD5
Content-Length: 0


10:18:25.5
SENDING TO: 209.95.52.97:5060
REGISTER sip:209.95.52.97 SIP/2.0
To: 
From: ;tag=e4269c5e
Via: SIP/2.0/UDP 192.168.3.5:6090
;branch=z9hG4bK-d87543-161839468-1--d87543-;rport
Call-ID: e01ac670234a8675
CSeq: 3 REGISTER
Contact: ;expires=0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3004t stamp 16741
Authorization: Digest
username="",realm="209.95.52.97",nonce="WYlDhVmJQlmWGnZELD+8UBwWgX2NmBdu",uri="sip:209.95.52.97",response="2b4efd8c09e8ce2de0a56fab38157c72",algorithm=MD5
Content-Length: 0


10:18:29.5
SENDING TO: 209.95.52.97:5060
REGISTER sip:209.95.52.97 SIP/2.0
To: 
From: ;tag=e4269c5e
Via: SIP/2.0/UDP 192.168.3.5:6090
;branch=z9hG4bK-d87543-161839468-1--d87543-;rport
Call-ID: e01ac670234a8675
CSeq: 3 REGISTER
Contact: ;expires=0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3004t stamp 16741
Authorization: Digest
username="",realm="209.95.52.97",nonce="WYlDhVmJQlmWGnZELD+8UBwWgX2NmBdu",uri="sip:209.95.52.97",response="2b4efd8c09e8ce2de0a56fab38157c72",algorithm=MD5
Content-Length: 0


10:18:33.5
SENDING TO: 209.95.52.97:5060
REGISTER sip:209.95.52.97 SIP/2.0
To: 
From: ;tag=e4269c5e
Via: SIP/2.0/UDP 192.168.3.5:6090
;branch=z9hG4bK-d87543-161839468-1--d87543-;rport
Call-ID: e01ac670234a8675
CSeq: 3 REGISTER
Contact: ;expires=0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3004t stamp 16741
Authorization: Digest
username="",realm="209.95.52.97",nonce="WYlDhVmJQlmWGnZELD+8UBwWgX2NmBdu",uri="sip:209.95.52.97",response="2b4efd8c09e8ce2de0a56fab38157c72",algorithm=MD5
Content-Length: 0


10:18:34.3
RECEIVING FROM: 209.95.52.97:5060
SIP/2.0 200 OK
To: ;tag=9dd61ff61e802d8e2bef5f14621ef3c2.8904
From: ;tag=e4269c5e
Via: SIP/2.0/UDP 192.168.3.5:6090
;branch=z9hG4bK-d87543-161839468-1--d87543-;rport=6090;received=192.168.3.5
Call-ID: e01ac670234a8675
CSeq: 3 REGISTER
Server: kamailio (5.0.2 (x86_64/linux))
Content-Length: 0


10:18:37.7 Proxy slot #0 () - Shutting down DUM took 16.115001 seconds.



On Tue, Aug 8, 2017 at 2:04 AM, Joel Serrano  wrote:

> Hi,
>
> (Sorry, my previous reply got blocked due to email size). Can you enable
> debug logs and try again, then send the logs?
>
> I tried the regex with the number 000919629897172 and it worked for me..
> We must be missing something..
>
>
>
> On Sun, Aug 6, 2017 at 11:19 PM, Logeshwaran G 
> wrote:
>
>> I mean to say by applying the Rule mentioned from Joel is also not worked.
>>
>>
>> Rules:
>> ==
>> dpid: 1
>> pr: 1
>> match_op: 1
>> match_exp: ^000[0-9]+$  <<< This will trigger a match on any number
>> that will start with three zeros.
>> match_len: 0
>> subst_exp: ^000([0-9]+)$  <<< If the match_exp is found, then create
>> a group with the desired part of the number, in this case, everything after
>> the three zeros.
>> repl_exp: \1   <<< \1 is a back reference to group 1, in this case
>> the number you selected in subst_exp, without the three zeros.
>> attrs:
>>
>>
>>
>>
>> On Mon, Aug 7, 2017 at 11:43 AM, Logeshwaran G 
>> wrote:
>>
>>> Please find the below output
>>>
>>>  5(12951) ERROR: 

Re: [SR-Users] Issue in Dialplan Module

[Joel Serrano]

Hi,

(Sorry, my previous reply got blocked due to email size). Can you enable
debug logs and try again, then send the logs?

I tried the regex with the number 000919629897172 and it worked for me.. We
must be missing something..



On Sun, Aug 6, 2017 at 11:19 PM, Logeshwaran G 
wrote:

> I mean to say by applying the Rule mentioned from Joel is also not worked.
>
>
> Rules:
> ==
> dpid: 1
> pr: 1
> match_op: 1
> match_exp: ^000[0-9]+$  <<< This will trigger a match on any number
> that will start with three zeros.
> match_len: 0
> subst_exp: ^000([0-9]+)$  <<< If the match_exp is found, then create
> a group with the desired part of the number, in this case, everything after
> the three zeros.
> repl_exp: \1   <<< \1 is a back reference to group 1, in this case
> the number you selected in subst_exp, without the three zeros.
> attrs:
>
>
>
>
> On Mon, Aug 7, 2017 at 11:43 AM, Logeshwaran G 
> wrote:
>
>> Please find the below output
>>
>>  5(12951) ERROR: 

Re: [SR-Users] Issue in Dialplan Module

[Logeshwaran G]

Please find the below output

 5(12951) ERROR: 

Re: [SR-Users] Issue in Dialplan Module

[Logeshwaran G]

I am using the below function:

 if (is_method("INVITE")) {

   dp_translate("1", "$rU/$rU");
}


On Sat, Aug 5, 2017 at 9:19 PM, Joel Serrano  wrote:

> Can you post your block of config related to dialplan module from
> kamailio.cfg?
>
> Also, how are you calling the dp_* functions?
>
>
> On Fri, Aug 4, 2017 at 10:34 PM, Logeshwaran G 
> wrote:
>
>> Thanks a lot for the Detailed Explanation.
>>
>> I am Beginner to Kamailio, As per Your Suggestion I have used the below
>> Rule:
>>
>> Rules:
>> ==
>> dpid: 1
>> pr: 1
>> match_op: 1
>> match_exp: ^000[0-9]+$  <<< This will trigger a match on any number
>> that will start with three zeros.
>> match_len: 0
>> subst_exp: ^000([0-9]+)$  <<< If the match_exp is found, then create
>> a group with the desired part of the number, in this case, everything after
>> the three zeros.
>> repl_exp: \1   <<< \1 is a back reference to group 1, in this case
>> the number you selected in subst_exp, without the three zeros.
>> attrs:
>>
>> But the First three Digit is not Removed. Please find the below log:
>>
>>  5(16152) INFO: 

Re: [SR-Users] Issue in Dialplan Module

[Logeshwaran G]

Thanks a lot for the Detailed Explanation.

I am Beginner to Kamailio, As per Your Suggestion I have used the below
Rule:

Rules:
==
dpid: 1
pr: 1
match_op: 1
match_exp: ^000[0-9]+$  <<< This will trigger a match on any number
that will start with three zeros.
match_len: 0
subst_exp: ^000([0-9]+)$  <<< If the match_exp is found, then create a
group with the desired part of the number, in this case, everything after
the three zeros.
repl_exp: \1   <<< \1 is a back reference to group 1, in this case the
number you selected in subst_exp, without the three zeros.
attrs:

But the First three Digit is not Removed. Please find the below log:

 5(16152) INFO: 

Re: [SR-Users] Issue in Dialplan Module

[Anthony Joseph Messina]

You missed what Daniel said:

IN a regexp ^ matches the beginning of the line/string, and $ matches
the end.

So "^000$" only matches exactly "000" and not "000"
Remove the $ to match strings begining with 000.

-- 
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
F9B6 560E 68EA 037D 8C3D  D1C9 FF31 3BDB D9D8 99B6

On Friday, August 4, 2017 11:18:04 PM CDT Logeshwaran G wrote:
> Yes I have Tried, please find below the Rules I have applied and the Result:
> 
> Rules:
> ==
> dpid: 1
> pr: 1
> match_op: 1
> match_exp: ^000$
> match_len: 0
> subst_exp: ^$
> repl_exp:
> attrs:
> 
> 
> I am Calling to the number 00091xx , But its saying as Too many
> Hops.
> 
> Its only looking for 000, Its not taking the 91xx numbers, If I
> call 000 only its replacing with the given number in the Rule table.
> 
> I need to Remove only the first 3 digits, and the other numbers should go
> to the call.
> 
> For Example If I am calling 00091x, It should remove the first 3
> digits 000 and 91x call should be place.
> 
> Please Guide me for removing the first three digits alone and other numbers
> should takes place.
> 
> On Fri, Aug 4, 2017 at 6:43 PM, Joel Serrano  wrote:
> > Have you tried what Daniel suggested?
> > 
> > Share the results of the tests and we can go from there.
> > 
> > On Thu, Aug 3, 2017 at 21:34 Logeshwaran G 
> > 
> > wrote:
> >> Input Please!!
> >> 
> >> On Thu, Aug 3, 2017 at 5:08 PM, Logeshwaran G 
> >> 
> >> wrote:
> >>> Thanks a lot!
> >>> 
> >>> But for my scenario,
> >>> 
> >>> If I am Dialling 0009199, need to remove the first three digits
> >>> 000, so the call should go to 9199.
> >>> 
> >>> I am stucked to create the rule for the above scenario, Kindly help me
> >>> for the same.
> >>> 
> >>> Kind Regards,
> >>> Logeshwaran
> >>> 
> >>> On Thu, Aug 3, 2017 at 4:48 PM, Daniel Tryba  wrote:
>  On Thu, Aug 03, 2017 at 04:00:45PM +0530, Logeshwaran G wrote:
>  > ++--++--+---+---+---
>  
>  +--+---+
>  
>  > | id | dpid | pr | match_op | match_exp | match_len | subst_exp |
>  
>  repl_exp
>  
>  > | attrs |
>  > 
>  > ++--++--+---+---+---
>  
>  +--+---+
>  
>  > |  1 |1 |  1 |1 | ^000$ | 0 | ^000$ |
>  > |  
>  > |   | 111
>  > 
>  > ++--++--+---+---+---
>  
>  +--+---+
>  
>  > The above rule replacing only the 000, If we Dial 000 its
>  
>  omitting,
>  
>  > While Dialing 000 its replacing that with 111.
>  
>  IN a regexp ^ matches the beginning of the line/string, and $ matches
>  the end.
>  
>  So "^000$" only matches exactly "000" and not "000"
>  Remove the $ to match strings begining with 000.


signature.asc
Description: This is a digitally signed message part.
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Issue in Dialplan Module

[Logeshwaran G]

Input Please!!

On Thu, Aug 3, 2017 at 5:08 PM, Logeshwaran G 
wrote:

> Thanks a lot!
>
> But for my scenario,
>
> If I am Dialling 0009199, need to remove the first three digits
> 000, so the call should go to 9199.
>
> I am stucked to create the rule for the above scenario, Kindly help me for
> the same.
>
> Kind Regards,
> Logeshwaran
>
> On Thu, Aug 3, 2017 at 4:48 PM, Daniel Tryba  wrote:
>
>> On Thu, Aug 03, 2017 at 04:00:45PM +0530, Logeshwaran G wrote:
>> >
>> > ++--++--+---+---+---
>> +--+---+
>> > | id | dpid | pr | match_op | match_exp | match_len | subst_exp |
>> repl_exp
>> > | attrs |
>> > ++--++--+---+---+---
>> +--+---+
>> > |  1 |1 |  1 |1 | ^000$ | 0 | ^000$ |
>> > |   | 111
>> > ++--++--+---+---+---
>> +--+---+
>> >
>> > The above rule replacing only the 000, If we Dial 000 its omitting,
>> > While Dialing 000 its replacing that with 111.
>>
>> IN a regexp ^ matches the beginning of the line/string, and $ matches
>> the end.
>>
>> So "^000$" only matches exactly "000" and not "000"
>> Remove the $ to match strings begining with 000.
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users