Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Is it possible to monitor Cisco devices (phones, ATAs) other than ping

Is there a way to monitor specific devices in Cisco Communications Manager and be alerted when they are unregistered? I have some devices setup to alert when Orion cannot ping them, but I have found some Cisco ATAs that are still pingable but not registered in CM and not working as a result. I am not having much luck finding any solutions when I search for ways to do this. I feel like there must be some way...

Find more posts tagged with

cisco_unified_communications_manager

Accepted answers

FormerMember

If you have VoIP and Network Quality Manager you can create an alert that will email or text someone when a device becomes unregistered. You can filter it by name or MAC for only the devices you want to monitor.

All comments

zennifer

I found 3 suggestions that may get you pointed in the right direction. I think you need to get Cisco set up, then attempt to catch the traps in Solarwinds.

In Cisco:

You can configure the Real Time Monitoring tool to alert you based on multiple criterias, but I think this will be helpful:

Error Message

CCM_CALLMANAGER-CALLMANAGER-3-DeviceUnregistered : Device unregistered. Device name. [String] Device MAC address [Optional]. [String] Device IP address [Optional]. [String] Protocol. [String] Device type. [Optional] [Enum]Device description [Optional]. [String] Reason Code [Optional]. [Enum]IPV6Address [Optional]. [String] IPAddressAttributes [Optional]. [Enum]IPV6AddressAttributes [Optional]. [Enum]

Explanation A device that has previously registered with Cisco CallManager has unregistered. This event may be issued as part of normal unregistration event or due to some other reason such as loss of keepalives. In cases of normal unregistration with Reason Code 'CallManagerReset', 'CallManagerRestart', or 'DeviceInitiatedReset', the severity of this alarm is lowered to INFORMATIONAL.

Recommended Action No action is required if unregistration of this device was expected. If the Reason is ConfigurationMismatch, go to the Device configuration page, make a change to the Description field, save, then reset the device.

Here is the link to the document:

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/managed_services/8_5_1/CUCM/ServErrMess.html#wp2017383

and also this one:

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/err_msgs/7_x/ccmalarms712.html

In RTMT, you already have a PreConfigured Alert named as "NumberOfRegisteredPhonesDropped",

You can find that under Alert-Central, Check out whether that will be usefull for your need.

The Other Option for you to get a Notification on Phone Unregistration is by Configuring the Alarms under Serviceability.

There you can find the Alarm Event "DeviceUnregistered"

Please make use of the below link

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/5_0_1/ccmsrva/saalarm.html

jhill7

Thanks for your response. I am looking for a way to do this with Solarwinds Orion. I have already researched these options with CUCM and RTMT and it does not do what I am looking for.

HerrDoktor

I found some syslog capabilities on my SPA504G, maybe you can configure the devices to send Syslogs to the Orion Server and put alerts on those.

I didn't find any SNMP function on my phone...maybe the "top-series" has SNMP...

sploy

have you given a UnDP any thoughts on using? I have not used this in particular, but upon reading your concern, it UnDP comes to mind first.

HerrDoktor

UnDP relies on SNMP, so we need to clarify if SNMP is working on those devices.

but if it works, your input is correct

FormerMember

dmartzall

Have you tried doing an SNMP walk on the device yet to see what is being exposed via SNMP? Cisco is usually pretty good about making their devices able to be monitored via SNMP. I haven't worked with Cisco phone systems in a while and when I did we were using HP Node Manager.

rschroeder

THIS! ^

HerrDoktor

Of course this is the best way, however it seems that @jhill7 doesn’t have VNQM...

jhill7

@bsch, this would be exactly what I am looking for! And I do have VNQM...just didn't know this was an option. However, I tested this out with many different settings this morning and it doesn't seem to be working. Bummer! I thought this was going to be the answer. Not sure why, but VNQM seems to be seeing the phone I am testing with as rejected. The phone was plugged in and registered in CUCM, then I unplugged it and the alert was never triggered. When I set it to a status of anything other than registered, the alert was trigger because VNQM showed it as rejected, despite it being registered in CUCM. Strange...

rschroeder

It this turns out to be a VNQM limitation, are you participating in the current VNQM Beta? It's a great place to discover what the new version can do, and it's the right location to make folks aware of a short-coming or a need.

jhill7

I did some more testing and the alert seems to be working now, just with a 15 minute delay. I am going to try and figure out if there is way to adjust the timing (just not sure what setting is checking device registrations) but I think this is going to work out for me. Thanks so much bsch!