<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
configure both routers for SRST so router #2 will take over management
of the d-channel when MGCP backhaul to CM goes down.<br>
<br>
Then configure router #1 with an SRST VOIP dial-peer pointing to
router#2. do a normal huntgoup (preference 1, pref 2,).<br>
<br>
believe this should work fine.<br>
<br>
/Wes<br>
<br>
Ruttman, Peter G. wrote:
<blockquote
cite="mid7E3064B7EFC16C41B185C41D141008B75C5E0B@foleyex97.foleylaw.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="MS Exchange Server version 6.5.7226.0">
<title>Using another router's PRI while in SRST</title>
<!-- Converted from text/rtf format -->
<p><font face="Arial">I am looking to split my router's PRIs between
two 3745 routers. So if I loose a router I will still continue to have
PSTN service without technical intervention. However, if my WAN goes
into SRST (the callmanagers are offsite) then the phones will register
to only one of the routers and I do not know how or if it is possible
to configure SRST to access the other router PRI. One way is to make
two device pool and point each at a different router and configure SRST
on both but that doesn't give me any redundancy if I also loose a PRI
for some reason. Is there any way for a signal SRST router to be
configured to remotely get at another router's PRIs?</font></p>
<p><font face="Arial">Pete</font>
</p>
<br>
The preceding email message may be confidential or protected by the
attorney-client privilege. It is not intended for transmission to, or
receipt by, any unauthorized persons. If you have received this message
in error, please (i) do not read it, (ii) reply to the sender that you
received the message in error, and (iii) erase or destroy the message.
Legal advice contained in the preceding message is solely for the
benefit of the Foley & Lardner LLP client(s) represented by the
Firm in the particular matter that is the subject of this message, and
may not be relied upon by any other party. <br>
<br>
<br>
Internal Revenue Service regulations require that certain types of
written advice include a disclaimer. To the extent the preceding
message contains advice relating to a Federal tax issue, unless
expressly stated otherwise the advice is not intended or written to be
used, and it cannot be used by the recipient or any other taxpayer, for
the purpose of avoiding Federal tax penalties, and was not written to
support the promotion or marketing of any transaction or matter
discussed herein.<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</body>
</html>