Cisco SPA112 Internet Telephony Adapter Not Working (As of Feb. 7, 2017)
I just got off the telephone with my home alarm company. Our alarm system uses a Cisco SPA112 Internet Telephony Adapter using a SIP Protocol to communicate with the monitoring company. They use Ports 5060, 5065, 9000-9049, and 16384-16482.
As of February 7th, the system stopped working properly. Although the Cisco Adapter is calling the alarm company when the system detects an alarm, they are not receiving specific signals related to the exact nature of that alarm.
Like the issues that people are describing in this post:
I believe that this problem is directly related to some change that HughesNet engineers made on February 7th. Switching the DNS server to 220.127.116.11 solved the issues described in that post, but there are these unresolved problems with my home alarm's ability to communicate with the alarm monitoring company. This issue is more serious because it puts us at risk for burglaries and fires with no response from the monitoring company.
If your engineers need further information, they can call me at 760-415-2670 and/or I can put them in touch with a technical support professional with whom I have been working at my alarm monitoring company.