<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3086" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>I think I've come up with a plan that suits my needs regarding
inbound dialing during SRST and wouldn't mind hearing what others have to
say....</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Basically, I'm going to create two dial-peers for both the T1
ports which translate all incoming calls so that it adds a 9 in front of it.
Then I will use num-exp to modify these to the appropriate
extension.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>My reasoning behind this is this:</FONT></DIV>
<UL>
<LI><FONT size=2>by prefixing all incoming calls I am not limited to the
number of translation rules (15)</FONT></LI>
<LI><FONT size=2>by using the translation profile incoming on the
dialpeer I don't have to worry about affecting numbers dialed by phones
onsite</FONT></LI>
<LI><FONT size=2>by using num-exp config statements with 9<blah>, onsite
phones don't see any change in dialing behaviour</FONT></LI>
<UL>
<LI><FONT size=2>if i had used just the number without the 9, users would
see matches to non-existant extensions</FONT></LI></UL>
<LI><FONT size=2>by using num-exp I have no limits (not that I've
seen)</FONT></LI></UL>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT
size=2>--------------------------------------------------------------------------------<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>...there's no such thing as a bad timbit...<BR></DIV></FONT></BODY></HTML>