[cisco-voip] Phones reset... For no reason
Lelio Fulgenzi
lelio at uoguelph.ca
Wed Feb 23 20:10:01 EST 2005
You can also get this information directly from the phone, under network statistics.
This page gives you a summary. The one you mention I've run into before. It's the dreaded IP address conflict.
The following list defines components of text messages that might display on the phone's LCD screen:
.Rcv-number of packets received at the phone.
.Xmt-number of packets transmitted from the phone.
.REr-number of receive errors at the phone.
.Bcast-number of broadcast packets received.
.TCP-timeout-connection closed due to exceeding the allowed retry time.
.TCP-Bad-ACK-connection closed because an unacceptable ACK was received.
.CM-reset-TCP-Cisco CallManager closed and initiated the closing of connection.
.CM-closed-TCP-Cisco CallManager closed and initiated the closing of connection.
.CM-aborted-TCP-Cisco CallManager closed and initiated the closing of connection.
.CM-NAKed-Cisco CallManager refused the connection attempt.
.KeepaliveTO-phone closed because of a Keepalive Timeout.
.Failback-phone closed due failback to a higher priority Cisco CallManager.
.Phone-Loading-phone closed to upgrade software. This message appears only if TFTP fails during software upgrade.
.Phone-Keypad-phone closed due to a **#** reset.
.Phone-Re-IP-phone closed due to a duplicate IP address condition.
.Reset-Reset-phone closed due to receiving a Reset/Reset from Cisco CallManager administration.
.Reset-Restart-phone closed due to receiving a Reset/Restart from Cisco CallManager administration.
.All-CMs-Bad-phone detected a state in which all Cisco CallManager servers failed their keepalives.
.Phone-Reg-Rej-phone closed due to receiving a registration reject.
.Phone-Initialized-phone has not experienced a connection close since the hardware reset or since it was powered on.
.Elapsed time-the amount of time that has elapsed since the phone connected to Cisco CallManager.
.Port 0 Full, 100-network port is in a link up state and has auto-negotiated a full-duplex 100 Mbps connection.
.Port 0 Half, 10-the network port is in a link up state and has auto-negotiated a half-duplex, 10-Mbps connection.
.Port 1 Full, 100-the PC port is in a link up state and has auto-negotiated a full-duplex 100-Mbps connection.
.Port 2 Down-PC port is in a link down state.
----- -----
Lelio Fulgenzi, B.A. lelio at uoguelph.ca.eh
Network Analyst (CCS)
University of Guelph FAX:(519) 767-1060 JNHN
Guelph, Ontario N1G 2W1 TEL:(519) 824-4120 x56354
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
remove the 1st letter of the canadian alphabet from my email, eh!
----- Original Message -----
From: Grabowski, David
To: cisco-voip at puck.nether.net
Sent: Wednesday, February 23, 2005 6:01 PM
Subject: RE: [cisco-voip] Phones reset... For no reason
Thx for the reply, Wes...
CM traces say, "Last=Phone-Re-IP"
DHCP renew?
Why would that cause the phones to reset?
> -----Original Message-----
> From: Wes Sisk [mailto:wsisk at cisco.com]
> Sent: Wednesday, February 23, 2005 5:42 PM
> To: Grabowski, David
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Phones reset... For no reason
>
> When the phones re-register the first time after
> unregistration, they report the reason they last unregistered from CM.
> Search for "Last=" in the detailed CCM traces, likely on the
> backup server, or if phones could not connect to backup
> either, then the message would appear in the traces on the primary.
>
> The event viewer messages gives the server side of the story
> 'why did the phones unregister'
> the Last= text gives the phone side of the story.
>
> /Wes
>
> Grabowski, David wrote:
>
> >CM 3.3(4)sr2. One pub, one sub. About 50 phones, all 7960's.
> >
> >Over the weekend, I upgraded from OS 2000-2-6sr5 to 2000-2-7sr2.
> >
> >This afternoon, for seemingly no reason, most of our phones
> just reset.
> >Event logs on the sub show a deregistration. Nothing else.
> >
> >Opened a case with TAC. They claim that since our servers
> >(MCS-7825-1133) are configured for autonegotiation, as are our 6500
> >switches, that this must be the problem. I disagree.
> >
> >1. They've been this way for more than a year.
> >2. No (as in zero) errors on the switch ports. No (as in
> zero) errors
> >on the servers (netstat -e). Usually, when there's an
> autonegotiation
> >problem, we'd see errors 3. We have a third-party app that
> monitors the
> >server, down to the windows services. If there was a
> connectivity issue
> >(such that most of the phones would lose connection to it),
> one would
> >figure that our monitoring app would have had issues
> connecting to the
> >server and verifying that the services were up
> >
> >The only things that have happened recently are..
> >
> >1. The OS upgrade mentioned above
> >2. I was using IP Communicator on a desktop. Couldn't do a meet-me
> >conference -- not sure why not. Event logs show errors with
> >"ConferenceNoMoreResourcesAvailable" (I doubt that this is related,
> >just including it here for completeness)
> >
> >Any ideas?
> >#############################################################
> ##########
> >##############
> >CONFIDENTIAL: This e-mail, including its contents and
> attachments, if any, are confidential. It is neither an offer
> to buy or sell, nor a solicitation of an offer to buy or
> sell, any securities or any related financial instruments
> mentioned in it. If you are not the named recipient please
> notify the sender and immediately delete it. You may not
> disseminate, distribute, or forward this e-mail message or
> disclose its contents to anybody else. Unless otherwise
> indicated, copyright and any other intellectual property
> rights in its contents are the sole property of Mizuho
> Securities USA Inc.
> > E-mail transmission cannot be guaranteed to be secure
> or error-free. The sender therefore does not accept liability
> for any errors or omissions in the contents of this message
> which arise as a result of e-mail transmission. If
> verification is required please request a hard-copy version.
> > Although we routinely screen for viruses, addressees
> should check this e-mail and any attachments for viruses. We
> make no representation or warranty as to the absence of
> viruses in this e-mail or any attachments. Please note that
> to ensure regulatory compliance and for the protection of our
> customers and business, we may monitor and read e-mails sent
> to and from our server(s).
> >#############################################################
> ##########
> >##############
> >
> >_______________________________________________
> >cisco-voip mailing list
> >cisco-voip at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
>
#####################################################################################
CONFIDENTIAL: This e-mail, including its contents and attachments, if any, are confidential. It is neither an offer to buy or sell, nor a solicitation of an offer to buy or sell, any securities or any related financial instruments mentioned in it. If you are not the named recipient please notify the sender and immediately delete it. You may not disseminate, distribute, or forward this e-mail message or disclose its contents to anybody else. Unless otherwise indicated, copyright and any other intellectual property rights in its contents are the sole property of Mizuho Securities USA Inc.
E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
Although we routinely screen for viruses, addressees should check this e-mail and any attachments for viruses. We make no representation or warranty as to the absence of viruses in this e-mail or any attachments. Please note that to ensure regulatory compliance and for the protection of our customers and business, we may monitor and read e-mails sent to and from our server(s).
#####################################################################################
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050223/d46c65e3/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 43 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20050223/d46c65e3/attachment-0001.gif
More information about the cisco-voip
mailing list