We have a centralized CUCM cluster servings offices around the world. Jabber seems to depend on the App Dial Rules mechanism of CUCM in order to help normalize phone number dialing in the client and its various integration points/flows.
The problem with this, is that App Dial Rules do not support anything past "number of digits". This causes quite a bit of headache when trying to configure them against non-NANP numbering schemes.
My questions are, can anyone recommend a good strategy to support app dial rules globally, and if not, is Cisco working to make this functionality better by adding regex support in the dial rules?
I have the same problem. I'd very much like to see more advanced dial rule capability I'm CUCM. Regex support would be wonderful.
For example, in our directory, many of our phone numbers are listed as [E.164 #Ext]. That is to say, the full number followed by octothorpe and the extension. I'd like to have a rule to remove the extension part, but it doesn't seem possible.
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...