[cisco-voip] PRI fails but ccm status is still registered

[Wes Sisk]

There are several CM service parameters to affect hunting logic.  "Stop 
hunting on...."  CSCef90503 adds the ability to configure all reason 
codes to stop hunting.

In this case, since the d-ch is down, I would expect CM to hunt to the 
next member in the route list / route group by default.

/Wes

Gareth S. Cafirma wrote:
> Thanks Wes, now the problem is since its still registered, any call 
> that comes in to this pri will busy out and calls will not go to the 
> next PRI. Any solution or workaround for this one?
>
> On Feb 28, 2008, at 1:56 PM, Wes Sisk <wsisk at cisco.com> wrote:
>
>> For 6608 i believe it is going to stay registered, just the d-channel 
>> will be down/OOS.  Use perfmon or RTMT counters to check that condition.
>>
>> For IOS MGCP gateways performing d-channel backhaul the gateway will 
>> show registered even if the d-ch is down. However the specific 
>> endpoint will only show registered if the d-ch is up.
>>
>> /Wes
>>
>> Gareth S. Cafirma wrote:
>>> Its on a 6608 blade and the other end is rightfax server. Server 
>>> shuts  down but pri still shows as registered in ccm. Anyone 
>>> encountered this  before?  Ccm 4.1(3)es122.1
>>>
>>> Thank you.
>>> Gareth
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>