<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1515" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff><SPAN class=398112914-13092005>I tried this
below without luck. Is this what you were describing or am I on the wrong
track?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff>dial-peer voice 1 pots<BR> description
Outgoing call dial peer<BR> preference 1<BR> destination-pattern
9T<BR> progress_ind alert enable
8<BR> direct-inward-dial<BR> port 4/0:23</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff>dial-peer voice 101
voip<BR> description Outgoing call dial peer<BR> preference
2<BR> destination-pattern 9T<BR> progress_ind alert enable
8<BR> session target ipv4:172.28.130.1<SPAN class=398112914-13092005> (IP
address of other SRST router)</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff></FONT> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Walenta, Phil
[mailto:philip.walenta@berbee.com] <BR><B>Sent:</B> Friday, September 09, 2005
11:04 PM<BR><B>To:</B> Wes Sisk; Ruttman, Peter G.<BR><B>Cc:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> RE: [cisco-voip] Using another
router's PRI while in SRST<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=047060304-10092005><FONT face=Arial
color=#0000ff size=2>Wes, you are correct. Simply pointing dial peers at
the opposite router will work. I've done this numerous times with great
success.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Wes
Sisk<BR><B>Sent:</B> Friday, September 09, 2005 5:47 PM<BR><B>To:</B> Ruttman,
Peter G.<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Using another router's PRI while in SRST<BR></FONT><BR></DIV>
<DIV></DIV>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 content="MS Exchange Server version 6.5.7226.0" name=Generator><!-- 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 width="90%" SIZE=4>
_______________________________________________
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></BLOCKQUOTE><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></BODY></HTML>