Nextalarm used to be big to connect the alarm panels to VOIP via an ABN (dongle) between the router/modem and the digital communicator. Think of it as primitive dialer capture and retransmission via IP to them. The panel's programming, telephone and account # wouldn't need to be modified as the data was captured by their device and then the generic CID signals transmitted via their ABN (which has it's own acct. #) to their CS and translated from there....but that's not applicable in this case then.
so it's dialup (layman's term) and cellular via serial port (full data transmitted via DB9 between units) so in this case the fact of the matter is as I said, their automation software is summing the information incorrectly, either via their template (or lack of) which tells their automation software the difference between a (different panel reference) keypad police panic as zone 99 vs. 000 (GE vs. Ademco in this case) and what pops up on the screen at the CS and the appropriate information displayed to the operator or on the web interface.
The CID code and extended information is correct, it's automatic when you enable reporting of that event type and the CID code is listed in RP and is not changable as a value. The error is on their part, as I stated, I have multiple M1's reporting correctly to my CS and the extended information (module number, etc.) following the event code and all report correctly, show in the account's event log at the CS correctly as well as is reported to the end user correctly. You can't change what a panel sends in hard coded information.
