For desk phone listening volume adjustments, use the volume button on the earpiece of the headset and/or the volume button on the desk phone.When un-muted you will hear three low tones. These tones will repeat every 60 seconds while mute is active. When mute is activated, the base will be solid red and you will hear three high tones (you will still be able to hear the caller).Mute your Headset Microphone During a Call Flash between calls – During a call, long press the volume button up or down for 1.5 secondsĢ Call button – Place, answer, end a call – Short press the call control buttonģ Headset LED – Flashed white when in use.Mute/un-mute a call – To mute/un-mute the headset, press the volume/mute button in.Increase the volume – Press the volume button up.Decrease the volume – Press the volume button down.To force snd_usb_audio to be loaded before usbhid, I added to my /etc/modprobe. If snd_usb_audio is loaded first, things work ok. This appears to be something about the order the snd_usb_audio and usbhid modules are loaded. If the headset is plugged in afterwards it does work. If the headset is plugged in while the PC is booting, the controls do not work. It doesn't work if the headset is plugged in at boot Now when you log in using Gnome, the lineakd daemon will start automatically. I don't know what the KDE equivalent would be. With Gnome, use System->Preferences->Sessions. The daemon must be started from an X session). I created it in /etc/init.d, but it could be anywhere. Start the lineakd daemon in the background and the volume control should work.Ĭreate a script lineakd. Then create a config file ~/.lineak/nf KeyboardType = PLA-DSP300ĪudioLowerVolume = /usr/bin/amixer -c 1 set PCM 2-ĪudioLowerVolume+shift = /usr/bin/amixer -c 1 set Mic 2-ĪudioRaiseVolume = /usr/bin/amixer set -c 1 PCM 2+ĪudioRaiseVolume+shift = /usr/bin/amixer set -c 1 Mic 2+ I used lineakd to handle the keycodes from the headset.Ĭreate a definition file for the headset in ~/.lineak/f I used xev (from xbase-clients package), to find what keycodes are being generated by the headset. The mute and volume buttons were sending keycodes to the system. The trick In getting the volume control to work was realising that part of the headset was behaving like a USB keyboard. The mute button worked without any action on my part, but the volume did not. Now when I boot, the headset is always the second device. Create new file /etc/modprobe.d/usb-headset with # Set usb headset as second device The assignment of device numbers can be controlled using a module parameter. If I booted with the headset plugged in, the headset device drivers would load first,making the headset the first device. Plugging in the headset now would make it the second device (/dev/dsp1). If I booted the PC without the headset, my main sound card would naturally be the first device(/dev/dsp). I want the headset to be the second device This may have started working at the same time I downloaded new firmware to the device, I just don't know. I still don't know what changed, but at some point the headset could be controlled from alsamixer. When I first tried to use the headset, It worked fine, but I couldn't control the volume or mute the mic no matter what I tried. The model I have is the DSP 300, although I expect that these instructions will work for other models also. I also had problems if the headset was plugged in when I booted the PC. While the headset itself worked straight off, the volume control did not. The headset has a control with volume and mute buttons. I got a Plantronics USB headset to use for Skype. How To - Get the volume control working on the Plantronics USB headset This article may not be appropriate for this wiki, and may be deleted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |