[cisco-voip] Why Do Route Lists Unregister?

[Keith Klevenski]

We have both servers in our CM group so that is not the issue.  

 

Since originally sending this email I realized voice mail was down.
After looking into this I discovered the hunt list that contains the
voice mail ports was unregistered as well.  Resetting it brought
everything back up just fine.  Unity is off of sw1 along with the
publisher.  If Unity lost connectivity to the sub then the vm ports
should register to the pub which was on the same switch.  When
connectivity to the sub was restored the vm ports should have registered
back to the sub, but instead I have an unregistered hunt list that
required a reset to get back online.

 

Anyone else have things like this happen?  This has happened a couple of
times recently.  Running CCM 4.1.3 SR4b.  I would love to know why a
hunt/route list unregisters and STAYS unregistered until a reset is
done.  

 

TIA

 

Keith

 

________________________________

From: Justin Steinberg [mailto:jsteinberg at gmail.com] 
Sent: Friday, February 16, 2007 4:21 PM
To: Keith Klevenski
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Why Do Route Lists Unregister?

 

Route lists are assigned to a CM group.

Are your RL assigned to a CM group that has both pub and sub?  If not,
perhaps that can cause some trouble when your cluster lost connectivity.

Justin

On 2/16/07, Keith Klevenski <keith.klevenski at rig.net> wrote:

Hi all,

 

I asked this question recently, but I never got a solid answer.  

 

A few minutes ago we had an issue between our two core 6500's and sw1
was not accessible, but sw2 was (an rspan gone bad).  Each switch has a
6608 with several PRIs off each one in each switch.  The publisher is
off sw1 and the subscriber is off sw2.  After the rspan was removed from
sw1 (console access via Envoy) traffic starting flowing normally again.
Several minutes later I was informed that no outbound calls could be
made.  I looked around and noticed that all route lists were
unregistered and of course no calls were going out.  I reset all the
route lists and they registered and calls started going out normally
again.  

 

So the question again is why would route lists unregister and stay
unregistered until they were all reset?  All of our route lists were
unregistered, even route lists that only contain one ICT or one gateway.
It seems related to CCM losing connectivity to the gateways in the route
lists, but why they would stay unregistered until a reset eludes me...

 

Any input appreciated as always!

Keith

 

 


_______________________________________________
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/20070216/8fcb074a/attachment-0001.html