I am using IP Communicator 220.127.116.11 with a VXI Voxstar USB wireless headset on a laptop with Windows 7 Enterprise. I can hear and talk with the headset, but the on/off button on the headset doesn't act as a switch hook. VXI has said that they don't have a software that will make the on/off button act as a switch hook. Is there a setting within IP Communicator that will make the button work? If that's not possible, does anyone use another brand USB Wireless headset with IP Communicator where their on/off button on the headset itself acts as a switchhook, so I can leave my desk and still answer calls? Or, is there a software that anyone knows of that will make my switchhook work with IP Communicator?
About Choosing Headsets and Handsets for Cisco IP Communicator
Even though internal testing of third-party headsets and handsets for IP Communicator has been performed, Cisco does not certify or support products from headset and handset vendors. Because of the inherent environmental and hardware inconsistencies in the locations in which IP Communicator is deployed, there is no one best solution that is optimal for all environments. Cisco recommends that customers test the headsets and handsets that work best in their environment before deploying a large number of units in their network. The primary reason that support of a headset or handset would be inappropriate for an installation is the potential for an audible hum, either a hum heard by the remote party, or by both the remote party and the IP Communicator user. Causes for the hum range from electrical lights near the PC to the PC power source itself. In some cases, a hum experienced by a user using an audio device that is plugged directly into the PC USB port may be reduced or eliminated by using a powered USB hub. In some instances, the mechanics or electronics of various headsets can cause remote parties to hear their own voices echo back when they speak to IP Communicator users. The IP Communicator user will not be aware of the echo.
Finally, some analog headsets do not match the electrical characteristics for which some soundcards are designed. The microphones on such headsets are frequently too sensitive, even when the input levels in IP Communicator are reduced to their lowest values; the voices of users on such headsets will sound distorted to remote parties. It is important to ask IP Communicator users whether a particular headset sounds good to them. In addition, remote parties should be queried as to the reception from IP Communicator when using a particular headset. Testing performed in Cisco labs has shown that the Plantronics DSP 300 and Plantronics DSP 400 have performed well with IP Communicator, but it remains the customer's responsibility to test the headsets in their environment.
Hello, We have been facing issues with backup of drfcomponent.XML & Processnode.XML files to our backup servers during scheduled Backup in our CUCM 11.0 servers.We have been using Titan FTP server for Backup. I see error on backup statusERRO...
To participate in this event, please use the button to ask your questions
At the beginning of 2020, no one would have imagined the changes in work and learning habits that we would face in the foll...
We have a manager that's left and we want to let callers know to call the new manager at a different number, but we don't want the caller to be able to leave a message. Can a voicemail box be setup to work this way?If so, how? Thanks Kelvin
Hi We have CM 11.5 and jabber 12.6 some of our users are receiving incorrect user name or password login, we can confirm the credentials are correct, not all of them are facing the issue some of the users are able to login while others get the ...