Re: VoIP transmission troubles

["A.J." <j_re_pairman@xxxxxxxxx>]

VOIP & Security Alarm don't mixed.

Sending one account ID and received as another account ID on the other end
is nothing new and there is no way around it. People can say whatever they
want but there is just no way that alarm signal can be transmitted over VOIP
in any reliable way. Putting a "*99" in front of the phone number seems to
improve the success rate but it's still not 100% fool proof.

"*99" activates the "data mode" of the VOIP ATA for the duration of the
call.

So if the client is not willing to upgrade to GSM or IP monitoring, then try
this "*99" trick.




"tourman" <robercampbell@xxxxxxxxx> wrote in message
news:b359e163-7cc9-48a5-beb1-ac0c49ee86a1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I'd like to hear from some of the regulars about their experiences
> with alarm transmission over VoIP.
>
> I have one customer who without my knowledge changed to VoIP from a
> Bell line, and then asked me to hook up the panel using his new
> service. I did so reluctantly, but only after he signed a legal
> agreement limiting liability, and with the express understanding it
> was being done experimentally. I programmed in a daily test and kept
> watch each morning for failures to communicate. It seemed to stop
> transmitting only very occasionally, until one day it started sending
> "ghost" signals which resulted in a police dispatch on the wrong
> account number. The panel was programmed in Contact ID, but it seems
> when the signal went out on the network, it transposed a "6 " in the
> account code for a "5". Then the comedy of errors increased when the
> station failed to check the CID (where they would have picked up that
> it was coming from the wrong phone number) and dispatched the police.
> Needless to say, I had an unhappy client who couldn't understand why
> the cops arrived...(and yes, the account number in the panel IS
> properly programmed...).
>