<div>Hi List,</div>
<div> </div>
<div>Since two weeks I have issues with my IP Phones, after check CCM 4.0 I saw a lot of errors by device unregistered, and my users are complain because the calls in course are dropped. I don't know why the IP Phones unregistered, pls any suggestions... thanks.
</div>
<div> </div>
<div>My CCM logs are:</div>
<div> </div><font face="Courier New" size="2">
<p>Event Type: Error</p>
<p>Event Source: Cisco CallManager</p>
<p>Event Category: None</p>
<p>Event ID: 3</p>
<p>Date: 16/08/2007</p>
<p>Time: 10:25:04 a.m.</p>
<p>User: N/A</p>
<p>Computer: PECMA01</p>
<p>Description:</p>
<p>Error: DeviceUnregistered - Device unregistered.</p>
<p>Device name.: SEP0013605818CA</p>
<p>Device IP address.: <a href="http://10.20.0.132">10.20.0.132</a></p>
<p>Device type. [Optional]: 30007</p>
<p>Device description [Optional].: Patricia Verastegui 2237</p>
<p>Reason Code [Optional].: 8</p>
<p>App ID: Cisco CallManager</p>
<p>Cluster ID: PECMA01-Cluster</p>
<p>Node ID: <a href="http://10.20.0.16">10.20.0.16</a></p>
<p>Explanation: A device that has previously registered with Cisco CallManager</p>
<p>has unregistered. This event may be issued as part of normal unregistration</p>
<p>event or due to some other reason such as loss of keepalives.</p>
<p>Recommended Action: No action is required if unregistration of this device</p>
<p>was expected..</p>
<p> </p>
<p> </p>
<p>Event Type: Error</p>
<p>Event Source: Cisco CallManager</p>
<p>Event Category: None</p>
<p>Event ID: 3</p>
<p>Date: 16/08/2007</p>
<p>Time: 10:24:52 a.m.</p>
<p>User: N/A</p>
<p>Computer: PECMA01</p>
<p>Description:</p>
<p>Error: DeviceUnregistered - Device unregistered.</p>
<p>Device name.: SEP00131A41940B</p>
<p>Device IP address.: <a href="http://10.20.1.114">10.20.1.114</a></p>
<p>Device type. [Optional]: 30007</p>
<p>Device description [Optional].: Stephanie Kilimajer 2215</p>
<p>Reason Code [Optional].: 8</p>
<p>App ID: Cisco CallManager</p>
<p>Cluster ID: PECMA01-Cluster</p>
<p>Node ID: <a href="http://10.20.0.16">10.20.0.16</a></p>
<p>Explanation: A device that has previously registered with Cisco CallManager</p>
<p>has unregistered. This event may be issued as part of normal unregistration</p>
<p>event or due to some other reason such as loss of keepalives.</p>
<p>Recommended Action: No action is required if unregistration of this device</p>
<p>was expected..</p>
<p> </p>
<p> </p>
<p>Event Type: Error</p>
<p>Event Source: Cisco CallManager</p>
<p>Event Category: None</p>
<p>Event ID: 3</p>
<p>Date: 16/08/2007</p>
<p>Time: 10:24:34 a.m.</p>
<p>User: N/A</p>
<p>Computer: PECMA01</p>
<p>Description:</p>
<p>Error: DeviceTransientConnection - Transient connection attempt.</p>
<p>Connecting Port: 0</p>
<p>Device name [Optional].:</p>
<p>Device IP address.: <a href="http://10.20.20.45">10.20.20.45</a></p>
<p>Device type. [Optional]: 255</p>
<p>Reason Code [Optional].: 6</p>
<p>App ID: Cisco CallManager</p>
<p>Cluster ID: PECMA01-Cluster</p>
<p>Node ID: <a href="http://10.20.0.16">10.20.0.16</a></p>
<p>Explanation: A connection was established and immediately dropped before</p>
<p>completing registration. Incomplete registration may indicate a device is</p>
<p>rehoming in the middle of registration. The alarm could also indicate a</p>
<p>device misconfiguration, database error, or an illegal/unknown device</p>
<p>trying to attempt a connection.</p>
<p>Recommended Action: No action is required if this event was issued as a</p>
<p>result of a normal device rehome..</p>
<p> </p>
<p> </p>
<p> </p>
<p>Event Type: Error</p>
<p>Event Source: Cisco CallManager</p>
<p>Event Category: None</p>
<p>Event ID: 3</p>
<p>Date: 16/08/2007</p>
<p>Time: 10:24:29 a.m.</p>
<p>User: N/A</p>
<p>Computer: PECMA01</p>
<p>Description:</p>
<p>Error: DeviceUnregistered - Device unregistered.</p>
<p>Device name.: SEP001360581428</p>
<p>Device IP address.: <a href="http://10.20.1.164">10.20.1.164</a></p>
<p>Device type. [Optional]: 30007</p>
<p>Device description [Optional].: Ursula Quevedo 1897</p>
<p>Reason Code [Optional].: 9</p>
<p>App ID: Cisco CallManager</p>
<p>Cluster ID: PECMA01-Cluster</p>
<p>Node ID: <a href="http://10.20.0.16">10.20.0.16</a></p>
<p>Explanation: A device that has previously registered with Cisco CallManager</p>
<p>has unregistered. This event may be issued as part of normal unregistration</p>
<p>event or due to some other reason such as loss of keepalives.</p>
<p>Recommended Action: No action is required if unregistration of this device</p>
<p>was expected..</p>
<p> </p>
<p> </p>
<p> </p>
<p>Event Type: Error</p>
<p>Event Source: Cisco CallManager</p>
<p>Event Category: None</p>
<p>Event ID: 3</p>
<p>Date: 16/08/2007</p>
<p>Time: 10:23:54 a.m.</p>
<p>User: N/A</p>
<p>Computer: PECMA01</p>
<p>Description:</p>
<p>Error: DeviceTransientConnection - Transient connection attempt.</p>
<p>Connecting Port: 2000</p>
<p>Device name [Optional].: SEP0012D9167518</p>
<p>Device IP address.: <a href="http://10.20.1.228">10.20.1.228</a></p>
<p>Device type. [Optional]: 30007</p>
<p>Reason Code [Optional].: 1</p>
<p>App ID: Cisco CallManager</p>
<p>Cluster ID: PECMA01-Cluster</p>
<p>Node ID: <a href="http://10.20.0.16">10.20.0.16</a></p>
<p>Explanation: A connection was established and immediately dropped before</p>
<p>completing registration. Incomplete registration may indicate a device is</p>
<p>rehoming in the middle of registration. The alarm could also indicate a</p>
<p>device misconfiguration, database error, or an illegal/unknown device</p>
<p>trying to attempt a connection.</p>
<p>Recommended Action: No action is required if this event was issued as a</p>
<p>result of a normal device rehome..</p>
<p></p></font>
<p> </p>
<div><br clear="all"><br>-- <br>Omar E.P.T<br> </div>