<!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.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Does anyone have any experience with a Digium T410P
over T1's using a Norstar?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I'm developing Asterisk for use as a
replacement/backup phone switch. The Norstar is in the loop only as a temporary
development tool, and will not be used in the final product. I've been trying to
route calls in and out of asterisk via the Norstar as it allows access to
readily available phones and existing extensions etc... </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Inbound to asterisk from a nortel phone
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I get a message on the console </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>"starting simple switch on Zap/NN-1 (where NN-1 is
the T1 group attached to the Norstar) and (subsequently) "Unknown extension 'X'
in context 'blah' that 'X' (where 'X' is the first
number dialed, regardless of what I dial, and where 'blah' is the
context entered in zapata.conf). </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>When I do a dial command from the console to the
same dialstring, the call appears to route and the appropriate phone on the
Norstar rings. I've even left the 'dmo' stuff intact as a test, and find that I
can access the demo features from the Norstar, even the IAX features seem to
route correctly, but when I get to my extensions, poof.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Any suggestions or pointers would be
appreciated.</FONT></DIV></BODY></HTML>