Re: VONTAGE

[tourman <robercampbell@xxxxxxxxx>]

On Aug 5, 12:39=A0pm, Jim <alarmi...@xxxxxxx> wrote:
> On Aug 5, 3:33 am, CH IS <s...@xxxxx> wrote:
>
>
>
> > > "tourman" wrote...
>
> > > RHC: Yeah, I've had loads of clients come to me with VoIP service and
> > > they never want to understand that this service is unreliable with an
> > > alarm. So their next step is to call another company who doesn't give
> > > a shit, and hooks them up anyway just for the money. It almost seems
> > > dealers who do the right thing are punished by the scummy ones who
> > > don't care about anything other than that monthly RMR. And if you try
> > > to sell the client on the proper IP connecting device, they won't
> > > spend a dime on it.....
>
> > > Although it might be hard to swallow at times, you are doing the righ=
t
> > > thing !! And if they care that little about the alarm, then the hell
> > > with them....you're better off getting rid of them
>
> > Any idea what Shaw's digital phone service is? Aparently it's not VoIP.
>
> > We've had a couple of customers switch to it and haven't had any proble=
ms so
> > far. And the Shaw techs seem to know more about how not to mess up a li=
ne
> > seizure phone connection than Telus does. They just take Telus' incomin=
g
> > line off and replace it with theirs, not bothering to "fix" this strang=
e
> > connection they don't understand.
>
> >http://www.shaw.ca/en-ca/ProductsServices/DigitalPhone/AboutDigitalPh...
>
> > - Chris
>
> We had this problem with Cablevision a number of years ago. It took
> over a year when subscribers found out that their alarm systems
> weren't working and had to pay their alarm companys to rehook the
> alarm and complaining to Cablevision, for them to meet with the alarm
> associations to learn how to make the proper connections. The
> associations had been trying to get Cablevision "informed" for quite
> some time. But it wasn't until they started to get complaints and
> cancellations that they finally paid attention. The associations
> helped them set up classes for their technicians and provided them
> with old alarm panels and mock telephone line connections so that they
> would know what to do in the field.
>
> The techs are "supposed to" have the consumer test the alarm system
> before they leave the premises .... but that doesn't always happen. We
> have relatively fewer problems now, as compared to the beginning of
> VoIP in this area. The one thing they haven't learned is that when you
> back feed the telephone line to an alarm panel, it will still sense
> the telephone line so it wont show telco fail, but it can't dial out
> when the line seizure relay flips. So if they don't test the system
> before they leave .......

RHC: Yeah, in all honesty, things have improved a bit around our area
too. Mostly it's the Cable company employees who have finally learned
to set up the alarm on their system properly (probably because Rogers
Cable fines them $40 if they receive a complaint about an alarm that
doesn't work after they've been in). And since the cable phone doesn't
leave their cable network and go out on the internet, the connection
is as reliable as a land line. I've had more than one call me on my
cell to actually ask me how to set things up (if a telephone guy ever
called, I think I would faint from amazement....:))

The phone company use a lot of poorly trained subcontractors who
really don't care about the alarm and this ends up causing me a great
deal of unnecessary service work to fix the system afterwards. Nor
have we (the local dealers) found a way to bill the phone company in a
way that works. I refuse to bill my customers since it's not their
doing and they end up being caught in the middle of the disputes....

I must say, it did take the Cable guys awhile to figure out they have
to connect to the "red and green" rather than the "black and yellow"
pairs though....:))