Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CUCM 7.1 Call Forward All - Problems

Hi we have recently upgraded to CUCM 7.1 from 4.1, we are having intermittent problems with call forward all,

eg. we have fwd all on 2491 to 8060, sometimes 2491 will ring, but most tests will indeed forward to 2491??

Have also been to site and witnessed missed calls on the device, even though the FWD ALL is on.

Any ideas  would be appreciated.

The devices and lines, all have the same CSS and Partitions.

Cheers

Rich

  • IP Telephony
3 REPLIES
Hall of Fame Super Red

Re: CUCM 7.1 Call Forward All - Problems

Hey Rich,

Have you checked the CFWDALL CSS. In 4.x the CFWDALL CSS could

be left at but in newer versions of CUCM this CSS must be set.

Cheers!

Rob

"May your heart always be joyful And may your song always be sung May you stay forever young " - Dylan
New Member

Re: CUCM 7.1 Call Forward All - Problems

Hi Rob and thanks for the reply,

Have assigned CSS to FWDALL, as I said sometimes the FWDALL works, sometimes not so is a nightmare to try

and solve.

Failed to say, it is only happening on 7962 phones SCCP42.9-0-3S.

Its almost like CUCM is only sometimes checking it DB before signalling the phone??

Cheers

Rich

Cisco Employee

Re: CUCM 7.1 Call Forward All - Problems

Run a report from the Cisco Unified Reporting Tool for Database Status.  Make sure that everything is ok in there.  It almost sounds like some servers know about the forwarding and some might not, depending on which servers receives the call setup.  Another thought might be that change notification is broken on certain nodes, check "show tech notify" from the command line of each server, the CCM service should show the same number for the H and T columns.

503
Views
0
Helpful
3
Replies
This widget could not be displayed.