voiplover
Premium
join:2004-05-28
Portsmouth, NH | reply to TSymonds
Re: [Vonage] Vonage And ADT Issue
TSymonds, please become a member so that members can IM you in order to solve your problem. |
|
TSymonds
@army.mil |  reply to eddiyer
Can you tell me how to set up my ADT Vista 10 SE with my new Vonage system?
Thanks --
Major Tim Symonds |
|
voiplover
Premium
join:2004-05-28
Portsmouth, NH | reply to bthornhill
I agree. I just left them in there because of the type of format. 4+2 will only be a format worth holding on to.
"Nobody will ever need more than 540k of memory." Bill Gates |
|
bthornhill
join:2004-05-10 | reply to voiplover
There is no way that 3+1, 4+1 etc will ever become standard again. |
|
voiplover
Premium
join:2004-05-28
Portsmouth, NH
 ·callwithus
·Axvoice
1 edit | reply to bthornhill
If you want your alarm system to call for help, use a pots line
If you need to use a Voip line than ask your alarm company to use 4+2 format with your system.
FC stands for failure to communicate and with the DSC receiver that most monitoring stations that are now handling ADT's alarm signals, they aren't sending the kiss off signal to the subscribers alarm panel due to timing corrupted issues or lost packets. The reason why 4+2 has a better chance of completion is simply because it is pulsing out each digit of the signal. Contact ID is about a 4 second transmission sequence compared a 9 second transmission of 4+2 @ 20pps (~13 seconds completed). 4+2 @ 10pps has an even better chance but takes almost twice as long. Also your voip call is only going to be as good as the weakest link in your connection.
3+1, 4+1, 4+2, silent night slow 10pps and silent night fast 20pps (Napco actually invented 4+2) will probably be the up coming standard again in the alarm industry. If you keep up with with the NFP and your life safety code you should know that SIA is the approved format. Contact ID was designed for wantabe companies to make monitoring stations profitable. Guess what, It's killing them.
The saving feature for voip is providers implementing fax. When the sip server hears a fax tone or anything close (hand shake for 4+2) it will change the codec to 711 high bandwidth and hopefully allow the transmission to be accomplished.
Ademco (now owned by Honeywell) receivers and transmitters have to be able to use SIA to get the fire ratings. They may not offer the programming info in the manuals that you are receiving.
It is in your best interest to standardize on using 4+2 format at least as a back up.
RF (Radio) w/ telco backup is the only wide spread solution.
Just hanging in there to see what happens! |
|
bthornhill
join:2004-05-10
·voip.ms
| reply to eddiyer
said by eddiyer:
rattili,
I work for an alarm company as a service tech, and I have Vonage as my only home phone, my alarm system works just fine with Vonage with an exception, I have my alarm communicate in 10pps 1400Hz, with a 4X2 reporting format.
It's hard to imagine that a 4/2 format would work on VOIP. It's even harder to imagine that a central station in this day-and-age would still want a sub communicating in a pulsed format!
I tried ContactID on my system and there was too much echo in the line for the DTMF to transmit correctly. I was able to change the format over to SIA (generally acknowledged to be the more robust format) and it worked no problem. SIA is a "FSK" format (i.e. modem bursts).
To the best of my knowledge, ADEMCO systems cannot xmit in SIA. |
|
higginzdogz
join:2004-08-25
Richmond, VA
| reply to rattili
I am curious if you needed to do anything special with your Vonage adapter? I just had an ADT system installed today and the techs who installed it are claiming that they are unable to get a call to complete back to the ADT "base station". They told me that they were able to dial the 800 number, heard it ring 3 times and then got disconnected. I had similar issues when trying to use a fax machine across my Vonage connection and am wondering if there is something I can tweak. Thanks! |
|
rattili
join:2004-02-02
Collegeville, PA | reply to rattili
Also, do you think something changed on the Vonage side? This was working fine for over 6 months without any problem. And this "FC" started couple of days back. And I tested my alarm system numerous times before. It was never like this. |
|
rattili
join:2004-02-02
Collegeville, PA | reply to eddiyer
Thanks everyone for your responses. I'll look into your suggestions after I get home tonight. |
|
eddiyer
@204.246.x.x
 from:
IGGY 
| reply to rattili
rattili,
I work for an alarm company as a service tech, and I have Vonage as my only home phone, my alarm system works just fine with Vonage with an exception, I have my alarm communicate in 10pps 1400Hz, with a 4X2 reporting format. This slows down the communication a little so that everyone (your alarm and ADT's receivers) can understand. Under normal situations you can just change your reporting format to "slow it down" a little.
But here is the problem from your description of what is on your keypad, you have an Ademco alarm panel, now if ADT installed the alarm panel then it is an Ademco alarm panel that Ademco made for ADT in order to make it proprietary.
This causes a problem because they will only "talk" to ADT's receivers in a format called Contact ID (CID). When the alarm panel communicates in CID it is communicating at 2300Hz and is a faster communication (higher baud rate), the redial that you are seeing is coming from the panel not understanding what is called the "kiss off" this happens when the receiver has understood everything the alarm panel has sent and the "tell" the panel not to call back. When the "Kiss off" is not heard 100% correctly the panel will call back. This will happen until the panel is told to stop after so many attemps (set by your alarm company). So when you call the alarm company, they see 7 signals from you (even though you were only supposed to send 1) and they tell you, "sure we are receiving signals" but in reality your panel is not understanding the kissoff therefore calling back multiple times.
Now you know what is the problem, what can you do about it?
1)Call ADT and see if the panel can communicate in anything other than Contact ID
2)If it cannot throw the piece of crap out the window and get something that is not proprietary, the exact same panel model, just not an ADT panel POS. (The Ademco panel is a good panel what makes it crap is the ADT proprietary thing)
3)If that is not an option, look into getting a cell backup, not a true cell backup but one that works off of cellemetry (this is the billing section of the cellular service) a really good one is made by Telgard.
4)Get radio backup through ADT (Or another company)
Live with the 'FC' on your keypad...but you will never know if it a true Failure to Communicate |
|
