<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Using another router's PRI while in SRST</TITLE>
</HEAD>
<BODY>
<!-- 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></BODY>
</HTML>