Problems configuring translation patterns with CCM 3.3(3).
is it possible to use the character "#" in a translation pattern??
What we would like to do is to translate a range of number from 29XXX to 0057729XXX#.
Unfortunately we saw that, if the translation is done using a unique number without "variables", it works great (i.e.: 29567 translated in 0057729567# without any "X" characters it works).
Using "X" characters the result of the translation is to double the last specified digit, stripping the last digit before the octothorpe ("#") character: i.e. 29XXX in 0057729XXX#, where XXX = 123, the result of the translation is: 29123 = 0057729912# .
Re: Problems configuring translation patterns with CCM 3.3(3).
What do you want to do with the resulting pattern? If the aim is to send the number via call proccessing again to say a route pattern then why not just create a route pattern that closely matches the number of digits in the resulting string.
TP 29XXX = 0057729XXX
RP 0.057729XXX (urgent Priority)
this way you'll get the match immediately and route the call without the need for the #
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...