Odd communications failure with alarm system
Posted: Sat May 29, 2010 12:00 pm
My alarm system recently stopped playing nicely with Ooma (or vise-versa). Any help you have is appreciated:
1. Up until 5/27, everything was working fine.
2. Now, I have a persistent "communications failure" on my alarm panel.
3. My alarm dial code is: D1866349xxxx where the "D" stands for "wait for dial tone".
4. I tried to change my dial code to the following:
a) ppD1866349xxxx (where p's are 2 second pauses)
b) D*99p1866349xxxx
c) ppD*99p1866349xxxx
d) all the above permutations without the D
5. I have confirmed that the alarm panel is seizing the line properly
Some questions I have:
1. Is there any way to get the OOMA musical dialtone to just be a regular dial-tone?
2. Did anything specific change with the OOMA service level on 5/27?
The only other change in my system around that time was that my number port from time warner cable was completed. I used to have the old line in the Hub "Wall" port, but disconnected that. I was under the impression that this did not at all affect outbound calling (since that was happing over OOMA from day 1)? Is this possibly relevant?
Any thoughts? Thanks in advance!
1. Up until 5/27, everything was working fine.
2. Now, I have a persistent "communications failure" on my alarm panel.
3. My alarm dial code is: D1866349xxxx where the "D" stands for "wait for dial tone".
4. I tried to change my dial code to the following:
a) ppD1866349xxxx (where p's are 2 second pauses)
b) D*99p1866349xxxx
c) ppD*99p1866349xxxx
d) all the above permutations without the D
5. I have confirmed that the alarm panel is seizing the line properly
Some questions I have:
1. Is there any way to get the OOMA musical dialtone to just be a regular dial-tone?
2. Did anything specific change with the OOMA service level on 5/27?
The only other change in my system around that time was that my number port from time warner cable was completed. I used to have the old line in the Hub "Wall" port, but disconnected that. I was under the impression that this did not at all affect outbound calling (since that was happing over OOMA from day 1)? Is this possibly relevant?
Any thoughts? Thanks in advance!