[cisco-voip] Redundancy Options for CME

[Bill Greenwood (US)]

Even if the configurations are synchronized which would allow for the
phones to register with either router, how would the calls from the PSTN
be handled?  If a call was received on the router that was not the
primary it would see the phone as not being registered and forward to
voice mail.  There needs to be some method of having the routers
communicate with each other similar to a publisher and subscriber.  I
have not been able to find anything to allow for this communication.
Can the second router be configured with SRST?  But that still leave the
question on the PRIs, if both are connected to the primary router and it
fails then you are left with no connection to the PSTN.

 

From: mthompson729 at gmail.com [mailto:mthompson729 at gmail.com] 
Sent: Sunday, July 12, 2009 3:11 PM
To: Bill Greenwood (US)
Subject: Re: [cisco-voip] Redundancy Options for CME

 

I've never tried to do this, but the only way I could think to do this
is using HSRP on the FE interface. this is assuming that the HSRP
address can be used as the source-address for the CME system. 

This would make proper documentation and config sync a critical process
though. 



On Jul 12, 2009 3:03pm, "Bill Greenwood (US)"
<bill.greenwood at us.didata.com> wrote: 

> 
> 
> I am looking for information on how to provide redundancy for a CME
based system. 
> The configuration is there are two identical routers at the 
> site, two PRI circuits to the PSTN and 60 or so phones.  I am at a
loss as 
> to how to recommend redundancy for this.  Is it one router configured
with 
> CME as normal, but how should the second router be configured?  Is the

> second router configured with CME or as an SRST router.  How should
the 
> second router appear to the primary CME router?  How should the PRIs
be 
> connected, if one is connected to each router I can set up the dial
peer to 
> route the outbound calls, but how are the inbound (from the PSTN)
routed?  
> If the PRIs are connected to only one router redundancy is lost.  I
have 
> be unable to locate any documentation that explains how to set this
up. 
 
> 
> 
>   
> 
> 
> 
> 
> Thanks for your help. 
> 
> 
> 
> 
>   
> 
> 
> 
> 
> Bill 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Disclaimer: 
> 
> 
> 
> This e-mail communication and any attachments may contain confidential
and privileged information and is for use by the designated addressee(s)
named above only. If you are not the intended addressee, you are hereby
notified that you have received this communication in error and that any
use or reproduction of this email or its contents is strictly prohibited
and may be unlawful. If you have received this communication in error,
please notify us immediately by replying to this message and deleting it
from your computer. Thank you. 
> 
> 
>




-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090712/c2199e9d/attachment.html>