[cisco-voip] CFwdAll problem with CCM 3.3.4(sr4)

Tamer Mohamed Bayomy tamer.bayomy at xceedcc.com
Mon Apr 11 17:44:20 EDT 2005


Check Below

 

Symptom:
IP Phones will not be able to set Call Forward All (CFA) and phones that
are already CFA will be unable to clear the condition, even if the phone
indicates that it is not forwarded.

Further Problem Description:
Many times you will be able to tell when the problem first started by
looking in the Application Event Viewer on all nodes for an Error
message from CallManager. This message should state that an SDL
connection to one or more nodes went OOS (out of
service). 

Ideally the low level networking part of CallManager should alert all
other processes when the SDL link goes down. This will allow them to
reestablish their connections when the CallManager process recovers or
is restarted. In this case they are n
ever notified that the service went down, so they do not attempt to
recover.

 

Conditions:
After a stop or crash of the CallManager service on any node the
connection between the processes that monitor the database for changes
and the CallManager processes on all nodes will fail to re-establish.

This results in the CFA changes being written to the database (and can
be seen in the CCMAdmin web page) but the CallManager process on each
node will not be notified that the change occured.

Workaround:
Restarting the Database Layer Monitor service on all nodes in the
cluster should recover the connection (this is not service impacting).
In extreme cases a restart of CallManager may be necessary as well,
which will be service impacting.

Note that after the connection is restored the forwarding information
internal to CM memory may be corrupted for phones that were "stuck"
forwarded during the outage. To fix this change the CallingSearchSpace
for CFA under the line that is "stuck".
Update the line, then reset the devices. You can then change the CFA CSS
back to its original value and the phone should display the correct CFA
information and calls should be routed appropriately.

 

 

  _____  

From: Gawie Herholdt (GSP) [mailto:herholgs at telkom.co.za] 
Sent: Monday, April 11, 2005 11:36 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CFwdAll problem with CCM 3.3.4(sr4)

 

Hi 

 

We discovered a very strange problem... 

 

When users select the CFWDALL softkey on their phones and don't provide
any input (i.e. lets it timeout), then the system automatically forwards
all calls to a specific user (and it is always to the same user). We
tried everything, reboot, restart services. Remove and re-create the
templates, profiles, users and checked all the obvious settings.

 

Has anyone encountered this problem before or have any ideas? 

 

Thanks in advance

Gawie 

 

 

 

 

==================================================================
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at 
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050411/4cf902c2/attachment-0001.html


More information about the cisco-voip mailing list