Rob Huffman Thu, 01/29/2009 - 11:35

Hi Ricardo,

Here is a clip from the CME SRND Guide;

Redundant Cisco Unified CME Router

A second Cisco Unified CME router can be configured to provide call-control services if the primary Cisco Unified CME router fails. The secondary Cisco Unified CME router takes over and provides services seamlessly until the primary router becomes operational again.

When a phone registers to the primary router, it receives a configuration file from the primary router. Along with other information, the configuration file contains the IP addresses of the primary and secondary Cisco Unified CME routers. The phone uses these addresses to initiate a keepalive (KA) message to each router. The phone sends a KA message after every KA interval (30 seconds by default) to the router with which it is registered and after every two KA intervals (60 seconds by default) to the other router. The KA interval can be adjusted with the keepalive command.

If the primary router fails, a phone will not receive an acknowledgment (ACK) to its KA message to the primary router. If the phone does not get an ACK from the primary router for three consecutive KAs, it registers with the secondary Cisco Unified CME router.

During the time that the phone is registered to the secondary router, it keeps sending a KA probe to the primary router to see if it has come back up, now every 60 seconds by default or two times the normal KA interval. After the primary Cisco Unified CME router is operating normally, the phone starts receiving ACKs for its probes. After the phone receives ACKs from the primary router for three consecutive probes, it switches back to the primary router and reregisters with it. The reregistration of phones with the primary router is also called rehoming.

The physical setup for redundant Cisco Unified CME routers is as follows. The FXO line from the PSTN is split using a splitter. From the splitter, one line goes to the primary Cisco Unified CME router and the other goes to the secondary Cisco Unified CME router. When a call comes in on the FXO line, it is presented to both the primary and secondary Cisco Unified CME routers. The primary router is configured by default to answer the call immediately. The secondary Cisco Unified CME router is configured to answer the call after three rings using the voice-port ring number 3 command. If the primary router is operational, it answers the call immediately and changes the call state so that the secondary router does not try to answer it. If the primary router is unavailable and does not answer the call, the secondary router sees the new call coming in and answers after three rings.

The secondary Cisco Unified CME router should be connected in some way on the LAN, either through the same switch or through another switch that may or may not be connected to the primary Cisco Unified CME router directly. As long as both routers and the phones are connected on the LAN with the appropriate configurations in place, the phones can register to whichever router is active.

Configure primary and secondary Cisco Unified CME routers identically, with the exception that the FXO voice port from the PSTN on the secondary router should be configured to answer after more rings than the primary router, as previously explained. The ip source-address command is used on both routers to specify the IP addresses of the primary and secondary routers.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmesystm.html#wp1024559

Hope this helps!

Rob

saifuddin.miyaji Mon, 12/03/2012 - 01:52

Hi,

There are some unanswered questions on this HA setup:

1. Would the changes on the primary be synced to the secondary automatically? Is there any way to achieve this?

2. SRND talks about the FXO ports but what about the E1/T1 lines? How to achieve redundancy of those lines?

Regards

Saif

Jonathan Schulenberg Mon, 12/03/2012 - 02:30
  1. No although you could open two SSH sessions and copy/paste the command from one to the other. If you're the scripting type you could also probably write a Perl/Python/whatever script that periodically reads the running config of the primary router and replicates it to the other.
  2. You would either need a switchgear device to electrically switch between one device or the other; or, have separate PRIs in the carrier's trunk group. At this scale you would be better off doing a SIP trunk. Both routers can register and the provider can configure it such that they route calls to the secondary router if the first fails to respond to the INVITE.

Please remember to rate helpful responses and identify helpful or correct answers.

Paolo Bevilacqua Mon, 12/03/2012 - 04:37

Jonathan Schulenberg wrote:

  1. No although you could open two SSH sessions and copy/paste the command from one to the other. If you're the scripting type you could also probably write a Perl/Python/whatever script that periodically reads the running config of the primary router and replicates it to the other.

According to documentation, two CMEs can automatically synchonize extensions:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmexasgn.html#wp1017019

Extension Assigner Synchronization

Extension Assigner Synchronization enables the secondary backup router to automatically receive any changes made by Extension Assigner to ephone mac-addresses in the primary router. The synchronization is performed using the Cisco Unified CME XML interface. The Cisco Unified CME XML client encapsulates the configuration changes into an ISexecCLI request and sends it to the secondary backup router using HTTP. The server on the secondary backup side processes the incoming XML request and calls the Cisco IOS CLI parser to perform the updates.

For configuration information, see the "Configuring Extension Assigner Synchronization" section.

I still have to fully test this, as I'm not sure how to have working with a primary router where the extension were manually assigned.

Actions

This Discussion