I already have a CME site up and running using a T1 E&M-WINK to access the PSTN. All the DNs are in the range of 1400-1499. There are H323 connections to other sites (i.e. not running cme at the moment) around 30 sites with legacy PBX connected to cisco routers.
In order to reach the CME site people from other sites dial [Access-Code]14 (i.e. 14 is the site number). When that call hits the cme router I need to ring the pilot number for the site that is configured to ring on all IP Phones at the moment. I tried creating a dial-peer voip with destination-pattern of 14 and in it I configured a translation rule to convert the digits to the pilot number.. But when I did that.. all communication between IP Phones at the CME site is broken because they can't dial each other... because of the overlapping destination-patter..
That would be a good way to do it.. however there are more than 30 sites... and the client don't want to go to every router and do the changes.. this is the first cme site they are implementing.. and they would like the behavior to be the same without changing configs on the other sites... so somehow I need to do the translation on the cme ...
OK, good point. I am confused on what is being done with the number. Are the people at the remote site trying to reach a certain person at the CME site, or a group of extensions. What is this pilot number and what is it used for?
There are 30 sites with legacy pbx at the moment that are connected to voip gateways in order to do toll-by-pass calls. People on all sites dial a code and then the number of the site... When the calls reach the final destination the legacy pbx ring an specific extension.
Now one of the sites has a CME VoIP Router that replaced their legacy pbx. I know that all other sites now can dial the extensions directly but because all users are not notified yet.. all other sites will still be calling with the code+ [store-number].. when the [store-number] gets to the CME router I need to convert that number to a valid Directory Number and/or a Hunt-Group, etc..
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...