<!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>
<DIV><FONT face=Arial size=2>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Tahoma','sans-serif'">At
least for this telco, ISN and BRI was a money-loser. We’ve spent more time
trouble-shooting those connections (on behalf of the customers) than we ever
made in monthly or per-minute charges.<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P>Obviously I
can't speak for a telco that I know nothing about. The ability to support
ISDN requires some training and test equipment, and I've seen a wide variety of
approaches to managing that, some that work better than others. I do know
that it seems to be thriving (as well as can be expected) here. Qwest has
even used it with non-savvy customers as a method of pair gain where trunking
was limited or the cost of upgrading a drop cable was high. The techs that
actually work with it have proven competent and have the necessary equipment to
quickly diagnose problems, often remotely from the ROC. The exception
being one time when they sent a tech with no ISDN experience to a remote
terminal to solve another problem and he killed an ISDN circuit in it and it
took a couple of repeat visits to figure out what he did wrong.</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></FONT> </DIV></BODY></HTML>