Cisco Ip Communicator 8.6.6 Download
Abigayle Laurenitis
Run as Administrator did finally work. But there is a key gotcha. Simply closing communicator does not really stop it from running. Process communicatork9.exe is still running. So opened Task Manager and forced that proc to end. THEN RUn as Administrator allowed me to change the network settings.
I have installed Cisco IP Communicator 8.6.1.0 on my Laptop DELL Latitude E6320. Everything is working except the microphone. When I went to the Audio Tuning Wizard, I couldn't perform the microphone test. There was no respone on color bar whenever I make a noise. Then there is a pop-up message said: Could not monitor microphone. Please check the following: (1) A call is in progress (2) Another application is using the microphone (3) Microphone is muted.
I just purchased Plantronics Voyager Pro UC but until now I cannot use it. I am using Windows 7 and it seems Cisco IP Communicator could not detect voyager. I went to the Audio Tuning Wizard but there is only Default Windows Audio Device on the selection for Headset, Speakerphone, and Handset. But I found BUA-200 on Ringer selection. I have paired the USB indicated by blue light.
When I opened the Sounds configuration from the control panel, under Playback tab there is Speakers BUA-200 as default device. And under Recording tab, there is Microphone BUA-200 also as default device. But still, when I went to Audio Tuning Wizard, there is only Default Windows Audio Device on the Headset selection.
Is there any other solution determined other than modifying registry? I use CIPC version 8.6.3.0 and have this issue. IP communicator doesn't recognize my microphone. I'm using laptop Dell Latitude E6410.
I had the same issue with Win7 and IP comminucator 7.5. I was able to fix the issue. I went into the registries (by running regedit) and found and deleted the Cisco IP Communicator folder. Then, I ran the Audio Tuning again with the Plantronics headset plugged in to the computer. When completed, I was able to place and receive calls without any issues.
This has happened to me, after installing as an Administrator you have to open it up the first time as an administrator and put your settings in. Then you should be able to shut it down through task manager then just open up regular and should work.
I have an end user who's having an issue where his main phone app, cisco IP communicator keeps somehow over riding the audio for teams. So if cisco is up and running you can not hear any audio on a teams call. As soon as I kill cisco everything is normal. I have jacked around with audio settings in both apps and windows 10 till I'm blue in the face. I've reinstalled both cisco and teams w/o success. I can not seem to find any other issue like this anywhere online. Has anyone else experienced this issue with other soft phone apps and teams?
Forgot to provide that info. He is on a Dell 7480 and we've updated realtek audio drivers and bios from dell's website. didn't make any difference. What machine are you on and what are you using for your other softphone oposite Teams?
Any updates on this? We just recently implemented Myistra as our softphone application. When using our Jabra Evolve headset during a Teams call, when we receive an incoming call from Myistra, the softphone automatically picks up the incoming call without touching anything and we end up losing audio on the Teams call.
Cisco Unified Personal Communicator (CUPC) is the client application that integrates into the Cisco Unified Presence Server (CUPS). This client runs on a Windows or Macintosh desktop environment and provides for several integrated communications features such as desk phone control, Instant Messaging (IM), Presence, softphone, communication escalation, and so on. This chapter covers the client installation, configuration, basic and advanced features, and client-side troubleshooting.
It is strongly recommended having LDAP synchronization configured in any CUCM installation. This brief section covers the steps required to configure a user in CUCM without LDAP integration. This is because when LDAP synchronization is enabled, the ability to add/delete users in the CUCM user interface is removed. All users are added or removed via the LDAP management interface. Figure 5-2 illustrates the concepts for the following steps:
The user might not show up for several minutes on the CUP server. If it is taking too long, go to Cisco Unified Serviceability > Tools > Control Center-Feature Services, select the CUP server (publisher if in a cluster), and then start or restart Cisco UP Sync Agent.
When the user has been added to CUCM, it will be synchronized over to the CUP server. There is no need to add the user separately to the CUP server. LDAP synchronization is strongly recommended so most of these steps would not be necessary, and the rest can be done when doing the phone device provisioning in CUCM. For more information on CUCM synchronization with LDAP, refer to the "LDAP System Configuration" section in the Cisco Unified Communications Manager Administration Guide at
A common deployment model is for a single user to have both a desk phone and have CUPC act as a softphone during communications that take place away from the desk. CUPC offers a softphone capability that enables it to act as a phone device on a computer without the requirement of a desk phone, making the desk phone an optional device in a deployment. The use of a desk phone is optional and not required when deploying and configuring CUPC. This section covers the basic steps necessary in setting up an IP Phone to be used with CUPC. Figure 5-4 shows the addition of a physical desk phone.
The SUBSCRIBE calling search space determines how CUCM routes Presence requests that come from the phone. This setting enables you to apply a calling search space separate from the call-processing search space for Presence (SUBSCRIBE) requests for the phone.
The phone now registers to CUCM with the proper settings and user association. Adding the phone allows users to have the option to control their phone through a computer telephony interface (CTI) with the CUPC client. This allows for the added software features offered by the CUPC client and still has a desk phone for a more reliable voice experience.
The next step is to set up a CUPC device in CUCM associated to the appropriate user and potentially connected to a desk phone. The first step in planning for the CUPC device configuration is to understand the naming convention required in CUCM. These requirements follow:
When saved, a new screen comes up that shows what devices are associated to the DN. This field should at least have the CUCP device associated with it. If it is a shared DN with a phone device, two devices should be listed: the CUPC and the phone device. This is shown in Figure 5-9.
Now that the CUPC device is set up in CUCM and the users are configured, the client can be installed, and there will be Presence, desk phone connectivity (CTI), and softphone functionality. These are the basic services that CUPC has available, and in the next section, the advanced features of CUPC will be configured. It is recommended to have these features configured before installing the client.
Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.
This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.
For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.
For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.
Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.
Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.
On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.
We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.
Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.