cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
New Contributor III

test template match

I wanted to use the test template match function to modify strings.  I went to the documentation on the AOS and followed their example - it didn't work.

here is the sequence that I executed (the sample was right out of the documentation).

pastedImage_0.png

can someone help me on how to use the command.

thanks

Labels (1)
0 Kudos
Reply
7 Replies
Highlighted
Valued Contributor
Valued Contributor

Re: test template match

Larry, can you clarify more the application you're trying to use this command for? What specific documentation did you obtain the instructions from? Thanks

0 Kudos
Highlighted
New Contributor III

Re: test template match

Jay, not a problem.

the command and how I wanted to use it is defined in the "configuring SIP Proxy in AOS" .

My application is on a 7100 connected to a 6355.  While I was reading through the document it appeared that this command was what I was looking for to address another issue that I have with the 7100 namely that I have unused TNs associated with a SIP trunk that I want to route to a centralized response environment.  basically match the area code and the prefix and then accept wild cards and then substitute an extension for these numbers.

0 Kudos
Highlighted
Valued Contributor
Valued Contributor

Re: test template match

Larry, that may be part of the disconnect. There is no way to route numbers in the manner you're suggesting. Every DID must be explicitly specified and mapped to a particular user or service. Thanks

0 Kudos
Highlighted
New Contributor III

Re: test template match

Jay,

thanks for the note.  I did figure out that incoming numbers can't be modified except if they are passed via a trunk to another device.  To solve my problem, I added a match on the incoming SIP trunk with a low enough priority to insure that if the number was assigned to a phone then it would route to the phone, and then the remainder of the numbers got routed to another 7100 that I enabled auto attendant that basically told them to call the main number.

However, when I was in the CLI I tried a number of the Test Template examples on only the one to one would match.  I wanted to understand how to correctly use the Test Template.

0 Kudos
Highlighted
Valued Contributor
Valued Contributor

Re: test template match

Larry, the sample output from the guide looked like this:

#test template match “5551234” to “555XXXX” substitute-using “1359555XXXX”

Substitute Result -> 13595551234

It looks like you were using a regular expression in your match statement rather than the same wild card digits from the "substitute using", which is why it failed. Thanks

0 Kudos
Highlighted
New Contributor III

Re: test template match

Jay,

I noticed that you marked your answers as the correct answer.  I don't think that you answered the question.

the question was why doesn't the test template work correctly.

again, it appears that the command sequence shown in the reference manual doesn't work.

I tried all of the examples shown the reference guide (I was using AOS R12.1.0 CRG page 1793/4) on a 7100, and 6355.  it didn't work except for an exact match IE test template match 1234 to 1234 resulted in match , test template match 1234 to 123X resulted in no match and the substitute doesn't work

So that everyone on the same page the following is out of the AOS command reference guide

My question is simple, why doesn't it work.  I am not taking it out of context.  This is used for dial strings it should work on the 7100 or the 6355 and the command is accepted.

If you don't know the answer that's fine.

regards

pastedImage_0.png

0 Kudos
Highlighted
Valued Contributor
Valued Contributor

Re: test template match

Larry, I didn't mark my answer as correct and it doesn't appear that way as of right now. If I clicked it, it was in error, but it's also possible for another user to click it.

Your previous note indicated that you were looking in the "Configuring Sip Proxy in AOS" guide, so I hadn't looked at the examples in the AOS Command Reference Guide. I was able to get half of the commands you screenshotted to work, but some did not. That's either an error in the guide or it's a software bug. In either case, I would suggest opening a ticket so it can be investigated. Thanks

0 Kudos