Click To Call - Destination cannot be reached error

Unanswered Question
Jun 11th, 2010
User Badges:


Trying to troubleshoot what appears to be an Application Dial Rule problem when using the Click To Call widget.  Currently, can only dial internal extensions without issue.  Getting "Destination cannot be reached error" with all outbound calls.  I can see the phone attempt to process the call, but only appears to quickly go off/on hook.  Would like to know which trace files from Call Mgr I can use to accurately pinpoint this issue.  So far, I've tried using the CTI, CCM, Webdialer, and CCMCIP traces with Triple Combo to parse.  Not having much luck at this point.  As a second note, I was able to get this partially working on a non-domain PC with Proxy disabled in Internet Explorer.  Not totally sure if it is necessary to allow internal CCM IP and port via firewall.

UCCM version =

Click To Call version =

Sample Application Dial Rule Settings

- Number of Digits = 10

- Total Digits to be Removed = 0

- Prefix with Pattern = 9

For test calls, I'm only sending 7 digits for local call and want the App Dial Rule to prefix the 9 for outside call.  Any help, greatly appreciated.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 1 (1 ratings)
htluo Fri, 06/11/2010 - 14:27
User Badges:
  • Red, 2250 points or more

The first thing you want to check is CUCM > System > Service Parameters > Cisco WebDialer Web Services >"Apply Application Dial Rules on SOAP Dial Request".

This parameters should be set to "True" (default is "false").

After that, restart WebDialer service.

If that didn't help, we'll need web dialer logs to troubleshoot.


webberr Tue, 07/20/2010 - 12:59
User Badges:

Sorry - meant to rate it a "5" - but I slipped and hit

a "1" by mistake - sorry.

ckltd7401 Sun, 07/25/2010 - 18:54
User Badges:


Just wanted to update this by saying that I have yet to resolve this issue, but plan to upgrade UCCM from ver 7 to ver 8 near end of this coming Aug.  Therefore, I'm closing this thread.  After conferring with TAC, it was their recommendation that I reboot the Subscriber server that is having the WebDialer issue.

Thanks for the responses.



This Discussion