I will have to configure a CCM with about 300 IP phones and two digital E1 trunks with DID.
The Telephony Manager gave me a form with all IP phones and their features to be configured. And i realized that the last four digits of the DID range do not match the ip phone extension numbers of the ip phones in almost all cases.
Normally, if you have a DID range like this (These numbers are faked):
+1 234 567 2000 to +1 234 567 3999
Then, the optimal choice would be to use an extension directory range for ip phones from 2000 to 3999, with a one-to-one equivalence. With this approach, the transaltion can be easely made at route group level.
But the form i got from the Telephony Manager has random DID assignements, for instance:
Extension 2340 should use a DID +1 234 567 3415 (2340 clashes with 3415)
Extension 2534 should use a DID +1 234 567 2813 (2534 clashes with 2813)
And so on with 300 ip phones...
According with CCM documentation,i can use ?External Phone Number Mask? field for every IP phone Directory number configuration page and marking the Calling party?s External Phone Number Mask button at the route pattern. With such configuration, when making outbound calls the ip Callmanager will send the manually selected DID number instead of the DID stripped from the ip phone extension.
This is perfect for Outbound calls. But what about INBOUND calls ?
Should i expect that inbound calls from PSTN will be translated in the same way as outbound calls?
A call from outside to 1 234 567 3415 will be translated to 2340?
A call from outside to 1 234 567 2813 will be translated to 2534?
The second option will be (i guess) to create as many translation patterns as ip phones, but it does not seem a polite solution.
The third option would be to speak with the Telephony Manager to request him to arrange extensions and DID?s in a grouped fashion.
Re: DID with ungrouped translations and Inbound calls
I think your interest in a diplomatic solution is well placed. Moving forward with the current spec looks too much like aerobic exercise. I cannot imagine why such a convoluted arrangement would be helpful.
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...