I'm trying to better understand how RTMT works with regards to device search and in particular a device search for unregistered phones. We have a particular branch office that seems to be having connectivity issues, but our networking team is having trouble even confirming it's happening. We've been relying on RTMT to see the branch office phones unregister in order to alert the networking team what time we see issues happening. However, this past week an event happened that has made us question the validity of what we're seeing because we apparently don't understand how the tool works.
This past week our main office experienced a power outage and the phones on a particular PoE switch went down because that switch is not on a UPS. So we went into RTMT a couple of hours afterward to look at the list of unregistered phones from that power outage. We did not see any of the phones listed that we were expecting. It's as if they never unregistered.
So thinking it works on some type of polling interval, I powered off a phone for 5 minutes and then checked RTMT. I did see that phone in there. However, as soon as it was plugged back in, it was no longer listed in the unregistered phones after a device search. That makes some sense, but doesn't make complete sense why some phones are always listed in the unregistered phone device search. Even while listed in the unregistered phone device search they are currently registered with CUCM. I would expect RTMT to maintain a list of phones that have unregistered for a certain length of time for historical search purposes. It appears to be doing that, but also not doing that.
Based on all of that, it appears I do not understand how the whole mechanism for how phones appear in the unregistered device search. Anybody that can enlighten me to how this all works?
That's probably not a good tool to use for this. Use the syslog viewer and choose the AlternateSyslog. It contains info about phone unregistrations/registrations and also lists the reason the phone went out of service. You'll need to look through the Alternate Syslog on each node though.
The problem with using the Alternate SysLog is that we often end up with phones that spam our log and thus we lose any ability to go back in time to look at the logs to find remote office drops like we're trying to document. Even with the 5 log files in RTMT, they only go back to midnight today because of 2 phones spamming the logs about not finishing registration. We fix those phones when we look, but we're not in the SysLog every day trying to catch these devices spamming the logs. I'll keep your suggestion in mind, though.
However, my question really wasn't answered about HOW the device search reports the items in its list. That's what I'm trying to figure out and was hoping others might have some idea.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...