02-01-2013 07:07 AM - edited 03-16-2019 03:29 PM
CUCM 8.6 ---SIP---2811 Gateway---Sip---ITSP. Using internationl number to Beijing airport as test call. Number is 86 10 96158. SIP provider only wants to see this number being relayed to them. I have CUCM route pattern set at 9011.!# so that I can dial 9 for outside dialtone, then 011 designating international call then match any number after that and hit # sign to force the call. The CUCM strips the 9011 and sends out just the 86 10 96158 to the 2811 gateway. If I configure my outgoing voip dial peer destination pattern to exactly match "861096158" the call completes. If I use a .T in the dial peer nothing happens because it is not an E.164 number. How do I configure my voip dial peer destination pattern to match a variable length number that is not in E.164 format, so I can call any international number using the stripping rules of CUCM?
Solved! Go to Solution.
02-01-2013 04:18 PM
What you can do is configure your dial-peer to like this...destination-pattern 9011T
You will then not need to strip any digit in CUCM, but the gateway will strip it...
Using .T should work and it has nothing to do with e164. Maybe you were matching a differernt dial-peer...You can send a debug voip ccapi, debug ccsip messages and a sh run for us to see whats going on
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
02-01-2013 04:18 PM
What you can do is configure your dial-peer to like this...destination-pattern 9011T
You will then not need to strip any digit in CUCM, but the gateway will strip it...
Using .T should work and it has nothing to do with e164. Maybe you were matching a differernt dial-peer...You can send a debug voip ccapi, debug ccsip messages and a sh run for us to see whats going on
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
02-02-2013 03:07 AM
I don't know aokanlawon, this call manager 8.6, she has a mind of her own..You are right about the .T and nothing to do with e164. At first I thought that was the problem when it just wouldn't work. When I tried it the final time after fooling around with other types of destination patterns that didn't work, it started working. I have one dial peer to lock on to 18xx numbers, one to take a number like 97023445688 and replace the 9 with a "1" and send out the number and now one that is just .T to lock on to international numbers like my SIP provider wants. It has been a journey learning 8.6 from knowing absolutly nothing about it when I started, especially integrating the 7920 wireless IP phone to it. I guess I run for help too quick when I can actually figure it out on my own in time.
Thanks for your support,
Tedd
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide