We are using our Corporate LDAP Directory for IP phone directory lookup.
ie: 3rd party web server publishing the users phone dumber in the E.164 format.
We want to have our users dial this number using the dial key on the phone when displayed. I was hoping a translation pattern or route pattern on CUCM 6.1 would work but it doesnt support this. I am aware CUCM 7.X does support E.164 dialing however I am hoping someone out there has got a potential workaround on CUCM 6.1.2
eg: User displayed +64488552211 must then be converted to 10488552211 for the user to dial
We are hoping not to change the application, ideally have the CUCM do the conversion
u know for a fact that works?? have u seen it work? \ is not a valid character for a pattern, i knew it wasn't but just to make sure i tried your pattern on a 6.1(3) and i cannot save it. i get the message saying what digits/characters are valid and \ is not one of them.
the usage of + in any previous version other than 7 means:
matches one or more occurrences of the preceding digit or wildcard value
These are the ONLY valid entries you can have in a translation pattern:
[ ^ 0 1 2 3 4 5 6 7 8 9 A B C D - ] + ? ! X * # + . @
So in CUCM 6.x, the + is not a digit, so the translation, even in the latest firmware the phones and cucm 6.x,. Same thing in CUPS for click to call in Application Dial Rules. The + is ignored in CUCM 6.x. When you think it's 12 digits, it's not.. it's 11.
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...