I am trying to implement a large remote site with no local CCM. The remote site has five SRST gateways, one of which will serve as gatekeeper. In normal status, all phones are registered with CCM, and the gateways are H.323 peer to PSTN.
During WAN outage, all phones are registered with local gateways, and the gateways will register E.164 address to gatekeeper. So it will work as a H.323 environment.
However, in the real case, the users are using shared line quite a lot and the same E.164 numbers are registered with different gateways. And ironically, one single conflict number between gateways will fail the gateway registration with gatekeeper. Is there any way to work around this technical limitation? The numbers are all over the remote site and cannot be categorized into number blocks for different gateways, so zone prefix or tech prefix does not help much in this case.
We have more than 1,000 phones in this single huge remote site. It is not possible to register all the phones into one SRST gateway. And we need some dedicated SRST gateway for some specific sub-site within the remote site. Moreover, the DNs are very scattered and cannot be grouped to gateways by blocks.
Regarding to SRST gateways, we have PRI to PSTN. DNs are registered with CCM with 10 digit.
Now what I am thinking is not to register E.164 to gatekeeper, but use the same tech prefix for all the gateways. What I am not sure is will the gatekeeper send request to all the gateways simutaneously or in a order. I may need to set priority in gatekeeper or not...
Thanks a lot for your help. It is my most complicated design and implementation so far.
Anyways, the other option I can think of is to not register the e.164 and statically register all extension to the gatekeeper, using the 'alias static' and pointing every 10 digit number to the designated gateway. Not sure if there is a limit here or not, from the gatekeeper capabilities perspective.
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...