*** Sur-Gard Accounts EXCEEDED......
- Thread starter Mp333
- Start date
Surgard is their receiver.
It's an issue with the CS, but what, I couldn't tell you. Could be you sending too much traffic to them (some CS have a basic # of signal cap, then charge for overages) or they have too many accounts on their receiver.
Contact them, but it's not a reassuring thing to see in my head.
Who's lifebeacon? Are you in ID?
It's an issue with the CS, but what, I couldn't tell you. Could be you sending too much traffic to them (some CS have a basic # of signal cap, then charge for overages) or they have too many accounts on their receiver.
Contact them, but it's not a reassuring thing to see in my head.
Who's lifebeacon? Are you in ID?
drvnbysound
Senior Member
What flavor of cell is it? Give details.
I don't understand how you don't know who monitors it....that shouldn't be a secret, no matter if it's wholesale or not.
When I go to the IP, it's not rackspace I'm seeing. Someone else.
It's not a CS. UL wouldn't allow the data and receiver/path to be offsite.
I'd need more information and screen shots to see what's going on and who's issue it really is.
I don't understand how you don't know who monitors it....that shouldn't be a secret, no matter if it's wholesale or not.
When I go to the IP, it's not rackspace I'm seeing. Someone else.
It's not a CS. UL wouldn't allow the data and receiver/path to be offsite.
I'd need more information and screen shots to see what's going on and who's issue it really is.
Without seeing the entire display, screen and making a couple assumptions.....
I don't know how they have the Uplink reporting to Affiliated, either POTS emulation or direct IP port to them, that would have to be answered by them.
They have the Uplink programmed for daily test. That is being reported in addition to the M1's weekly test. They need to pick which unit is performing the dialer test to the CS and correct. I prefer the M1 to handle the dialer test. (If you did dialer redirect, that's really the only place you'd change who's doing the reporting).
Assuming the column that has "JO" in it is raw data as sent to the CS, it looks like they set the Uplink to send SIA (not really my first choice) as the communications reporting method. JO would be the RC for log overflow. (transmitter log overflow) and which device that is here, would be what I'd question.....it's not the M1, it doesn't have the report code, so I don't see it coming or being generated by that. That would mean it's coming from the 4500 most likely.
I'd still need to know more of what you're posting screenshots of and what settings and config is in the uplink, M1 and XEP. to point fingers.
I don't know how they have the Uplink reporting to Affiliated, either POTS emulation or direct IP port to them, that would have to be answered by them.
They have the Uplink programmed for daily test. That is being reported in addition to the M1's weekly test. They need to pick which unit is performing the dialer test to the CS and correct. I prefer the M1 to handle the dialer test. (If you did dialer redirect, that's really the only place you'd change who's doing the reporting).
Assuming the column that has "JO" in it is raw data as sent to the CS, it looks like they set the Uplink to send SIA (not really my first choice) as the communications reporting method. JO would be the RC for log overflow. (transmitter log overflow) and which device that is here, would be what I'd question.....it's not the M1, it doesn't have the report code, so I don't see it coming or being generated by that. That would mean it's coming from the 4500 most likely.
I'd still need to know more of what you're posting screenshots of and what settings and config is in the uplink, M1 and XEP. to point fingers.
drvnbysound
Senior Member
DELInstallations said:
LOL, I didn't even think about trying to resolve the IP in a browser...
Mp333, look at what's there... http://184.106.251.224/
Mp333
Active Member
Here are the XEP details and the CS info...Not sure how to get the uplink info.....
Name: XEP
MAC Addr: 00-40-9D-BA-DB-AD
IP Addr: 192.168.1.150
Secure Port: 2601
M1XEP serial port OK: Yes
M1XEP has initialized: Yes
DHCP: No
Subnet: 255.255.255.0
Gateway: 192.168.1.1
Pri DNS: 192.168.1.1
Sec DNS: 0.0.0.0
Non-secure Port: 2101
AMX Beacon: No
Email Server: smtp.aol.com (URL)
Email Port: 587
Email From Addr: [email protected]<script data-cfhash='f9e31' type="text/javascript">/* */</script>
Email Username: [email protected]<script data-cfhash='f9e31' type="text/javascript">/* */</script>
Email POP before SMTP: No
DDNS Server: nic.changeip.com (URL)
DDNS Username: [email protected]
DDNS Hostname: xxxxxx.changeip.net
DDNS Email To: [email protected]
DDNS Email on Change: Yes
SNTP Server: wwv.nist.gov (URL)
SNTP Update Time: 03:03
SNTP Time Zone: GMT-5.00
SNTP Email on Errors: Yes
Bootware Version: 1.2.0
Application Version: 1.3.28
Problems:
The M1XEP's MAC address is invalid. Please contact Technical Support about this.
Name: XEP
MAC Addr: 00-40-9D-BA-DB-AD
IP Addr: 192.168.1.150
Secure Port: 2601
M1XEP serial port OK: Yes
M1XEP has initialized: Yes
DHCP: No
Subnet: 255.255.255.0
Gateway: 192.168.1.1
Pri DNS: 192.168.1.1
Sec DNS: 0.0.0.0
Non-secure Port: 2101
AMX Beacon: No
Email Server: smtp.aol.com (URL)
Email Port: 587
Email From Addr: [email protected]<script data-cfhash='f9e31' type="text/javascript">/* */</script>
Email Username: [email protected]<script data-cfhash='f9e31' type="text/javascript">/* */</script>
Email POP before SMTP: No
DDNS Server: nic.changeip.com (URL)
DDNS Username: [email protected]
DDNS Hostname: xxxxxx.changeip.net
DDNS Email To: [email protected]
DDNS Email on Change: Yes
SNTP Server: wwv.nist.gov (URL)
SNTP Update Time: 03:03
SNTP Time Zone: GMT-5.00
SNTP Email on Errors: Yes
Bootware Version: 1.2.0
Application Version: 1.3.28
Problems:
The M1XEP's MAC address is invalid. Please contact Technical Support about this.
Attachments
They don't have a DNIS number configured but it's checked. That's a red flag for me, especially with Surgard receiver configuration. Tells me the monitoring isn't properly set up on both ends with IP.
In this case, I'd need to see what is configured in the Uplink, and the CS details, such as their protocol and head end/automation. I already know the main portion of the monitoring isn't correct.
In this case, I'd need to see what is configured in the Uplink, and the CS details, such as their protocol and head end/automation. I already know the main portion of the monitoring isn't correct.
