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)
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!
After you got rid of the cable phone, are you distributing ooma dialtone to the same wall jack that your cable phone device used to?
I now know that the calling is working (ie. not a dialtone issue) since I can see calls (11s to 18s) to my central monitoring station on the Ooma call log.
I just switched my panel to use SIA FSK instead of Contact ID (apparently SIA frequency modulation is more resilient to poor line quality). My system is using the *99 and the first call seemed to work. Fingers crossed.
Ooma CS suggested to bypass ports UDP 3386 and UDP 3480, which he did but could not make it work.