[cisco-voip] More Unregistered Route/Hunt Lists

Keith Klevenski keith.klevenski at rig.net
Wed Mar 21 12:23:23 EST 2007


Seems to happen once every few weeks.  No real pattern that I can see.
I'm trying to think if this was after SR4d was installed.  It seems to
be really close anyway.  Nothing else is unregistering that I see.  A
few phones, but most of our phones are on rigs in the middle of the
ocean over satellite links so seeing phones unregister regularly is
definitely not unusual...

 

Keith Klevenski
IP Telephony Engineer

RigNet Inc.
1880 S. Dairy Ashford

Suite 300
Houston, TX 77077         

Office:   +1 281.674.0702
Mobile:  +1 713.677.3925

http://www.rig.net <http://www.rig.net/> 

 

"Extending the power of your knowledge"

________________________________

From: Scott Coner (US) [mailto:scott.coner at us.didata.com] 
Sent: Wednesday, March 21, 2007 12:20 PM
To: Keith Klevenski
Subject: RE: [cisco-voip] More Unregistered Route/Hunt Lists

 

How often is this happening?  Anything else randomly unregistering?

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Keith Klevenski
Sent: Wednesday, March 21, 2007 1:14 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] More Unregistered Route/Hunt Lists

 

Ok, once again I get a complaint of not being able to call long
distance, but local calling is fine.  I look at the route lists and
seven of the nine route lists we have are unregistered along with the
Unity hunt list for vm ports.  I reset them all and they register and
everything is fine again.  Running 4.1.3sr4b.  The CCM group the
hunt/route lists are in contain both CallManagers which has been the
only reason I read about that would cause a hunt/route list to
unregister (having only one CallManager in the CCM group assigned to the
hunt/route list and it goes down).  There was no loss of connectivity to
or between the CallManagers that I can tell.  

 

I see them unregister in the traces and event log.  For example:

 

Event Type:      Error

Event Source:   Cisco CallManager

Event Category:            None

Event ID:          3

Date:                3/21/2007

Time:                11:38:34 AM

User:                N/A

Computer:         HOUCM02

Description:

Error: DeviceUnregistered - Device unregistered.

  Device name.: US-LongDistance-RL

  Device IP address.: <deleted>

  Device type. [Optional]: 90

  Device description [Optional].: US-LongDistance-RL

  Reason Code [Optional].: 8

  App ID: Cisco CallManager

  Cluster ID: US-HOU-CL01

  Node ID: <deleted>

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..

 

Doesn't reason code 8 mean the device initiated the unregistration?  If
so why would a route list do this?  Any clue why 7 route lists and 1
hunt list unregistered, but 2 route lists did not?  I have yet to find
any good reason why a route/hunt list would become unregistered and stay
that way until manually reset (other than the ccm group only containing
one ccm and it goes down).  

 

Any insight would be WONDERFUL.  

 

Thanks!

 

Keith Klevenski
IP Telephony Engineer

RigNet Inc.
1880 S. Dairy Ashford

Suite 300
Houston, TX 77077         

Office:   +1 281.674.0702
Mobile:  +1 713.677.3925

http://www.rig.net <http://www.rig.net/> 

 

"Extending the power of your knowledge"

 

________________________________

Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070321/5db97342/attachment.html 


More information about the cisco-voip mailing list