[cisco-voip] phone rebooting itself
Ryan Ratliff
rratliff at cisco.com
Fri Feb 6 10:00:15 EST 2009
More recent versions don't have them in the Admin guide but they are
in the System Error Messages doc for each version.
http://cisco.com/en/US/docs/voice_ip_comm/cucm/err_msgs/7_x/
ccmalarms701.html (7.0)
Be aware though that this is just the reason that CUCM thinks the
phone unregistered for and is pretty general (and not entirely
accurate in some cases). To get a more accurate unregister reason
you can look at the sccp alarm message the phone sends the next time
it registers (most likely to the backup CUCM server or SRST router).
In CCM traces search for the text "last=". This is where the phone
indicates the reason it last unregistered from CUCM.
As Jason mentioned if you've got phones losing connection to CUCM
then you need to get a packet capture from behind the phone (and
preferably at the CUCM for the same time period). It really doesn't
take long for newer phones to time out a TCP session if it is not
getting TCP Acks from CUCM.
-Ryan
On Feb 5, 2009, at 9:16 PM, Lelio Fulgenzi wrote:
This document lists the reasons as well.
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/3_2/
english/administration/guide/7900trb4.html#wp1020334
Unfortunately, it's from CCM 3.x, but unfortunately the more recent
documents don't include the detail this one does.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt
----- Original Message -----
From: "Jason Burns" <burns.jason at gmail.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "Scott Kee" <SKee at cmsstl.com>, cisco-voip at puck.nether.net
Sent: Thursday, February 5, 2009 8:54:36 PM GMT -05:00 US/Canada Eastern
Subject: Re: [cisco-voip] phone rebooting itself
Get a packet capture are the back of the phone after enabling Span to
PC Port on the phone config page. That will definitively tell you why
the phone unregisters.
On Wed, Feb 4, 2009 at 9:12 AM, Lelio Fulgenzi <lelio at uoguelph.ca>
wrote:
Double check the requirements for phones across a WAN and make sure
you within spec.
That's the first thing.
Second thing, test the reliability of your WAN link with a ping
plotter tool of some type from HQ to the remote site. You may have a
fast link, but if it goes down for whatever reason, for any period of
time you'll see what you are seeing now.
The 7911s are even more susceptible to this (or more resilient,
depending on your thinking) - they failover rather quickly.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt
----- Original Message -----
From: "Scott Kee" <SKee at cmsstl.com>
To: cisco-voip at puck.nether.net
Sent: Tuesday, February 3, 2009 7:15:23 PM GMT -05:00 US/Canada Eastern
Subject: [cisco-voip] phone rebooting itself
I have a remote office that has 25 phones: 1 7975, 2 7965, and rest
are 7945.
All the phones are connected to the WS-C3560-48PS-S switch.
I am using H323 on the Cisco 2811.
Problem: time to time phones reboots itself or disconnects from the
call manager and gives below messages.
-UCB failure error
-certainly drops the call when they are on the phone
-it goes in to SRST mode(failover mode)-- it comes right backup.
I worked with Cisco TAC but they are saying the phone lost the
connection to the Call Manager.
Why it loses the connection to the CM?
Maybe the switch is too small to support 25 phones?
Does anyone know what maybe the cause of the issue?
Thanks,
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-
bounces at puck.nether.net] On Behalf Of Pat Hayes
Sent: Tuesday, February 03, 2009 5:44 PM
To: Sean Walberg
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity 5 - Call handlers for announcements
To add to what Bill said, for the port status monitor, make sure you
use the one from tools depot, not the web based one. The web based one
only shows you 'real time' state, where as the tools depot one has a
buffer and will show you the whole call, much easier to follow.
Something else you might consider is using the Audio Text Manager, it
helps to visualize your config and makes things a bit easier to
navigate when you've got a complicated tree:
http://ciscounitytools.com/APP_AudioTextManager403.htm
On Tue, Feb 3, 2009 at 10:19 AM, Sean Walberg <sean at ertw.com> wrote:
> Thanks for the suggestion. I recreated the call handler and it
works now.
> Would have liked to try your suggestion earlier though, I'm
curious why the
> handler didn't work.
>
> Sean
>
> On Tue, Feb 3, 2009 at 9:12 AM, Bill Talley <btalley at gmail.com>
wrote:
>>
>> One last suggestion if you continue to have the problem after
rebuilding
>> the call handler. I apologize if this has already been
mentioned, but you
>> can use the Call Viewer combined with the real time display of
Port Status
>> Monitor in Unity Tools to see where Unity is directing the call
during that
>> portion of the call to verify Unity is performing the expected
handling of
>> the call.
>> As you're probably aware, Call Viewer will just show you digits
>> accompanying the call from Call Manager. Port Status monitor,
when set to
>> real time display mode, will show you the call flow messages
while the call
>> is being handled by Unity identifying which mailbox/handler
answers the call
>> and which greeting is played.
>>
>> HTH
>>
>> On Tue, Feb 3, 2009 at 8:44 AM, Sean Walberg <sean at ertw.com> wrote:
>>>
>>> Thanks Bill,
>>>
>>> I checked and it's set to "Recording". There's a recording
there, too.
>>>
>>> I think I'll just delete this handler and recreated it.
>>>
>>> Sean
>>>
>>> On Sat, Jan 31, 2009 at 9:47 AM, Bill Talley <btalley at gmail.com>
wrote:
>>>>
>>>> Check the standard greeting page for that call hander and
verify the
>>>> radio button to play the greeting is ticked. It sounds like
the radio
>>>> button to play the system greeting is ticked.
>>>>
>>>>
>>>> On 1/30/09, Sean Walberg <sean at ertw.com> wrote:
>>>>>
>>>>> Thanks Scott,
>>>>>
>>>>> There's no call routing rule associated with this. At the
subscriber
>>>>> level, I have a blank greeting and then "After greeting, send
caller to call
>>>>> handler -> Attempt transfer for MBCKND Special Announcement".
>>>>>
>>>>> That call handler provides a menu, pressing 1 takes them to
another
>>>>> call handler that plays a greeting and waits for a digit.
Digits from there
>>>>> take the caller to other handlers, such as 1 for the primetime
lineup, which
>>>>> prompts for a digit from 1-5 corresponding with the day. Each
day is a
>>>>> separate call handler. Only the call handler associated with
#4, Thursday,
>>>>> goes to VM, all the others play the greeting properly.
>>>>>
>>>>> Sean
>>>>>
>>>>> On Fri, Jan 30, 2009 at 2:36 PM, Scott Voll
<svoll.voip at gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Check your call routing rule and see if the others are set
that way
>>>>>> and that one is missing a rule.
>>>>>>
>>>>>> scott
>>>>>>
>>>>>>
>>>>>> On Fri, Jan 30, 2009 at 11:24 AM, Sean Walberg
<sean at ertw.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> The voice mail coverage path of one of my office's front
desk goes to
>>>>>>> a Unity call handler, playing a message like "press 1 for
the programming
>>>>>>> lineup, 2 for the news desk, etc". Callers eventually get to
a menu along
>>>>>>> the lines of "press 1 for Monday, 2 for tuesday", and so forth.
>>>>>>>
>>>>>>> Each of these handlers is a greeting, which plays the
message, then
>>>>>>> kicks the caller back to the menu.
>>>>>>>
>>>>>>> This works great, except for the Thursday handler. When the
caller
>>>>>>> selects the Thursday option, they get a message saying "the
user at
>>>>>>> extension 103 is not available, please leave a message" (103
is the
>>>>>>> extension I have given the handler, as someone updates the
greeting
>>>>>>> periodically through Unity Greeting Admin). Then, the
distribution list
>>>>>>> that owns the handler gets a voicemail.
>>>>>>>
>>>>>>> I've gone through all the settings and the handler looks
just the
>>>>>>> same as the other handlers that happily play the greeting.
Only the
>>>>>>> "Standard" greeting is enabled. There is a greeting (I can
play it through
>>>>>>> my computer), and it is selected as active.
>>>>>>>
>>>>>>> Any clues as to what I should be looking for?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Sean
>>>>>>>
>>>>>>> --
>>>>>>> Sean Walberg <sean at ertw.com> http://ertw.com/
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cisco-voip mailing list
>>>>>>> cisco-voip at puck.nether.net
>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sean Walberg <sean at ertw.com> http://ertw.com/
>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Sean Walberg <sean at ertw.com> http://ertw.com/
>>
>
>
>
> --
> Sean Walberg <sean at ertw.com> http://ertw.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
_______________________________________________
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
_______________________________________________
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/20090206/5c734b4e/attachment.html>
More information about the cisco-voip
mailing list