<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>This document lists the reasons as well.<br><br>http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/3_2/english/administration/guide/7900trb4.html#wp1020334<br><br>Unfortunately, it's from CCM 3.x, but unfortunately the more recent documents don't include the detail this one does.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Jason Burns" <burns.jason@gmail.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "Scott Kee" <SKee@cmsstl.com>, cisco-voip@puck.nether.net<br>Sent: Thursday, February 5, 2009 8:54:36 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] phone rebooting itself<br><br><link href="/zimbra/css/msgview.css?v=081117021119" rel="stylesheet">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.<br><br><div class="gmail_quote">On Wed, Feb 4, 2009 at 9:12 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Double check the requirements for phones across a WAN and make sure you within spec. <br>
<br>That's the first thing.<br><br>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.<br>
<br>The 7911s are even more susceptible to this (or more resilient, depending on your thinking) - they failover rather quickly.<br><br>---<br><font color="#888888">Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt</font><div><div></div><div class="Wj3C7c"><br><br>
<br>----- Original Message -----<br>From: "Scott Kee" <<a href="mailto:SKee@cmsstl.com" target="_blank">SKee@cmsstl.com</a>><br>To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Sent: Tuesday, February 3, 2009 7:15:23 PM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] phone rebooting itself<br><br>I have a remote office that has 25 phones: 1 7975, 2 7965, and rest are 7945. <br>All the phones are connected to the WS-C3560-48PS-S switch.<br>
I am using H323 on the Cisco 2811.<br><br>Problem: time to time phones reboots itself or disconnects from the call manager and gives below messages.<br>-UCB failure error <br>-certainly drops the call when they are on the phone<br>
-it goes in to SRST mode(failover mode)-- it comes right backup.<br><br>I worked with Cisco TAC but they are saying the phone lost the connection to the Call Manager.<br>Why it loses the connection to the CM?<br>Maybe the switch is too small to support 25 phones?<br>
<br>Does anyone know what maybe the cause of the issue?<br><br>Thanks,<br><br><br><br><br>-----Original Message-----<br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Pat Hayes<br>
Sent: Tuesday, February 03, 2009 5:44 PM<br>To: Sean Walberg<br>Cc: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] Unity 5 - Call handlers for announcements<br>
<br>To add to what Bill said, for the port status monitor, make sure you<br>use the one from tools depot, not the web based one. The web based one<br>only shows you 'real time' state, where as the tools depot one has a<br>
buffer and will show you the whole call, much easier to follow.<br><br>Something else you might consider is using the Audio Text Manager, it<br>helps to visualize your config and makes things a bit easier to<br>navigate when you've got a complicated tree:<br>
<br><a href="http://ciscounitytools.com/APP_AudioTextManager403.htm" target="_blank">http://ciscounitytools.com/APP_AudioTextManager403.htm</a><br><br>On Tue, Feb 3, 2009 at 10:19 AM, Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> wrote:<br>
> Thanks for the suggestion. I recreated the call handler and it works now.<br>> Would have liked to try your suggestion earlier though, I'm curious why the<br>> handler didn't work.<br>><br>> Sean<br>
><br>> On Tue, Feb 3, 2009 at 9:12 AM, Bill Talley <<a href="mailto:btalley@gmail.com" target="_blank">btalley@gmail.com</a>> wrote:<br>>><br>>> One last suggestion if you continue to have the problem after rebuilding<br>
>> the call handler. I apologize if this has already been mentioned, but you<br>>> can use the Call Viewer combined with the real time display of Port Status<br>>> Monitor in Unity Tools to see where Unity is directing the call during that<br>
>> portion of the call to verify Unity is performing the expected handling of<br>>> the call.<br>>> As you're probably aware, Call Viewer will just show you digits<br>>> accompanying the call from Call Manager. Port Status monitor, when set to<br>
>> real time display mode, will show you the call flow messages while the call<br>>> is being handled by Unity identifying which mailbox/handler answers the call<br>>> and which greeting is played.<br>>><br>
>> HTH<br>>><br>>> On Tue, Feb 3, 2009 at 8:44 AM, Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> wrote:<br>>>><br>>>> Thanks Bill,<br>>>><br>
>>> I checked and it's set to "Recording". There's a recording there, too.<br>>>><br>>>> I think I'll just delete this handler and recreated it.<br>>>><br>>>> Sean<br>
>>><br>>>> On Sat, Jan 31, 2009 at 9:47 AM, Bill Talley <<a href="mailto:btalley@gmail.com" target="_blank">btalley@gmail.com</a>> wrote:<br>>>>><br>>>>> Check the standard greeting page for that call hander and verify the<br>
>>>> radio button to play the greeting is ticked. It sounds like the radio<br>>>>> button to play the system greeting is ticked.<br>>>>><br>>>>><br>>>>> On 1/30/09, Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> wrote:<br>
>>>>><br>>>>>> Thanks Scott,<br>>>>>><br>>>>>> There's no call routing rule associated with this. At the subscriber<br>>>>>> level, I have a blank greeting and then "After greeting, send caller to call<br>
>>>>> handler -> Attempt transfer for MBCKND Special Announcement".<br>>>>>><br>>>>>> That call handler provides a menu, pressing 1 takes them to another<br>>>>>> call handler that plays a greeting and waits for a digit. Digits from there<br>
>>>>> take the caller to other handlers, such as 1 for the primetime lineup, which<br>>>>>> prompts for a digit from 1-5 corresponding with the day. Each day is a<br>>>>>> separate call handler. Only the call handler associated with #4, Thursday,<br>
>>>>> goes to VM, all the others play the greeting properly.<br>>>>>><br>>>>>> Sean<br>>>>>><br>>>>>> On Fri, Jan 30, 2009 at 2:36 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>><br>
>>>>> wrote:<br>>>>>>><br>>>>>>> Check your call routing rule and see if the others are set that way<br>>>>>>> and that one is missing a rule.<br>>>>>>><br>
>>>>>> scott<br>>>>>>><br>>>>>>><br>>>>>>> On Fri, Jan 30, 2009 at 11:24 AM, Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> wrote:<br>
>>>>>><br>>>>>>>><br>>>>>>>> The voice mail coverage path of one of my office's front desk goes to<br>>>>>>>> a Unity call handler, playing a message like "press 1 for the programming<br>
>>>>>>> lineup, 2 for the news desk, etc". Callers eventually get to a menu along<br>>>>>>>> the lines of "press 1 for Monday, 2 for tuesday", and so forth.<br>>>>>>>><br>
>>>>>>> Each of these handlers is a greeting, which plays the message, then<br>>>>>>>> kicks the caller back to the menu.<br>>>>>>>><br>>>>>>>> This works great, except for the Thursday handler. When the caller<br>
>>>>>>> selects the Thursday option, they get a message saying "the user at<br>>>>>>>> extension 103 is not available, please leave a message" (103 is the<br>>>>>>>> extension I have given the handler, as someone updates the greeting<br>
>>>>>>> periodically through Unity Greeting Admin). Then, the distribution list<br>>>>>>>> that owns the handler gets a voicemail.<br>>>>>>>><br>>>>>>>> I've gone through all the settings and the handler looks just the<br>
>>>>>>> same as the other handlers that happily play the greeting. Only the<br>>>>>>>> "Standard" greeting is enabled. There is a greeting (I can play it through<br>>>>>>>> my computer), and it is selected as active.<br>
>>>>>>><br>>>>>>>> Any clues as to what I should be looking for?<br>>>>>>>><br>>>>>>>> Thanks,<br>>>>>>>><br>>>>>>>> Sean<br>
>>>>>>><br>>>>>>>> --<br>>>>>>>> Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a><br>
>>>>>>><br>>>>>>>><br>>>>>>>> _______________________________________________<br>>>>>>>> cisco-voip mailing list<br>>>>>>>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
>>>>>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>>>>>>><br>>>>>>><br>
>>>>><br>>>>>><br>>>>>><br>>>>>> --<br>>>>>> Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a><br>
>>>>><br>>>>>> _______________________________________________<br>>>>>> cisco-voip mailing list<br>>>>>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
>>>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>>>>><br>>>>><br>>>><br>>>><br>
>>><br>>>> --<br>>>> Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a><br>>><br>><br>
><br>><br>> --<br>> Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a><br>><br>> _______________________________________________<br>
> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>
</div></body></html>