#1: From Unity's perspective, my customer uses overlapping "dial IDs" in the way they want their numbering plan to work. as an example:
- dial-ID 123 extensions 1000-1999 live at voicemail site A
- dial-ID 123 extensions 2000-2999 live at voicemail site B
Both the remote AMIS sites here expect four-digit extension delivery. I could configure the dial-IDs as 1231 for site A and 1232 for site B, but unfortunately then Unity would send a three-digit extension along. If I had the ability to prefix the extension, I could work around this.
#2: the customer has a few remote systems where they want to be able to use the same three-digit long dial IDs, but deliver 5-digits to identify the extension, for example:
- dial-ID 321 extensions 0000-9999 live at site C, but the remote system expects 10000-19999. I could configure the dial-ID In Unity as 32 to achieve 5-digit extension delivery, but this will conflict with other sites (i.e. 322). If I could prefix on the extension (add a "1") I could configure the dial-ID as 321.
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...