<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'><br>Each router would have dial-peers pointing to the other router for each set. There is a default setting (in SRST anyways) that prevents a routing loop via H323.<br><br>I had a similar question, and it was discussed briefly on the list. One of the Cisco folk told me about the routing loop prevention. That's key. Because it's on by default, it helps.<br><br>Here's a press release talking about it (in very general terms). <br><br>http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_case_study0900aecd80424090_ns431_Networking_Solutions_Case_Study.html<br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Bill Greenwood (US)" <bill.greenwood@us.didata.com><br>To: cisco-voip@puck.nether.net<br>Sent: Sunday, July 12, 2009 3:43:39 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Redundancy Options for CME<br><br>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: "Tahoma","sans-serif";">From:</span></b><span style="font-size: 10pt; font-family: "Tahoma","sans-serif";"> mthompson729@gmail.com
[mailto:mthompson729@gmail.com] <br>
<b>Sent:</b> Sunday, July 12, 2009 3:11 PM<br>
<b>To:</b> Bill Greenwood (US)<br>
<b>Subject:</b> Re: [cisco-voip] Redundancy Options for CME</span></p>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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. <br>
<br>
This would make proper documentation and config sync a critical process though.
<br>
<br>
<br>
<br>
On Jul 12, 2009 3:03pm, "Bill Greenwood (US)"
<bill.greenwood@us.didata.com> wrote: <br>
<br>
> <br>
> <br>
> I am looking for information on how to provide redundancy for a CME based
system. <br>
> The configuration is there are two identical routers at the <br>
> site, two PRI circuits to the PSTN and 60 or so phones. I am at a
loss as <br>
> to how to recommend redundancy for this. Is it one router configured
with <br>
> CME as normal, but how should the second router be configured? Is
the <br>
> second router configured with CME or as an SRST router. How should
the <br>
> second router appear to the primary CME router? How should the PRIs
be <br>
> connected, if one is connected to each router I can set up the dial peer
to <br>
> route the outbound calls, but how are the inbound (from the PSTN)
routed? <br>
> If the PRIs are connected to only one router redundancy is lost. I
have <br>
> be unable to locate any documentation that explains how to set this up. <br>
<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Thanks for your help. <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Bill <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Disclaimer: <br>
> <br>
> <br>
> <br>
> 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. <br>
> <br>
> <br>
></p>
</div>
<p></p><hr size="1"><p></p>
<p><strong>
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.
</strong></p><br>_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
</div></body></html>