Help me understand this better. What is your PSTN connectivity (E1 PRI?) at the remote site where you are running CME and what is your WAN connectivity?
Why even run CME code at the remote site? Is there a reason you are wanting to do this? You can just configure this Voice Gateway as an H.323 gateway and register it with your CallManager cluster, and then use SRST if the WAN fails.
For ingress calls to your CME site,
are they not coming in on your local E1 in that site? If so, they have to hit an inbound pots dial-peer there first. Then the Pots call leg is terminated on the CME, and a VoIP call leg is created to CCM, then the phone should ring. (If the dial-peers are set up correctly).
What is the latency over the WAN from your CME site back the CCM Cluster?
Thanks for your reply. The PSTN connectivity in lab where I'm testing this for the moment is analog with a vic2-2fxo card.
When we will roll it out in production it will be with a E1 PRI.
We want to run CME at the remote site because we need to have the added functionality
like login to hunt groups when the connectivity to the central site is lost.
Calls are indeed coming in via the local pstn connection on the remote site. they match a pots dialpeer and then they need
to match a voip dial peer going to the callmanager at the central site. The problem is that they are mathing the dial-peers that CME
automatically creates when you configure ephones and dn's. To get around this problem, I added the $ after my dialpeer that is pointing to the callmanager.
This works, but it takes about 2 rings before the ipphone actually starts to ring.
When I remove the ephone and dn's configuration on the CME, the phone starts to ring directly. Offcourse, when the link fails, the phones are not configured on the CME this way and no calls can be received/placed.
In production it will be an MPLS network with COS setup for voice, so very limited latency
The option defined with the "srst mode auto-provision" command determines whether Cisco Unified CME adds the learned phone and extension information to its running configuration. If the information is added, it appears in the output when you use the show running-config command and is saved to NVRAM when you use the write command.
?Use the "srst mode auto-provision none" command to enable the Cisco Unified CME router to provide SRST fallback services for Cisco Unified Communications Manager.
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...