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..
Event Type: Error
Event Source: Cisco CallManager
Event Category: None
Event ID: 3
Time: 2:53:48 PM
Error: DeviceUnregistered - Device unregistered.
Device name.: SEP000F1FA22BB9
Device IP address.: 192.168.2.36
Device type. [Optional]: 30016
Device description [Optional].: SEP000F1FA22BB9
Reason Code [Optional].: 9
App ID: Cisco CallManager
Cluster ID: ICSCCM1-Cluster
Node ID: 172.17.0.21
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.
Recommended Action: No action is required if unregistration of this device was expected..
MRP3-8FXS#sh controllers t1
T1 1/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
Description: Connect to T1 trunk
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20020812, FPGA: 11
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
Data in current interval (649 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...