hi, I have been fpl for over 3 years now. just recently I have notice (last 6 month) that when my alarm device tries to dial home I keep getting "not covered by your tariff plane". when I try dialing the phone # manually from a handheld phone connected to the pap2 it dials in no problem. but when the device tries it get that error.
im with alarmforce and the # its trying to dial is 1-877-877-**** (I don't think they want ppl to know the #. I had to figure it out). I have checked my setting on the pap2 and all is set to freephneline standards. and like I said if I dial the # it connects no problem. alarm force is not helping bc they just want me to purchase another plan which I don't want to spend more $ on.
it worked without any issues before. the 2-way communication was there and worked. has I had some false alarms and it was able to call home and agent was able to communicate with us from the device. but like I said as of about 6 months it has not worked.
anyone have this issue?
thx
central alarm not working anymore
-
- Just Passing Thru
- Posts: 2
- Joined: 06/12/2013
- SIP Device Name: pap2
- Firmware Version: 5.1.6(LS)
- ISP Name: bell
- Computer OS: win7
-
- Just Passing Thru
- Posts: 2
- Joined: 06/12/2013
- SIP Device Name: pap2
- Firmware Version: 5.1.6(LS)
- ISP Name: bell
- Computer OS: win7
Re: central alarm not working anymore
so after more time testing. looks like it has something to do with how it take over the line and dials out. I pickup the phone as it dials and it dial the # pretty quick. faster then a fax machine would. like I stated already if I dial the # on my voip headset it connects not problem with out the "not covered by your tariff plane" msg.
I am able to send faxes no problem and the fax machine dials out fine. but for some reason every time I run a test on the central alarm I get the same error. it was working good in the past.
anyone have any ideas what it could be??
I am able to send faxes no problem and the fax machine dials out fine. but for some reason every time I run a test on the central alarm I get the same error. it was working good in the past.
anyone have any ideas what it could be??
-
- Just Passing Thru
- Posts: 21
- Joined: 11/04/2012
- SIP Device Name: PAP2T
- ISP Name: Telus's
- Computer OS: Win 7 Pro
- Router: Linksys RV042
Re: central alarm not working anymore
When I switched to FPL a few years ago, I had concerns about the stability and security of using the voip service. I contacted my monitoring service (Reliance Protecteron) and told them I wanted to cancel my service because they didn't support voip and I was ditching my traditional phone line. At the time, I was paying roughly $20 per month for monitoring. They said if I committed to a 3 year term, they would install a GSM link (cellular) for an extra $5.00 per month.
I would recommend you taking this approach since it's so frustrating to get data to run through a voip line consistently.
I would recommend you taking this approach since it's so frustrating to get data to run through a voip line consistently.
-
- Lightly Seasoned
- Posts: 199
- Joined: 06/09/2010
- SIP Device Name: SPA3102
- Firmware Version: 5.2.13(GW002)
- ISP Name: Cogeco Cable
- Router: Sagemcom F@ST3896 V2 Cogeco
- Location: Burlington, Ontario
Re: central alarm not working anymore
Perhaps the Alarm Force dialer is sending the data too quickly as you have heard on the line thus " not covered by your Tariff" See if you can get alarm force to remotely login to your panel, setup the dialer to pause 2 seconds before dialing out. I trust in your configuration you have a line seizure jack in the configuration so no one else can use the phone when it goes into alarm thus defeating the ability to dial out to the alarm montoring.
Good Luck
Good Luck