I've a client using some 3rd party VPN solution and wants to use IP Communicator. The users have tested the IPC and observed audio quality issues.
I am checking the Read Me for "CiscoIPCommunicatorAdminToolSetup.exe" and states "It also enables HTTP access for AutoUpdate and for IP Address auto-detection in the network audio settings for unsupported VPN clients (getIP.asp)."
I am not sure how to run this EXE CUCM Appliance model. Can someone please throw some insight on this Tool, how can it be helpful in our environment?
From READ ME - CiscoIPCommunicatorAdminToolSetup.exe
- To be launched on the TFTP server or Cisco Unified Communications Manager Publisher. This tool will install the DirectoryWizard tool for configuring the Quick Search and Dialing Rules features. It also enables HTTP access for AutoUpdate and for IP Address auto-detection in the network audio settings for unsupported VPN clients (getIP.asp).
Thanks in advance,
In case someone else gets stuck on this.
This does not apply for linux based CUCM (5.0 and later), please check:
Run the Cisco IP Communicator Administration Tool on the Cisco Unified Communications Manager publisher (the TFTP server where phone loads will be installed).
You must run the tool to install the Directory Wizard (used to configure the Quick Search and Dialing Rules features).
Obtain the tool from the product software download web site: http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278468661.
It is located inside the zipped folder with your build.
(For Windows-based Cisco Unified Communications Managers only) If any users in your network rely on unsupported VPN clients, you must enable HTTP access (the tool sets up an IP reflector web page to resolve audio IP auto-detection problems). Enabling HTTP access also improves performance for remote users.
Now, if they are having audio quality issues, (meaning both parties can hear each other but the quality of the audio is not as expected), this is must likely caused by insufficient bandwidth, so please perform a test on the corporate LAN, (with voice QoS enabled), and check if the problem persist, if not, this is must likely the issue, otherwise you may try with a supported VPN (there are trial periods for cisco vpn SW), and also try to enable the "Optimize for Low Bandwidth" feature (right-click > Preferences > Audio tab) and enable that checkbox.
Now, if the CIPC is not picking an IP address you may install the tool you are refering to on a windows server
If the Cisco IP Communicator party cannot hear the remote party, it might be for these reasons:
•The Cisco IP Communicator user is relying on a unsupported VPN. To resolve the issue, you must set up a web reflector page or manually specify the IP address in the Network Audio Settings window (right-click > Audio tab > Network button).
•The Cisco IP Communicator user is relying on a unsupported VPN, and Cisco IP Communicator is integrated with a Linux-based Cisco Unified Communications Manager (Releases other than 4.x). To resolve this issue, run the Cisco IP Communicator Administration Tool on a Windows server to resolve the audio IP address auto-detection problem.
•If Cisco IP Communicator is behind a firewall, make sure that the firewall is configured to pass TFTP and RTP traffic by using the appropriate port range.
Here is the troubleshooting guide for CIPC 8.5 which covers several audio related issues.