Explanation: A connection was established and immediately dropped before completing registration. Incomplete registration may indicate a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection.
Recommended Action: No action is required if this event was issued as a result of a normal device rehome..
These errors come from ip address 10.101.219.160 to 167.
These ip addresses are not from any registered phone or gateway. Moreover, device type = 255 means unknown, and reason code = 3 means database error.
Re: lots of DeviceTransientConnection in the application log
Yes, i have been investigating meanwhile and i found an WS-X6608 blade recently installed by somebody in a remote catalyst. For sure it was the reason of such amount of errors.
I deployed an ACL to prevent the WS-X6608 sending requests to the Callmanagers and these error messages got over. I will investigate what kind of problem or missconfiguration (if it is the case) is causing such behaviour.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
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 ...