<!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.5730.11" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>>Rather, can you tell me who claims to support what
hardware, so I can confirm?
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I don't have any notes on what I did. It was
a bunch of Google searches. I seem to recall that Digium themselves made a
two port BRI that would work. Eicon has some well respected products that
I am pretty sure are supported for NT1 (They are based in Canada). Zyxel,
I think does, also. I didn't go that way because most were two or more
ports and I only needed one and couldn't justify the $200 to $400
cost.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>>I have no time for digging
and experimenting, unfortunately. I expect that time will be >taken up
entirely trying to install and configure asterisk.<BR>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>That translates fairly straightforwardly into, "you
have no time for Asterisk or Linux, its underlying operating system. I
can't imagine going down this path in any form without setting aside weeks of
time for experimentation. I've invested at least two person weeks to get
Linux up and running and a small demo Asterisk install with no trunks and two
SIP phones. I think the payoff will be worth it, but the learning curve is
steep. If you are already capable of installing Linux from source code in
your sleep, you mileage may very significantly.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>>Okay, these
are various driver protocols in the kernel/user space,
right?</FONT><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Yes, Dahdi is tightly linked to Asterisk, the
others are more loosely coupled.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>>Since I
haven't purchased anything, should I be analysing the rate and support for
>development of these different protocols and informing my decision that
way?</FONT><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Based on the related posts today, it sounds like
you should be looking at what dahdi can do and what drivers the board makers
provide. The other options are possible paths to a solution but no where
close to turn-key.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>>any
solution that doesn't lease equipment from the provider conflicts to their
bottom-line >interest, so I don't expect any help from them. Am I wrong in
that?</FONT><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>I've been getting ISDN from QWEST for about eight
years now at a combination of four locations. The company has made a huge
amount of progress in operations over that time. The last two installs
went off pretty much without a hitch. The sales people tend to be weak on
ISDN, and the I & R people are variable. My best result has been with
the guy in the CO that works ISDN circuits from the inside. In our office,
he's sharp and quite willing to give out his phone number to anyone who doesn't
come across as an idiot for follow-up questions. I wouldn't expect them to
tell me how to configure Asterisk, but if they have a problem, or sales didn't
write up the configuration correctly, he's been able to answer my question and
change the CO programming on the spot for me.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Wilton</FONT></DIV>
<DIV><FONT face=Arial size=2> </DIV></FONT></BODY></HTML>