cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
445
Views
5
Helpful
2
Replies

Delay between activating/deactivating CFwdAll and actual forwarding

I have a "call forwarding all" issue with my CUCM v9.1 (BE6000).

When i actived the "call forwarding all" with the CUCM Administration page or the CUCM user page, this call forwading is displayed on the phone.

But, if i call this phone, the call is not forward, and if i wait a delay (2-5min), and i recall the phone, the call is forwarded to the destination call forward all, and all other call also.

When i disable this call forward, it's the same problem, i must wait the same delay (2-5min) for the call forward is disable.

 

 

In this Cisco support document, http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/43581-database-unreachable.html#t6

i seen in the know issues section, CSCdw94888 (registered customers only) —Delay between activating/deactivating CFwdAll and actual forwarding.

But i can't seen the detail of "CSCdw94888" issue.

 

 

I have seen this post: https://supportforums.cisco.com/discussion/9191526/call-forward-all

And i have disable the dns option for dhcp's scope of the phone but no success, the problem persists.

 

 

Anyone has got this issue or/and know the resolve issue?

 

Thanks

2 Replies 2

Manish Gogna
Cisco Employee
Cisco Employee

Hi Gilles,

CSCdw94888 applies to very old cucm versions. You can check the following on all servers

show status  ---- to check cpu / disk / memory usage

utils diagnose test    ---- for any connectivity , dns , tomcat issues

utils core active list   --- to check for any core dumps

Also, check the status of database replication through RTMT and make sure it is 2 for all servers.

If there is nothing in the above mentioned steps then try a reboot of cucm cluster. If that cannot be done, you need to collect cucm traces for a test call while enabling and disabling cfwdall and it needs to be checked for any delays in signaling.

HTH

Manish

 

 

Hi,

 

I have resolve the issue, it was an NTP problem.

There was a delay of 3min to Subscriber with the Publisher.

Exemple:

  • The publisher have his clock at 12:00, and the Subscriber 11:57, when we activated the call forward at 12:00 (time’s Publisher), we must wait for the Subscriber’s clock is 12:00 for the call forward is activated.

 

The customer has change his AD/DNS server. And when he have change his AD/DNS server, he does not configured properly the NTP’s service.

And the Publisher was unsynchronized for the NTP, when I use the utils diagnose test.

 

For test, and actually I use a Cisco’s router for the NTP source of the Publisher, and it works well!

I wait if the customer can configure properly the NTP’s service of his AD server.