<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2>I'm using dsci, <A
href="http://www.dscicorp.com">www.dscicorp.com</A> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2>I do IT consulting at various companies, and only one of
them had a phone system that satisfied me. So I asked them who they used,
and it's DSCI. I've since used a hosted pbx solution from dsci at a
different company, and have been very pleased.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2>I know one guy who uses covad, and he's happy with
it. As long as you get an MPLS T1 that's connected directly back to their
location, and you elect to run a certain level of QoS on the line, you get
perfect voice quality.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2>I think it's better to have the pbx solution outsourced
rather than in-house, because of two reasons - (1) If it's in-house, you're
absolutely responsible for it. If it's outsourced, the people who maintain
it eat, breathe, and dream nothing but phone systems. (2) Where we have it
outsourced, if the T1 goes down for some reason, of course we can't receive
calls. But any caller will still get the normal ringing, followed by voice
prompts, and leave voicemail. If I go get an internet connection
somewhere, I can open a webpage and forward somebody's extension to their cell
phone. Where we have it in-house, if the T1 goes down, callers get a busy
signal, end of story.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=703061315-30092006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> bblisa-bounces@bblisa.org
[mailto:bblisa-bounces@bblisa.org] <B>On Behalf Of </B>Michael
Filosa<BR><B>Sent:</B> Thursday, September 28, 2006 10:28 AM<BR><B>To:</B>
bblisa@bblisa.org<BR><B>Subject:</B> [BBLISA] VOIP
experience<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Does anyone have an experience with ether IP phones or VOIP providers. We
are looking to setup a couple smaller offices with phone service. The
various business class VOIP provider out there seem to be a god fit for
us but we have no experience with service or equipment in that world.
</DIV>
<DIV> </DIV>
<DIV>Any feedback comments would welcome.</DIV>
<DIV> </DIV>
<DIV>Most of the solutions we are consider using a cisco IP phone which connects
either to a local or remotely hosted IP PBX system.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></BODY></HTML>