network outages and recent tests have shown that works well, albeit the
switch takes about 20 minutes to propagate the dns updates but otherwise
flawless.
=20
It's embarrassing and I'm losing credibility when clients are asking if
I'm still in business as the phone has dropped way to often in the past
few month. Interesting enough all outages to date have been Fridays or
Mondays.
=20
Does anyone else do anything like this. Anyone else using the Bell SNR
service? Suggestions welcome.
=20
Thanks in advance
Dave Bour
Desktop Solution Center
905.381.0077
------_=_NextPart_001_01C7B8AD.3105FB55
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html;
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16481"
name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>I've had slew of=20
problems with my Bell Canada Single Number Reach (SNR) dropping in the past=20
couple of months. Another outage Monday for several hours has me
wondering=20
if there's a way to </FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>1. Make a call out=20
of my system via a PSTN back to my SNR line, say every 30 minutes (this
I'm=20
sure is easy enough via the call
file...however...)</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>2. Track the=20
outgoing call and match to an incoming call...if there's no incoming
call...it=20
means my Bell circuit or VoIP provider or .... something is down...send me an=20
email that the service is down such that I can reroute my SNR to=20
cellular.</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>The whole point of=20
this SNR was to give me mobility...though that came at a cost...Add the Voip
off=20
Asterisk and it's a near perfect solution except when this=20
fails.</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>From a network=20
perspective, I've got dual hosted solution now to resolve network outages
and=20
recent tests have shown that works well, albeit the switch takes about 20=20
minutes to propagate the dns updates but otherwise
flawless.</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>It's=20
embarrassing and I'm losing credibility when
clients are asking=20
if I'm still in business as the phone has dropped way to often in the past
few=20
month. Interesting enough all outages to date have been Fridays or
Mondays.</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>Does anyone else do=20
anything like this. Anyone else using the Bell SNR
service? =20
Suggestions welcome.</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>Thanks in=20
advance</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>Dave=20
Bour</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial
size=3D2>Desktop Solution=20
Center</FONT></SPAN></DIV>
<DIV><SPAN class=3D218571111-27062007><FONT face=3DArial=20
size=3D2>905.381.0077</FONT></SPAN></DIV></BODY></HTML>
------_=_NextPart_001_01C7B8AD.3105FB55--
