[cisco-voip] IP Phones unregisters at the same time CCM 4.1(3)sr1

Wed Feb 8 17:35:28 EST 2006

Here is what it says for the re-registers for one of the devices. There
is nothing with the "last" keyword. Hope this helps. Thanks all.

02/05/2006 20:25:17.802 CCM|DeviceUnregistered - Device unregistered.
Device name.:SEP0012D9845906 Device IP address.:172.16.25.11 Device
type. [Optional]:7 Device description [Optional].:HelpDesk - Desc Reason
Code [Optional].:9 App ID:Cisco CallManager Cluster ID:OGP19022B-Cluster
Node
ID:172.17.1.11|<CLID::OGP19022B-Cluster><NID::172.17.1.11><CT::AlarmSEP0
012D9845906><DEV::SEP0012D9845906>

02/05/2006 20:25:17.817 CCM|Socket Broken. DeviceName=Unknown, TCPPid =
[2.100.132.8876], IPAddr=Unknown IP Address, Port=0x0, Device
Controller=[0,0,0]|<CLID::OGP19022B-Cluster><NID::172.17.1.11><CT::2,100
,132,8876.1><IP::><DEV::>

02/05/2006 20:25:54.365 CCM|LineControl(8930) - registered with
Duplicate DeviceName SEP0012D9845906, force the device to do the
reregister: single device
case|<CLID::OGP19022B-Cluster><NID::172.17.1.11><CT::1,100,119,1.5012886
><IP::172.16.25.11><DEV::SEP0012D9845906>

02/05/2006 20:25:54.365 CCM|LineControl(8931) - registered with
Duplicate DeviceName SEP0012D9845906, force the device to do the
reregister: single device
case|<CLID::OGP19022B-Cluster><NID::172.17.1.11><CT::1,100,119,1.5012886
><IP::172.16.25.11><DEV::SEP0012D9845906>

-----Original Message-----
From: Ed Leatherman [mailto:ealeatherman at gmail.com] 
Sent: Wednesday, February 08, 2006 6:21 PM
To: Wes Sisk
Cc: Jose Robles; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] IP Phones unregisters at the same time CCM
4.1(3)sr1

I see large groups of resets sometimes during odd hours that are DHCP
leases expiring or some such similar.

On 2/8/06, Wes Sisk < wsisk at cisco.com <mailto:wsisk at cisco.com> > wrote:

8 = device initiated reset, but CM cannot be trusted in these matters. 
it only reports what it perceives to be the problem.

the phone reports what it believes to be the problem in the ALARM
message in the CCM traces when it re-registers to CM, either the primary
CM or the backup CM. 

1. open cmd prompt
2. "cd \prog*\cisco\trace\ccm"
3. findstr Last= ccm*.txt >last.txt
4. notepad last.txt

The text after the word "last" is the phone's point of view of why it 
unregistered. It is usually more informative (31 possible values as
opposed to 12 possible for CM).

Why does the phone say it unregistered?

Jose Robles wrote:
>
> I have an isue using CM 4.1.3 (sr1). 19 Ip Phones 7960 unregisters
many
> of them at the same time. Ussually at 4pm or 5pm or later when there
> is not much activity at the site. I've seen this problem in another
> forum people complaining with the same situation. This are the Reason 
> code 8 events in the event viewer and in the CCM Trace folder log:
>
>
> 02/06/2006 17:42:28.587 CCM|DeviceUnregistered - Device unregistered.
> Device name.:SEP0013193E52AB Device IP address.: 172.16.x.x Device
> type. [Optional]:7 Device description [Optional].:Description Phone
> Reason Code [Optional].:8 App ID:Cisco CallManager Cluster
> ID:1902-Cluster Node
> ID:172.17.x.x|<CLID::1902-Cluster><NID::
172.17.x.x><CT::AlarmSEP0013193E52AB><DEV::SEP0013193E52AB>
>
>
>
> The description for Event ID ( 3 ) in Source ( Cisco CallManager )
> cannot be found. The local computer may not have the necessary 
> registry information or message DLL files to display messages from a
> remote computer. You may be able to use the /AUXSOURCE= flag to
> retrieve this description; see Help and Support for details. The 
> following information is part of the event: DeviceUnregistered -
> Device unregistered.
> Device name.: SEP0012D9B95154
> Device IP address.: 172.17.x.x
> Device type. [Optional]: 7
> Device description [Optional].: Sistemas 
> Reason Code [Optional].: 8
> App ID: Cisco CallManager
> Cluster ID: 1902-Cluster
> Node ID: 172.17.x.x
> 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..
>
> 
> I think we are hitting a bug in 4.1.3 sr1. Any ideas?
>
> Thanks again,
>
> Jose A. Robles
> Sr. Network Consultant
> CCNP, CCDP
> CQS Routing and Lan Switching Specialist 
> Netxar Technologies, Inc. - www.netxar.com <http://www.netxar.com>
> 17 Ponce Street
> San Juan, PR 00917
> ph: +1 787 765 0058 x2015 
> fax: +1 787 756 5362
> cel: +1 787 547-0149
> email jose.robles at netxar.com <mailto:jose.robles at netxar.com> 
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip 

-- 
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060208/a479cedf/attachment-0001.html