How To Install Plantronics Powerline From A Powerpoint Powerline (Powerline) From A Microsoft Powerbook (Powerplone) From An Ipa (Powerbook) From Powerline) (Powerplant) From Your Computer Or Power

Transcription

1 PEM Plantronics Enterprise Manager Configuration and Customization of Plantronics Software

2 Contents Overview 3 PEM Specifications 4 Target Audience 4 System Requirements 4 Language Support 4 Installer Tool Options 4 Start Menu Entries 4 Startup Requirement 4 Customizable Devices 4 Installation and Setup 5 Software Installation 5 Device Customization Overview 5 Device Customization Setup 5 User Preference Customization 6 MSI Customization 6 Deployment Scenarios 9 Use Case 1 9 Use Case 2 9 Use Case 3 9 Use Case 4 10 Frequently Asked Questions 12 Settings Matrix 15 Terms 19 2

3 Overview The Plantronics Enterprise Manager (PEM) enables IT administrators to: Customize the default settings and features of supported Plantronics headsets, and optionally lock features and settings to prevent user modification. Prevent help desk calls by providing a uniform install base thereby ensuring a consistent experience for your users Select the proper mix of software support modules to meet the unique needs of your corporation or user base. These modules enable softphones and music players to properly interface with Plantronics devices. Select whether to install Plantronics applications such as Plantronics Control Panel which allows the end user to change permitted settings or the Battery Status Meter which notifies the user when the battery is getting low on their wireless device. Select how software and device firmware updates will be handled. The finished customized install package can then distributed for installation from a server or pushed via standard IT tools to deploy MSI packages and files. IT will need to use their company s standard software deployment tools (i.e. SCCM, Tivoli, GPO, LANDesk) to push the installation and copy any required XML files. NOTE: The Spokes for Windows MSI is available for download outside of PEM from for deployments where customization is not required. 3

4 PEM Specifications Target Audience This tool was built to assist system administrators/application packagers with the enterprise deployment of Plantronics devices and software. System Requirements Windows XP wsp3, Vista (32 or 64 bit), or Windows 7 (32 or 64 bit) 30 MB free system memory 10 MB free disk space.net framework (supplied by Microsoft), version 3.5 sp1 21 MB available disk space 11 MB memory (Windows 7) Language Support PEM runs in English only. Supported languages for the Spokes for Windows are: Chinese (traditional and simplified), Danish, Dutch, English (US and British), Finnish, French (standard and Canadian), German, Italian, Japanese, Korean, Norwegian, Portuguese (standard and Brazilian), Spanish (Castilian and Latin American), Swedish and Turkish. Plantronics applications run in the currently set language of your operating system, as determined by the operating system s language code page. Installer Tool Options Verbose or silent user installer mode, log files, overwrite/update/uninstall of Spokes for Windows are all controlled with the standard MSI installer tool options. For more information, please refer to the documentation for Microsoft s MSIEXEC tool. It is highly recommended you use the log file option when deploying customized MSI packages. This will be your best source of information, should you encounter difficulties. Start Menu Entries The Spokes for Windows Installer does not install shortcuts on the desktop instead links are added to a Plantronics entry in the start menu. Plantronics Enterprise Manager provides IT with the capability to select which applications should be installed and which applications are available in the start menu. Startup Requirement Spokes for Windows (PlantronicsURE.exe process) runs at system startup and this behavior cannot be changed by PEM. Customizable Devices Savi 430 (D100 adapter), Savi 440 (D100 adapter), Savi Office, Savi W7xx and Voyager Pro UC. 4

5 Installation and Setup Software Installation Download PEM by accessing Use the Spokes for Windows download button to navigate to PEM download. Once installed, launch PEM from the Start menu. Device Customization Overview IT can choose to customize device settings on behalf of the user. The settings that are available for customization can be found on the corresponding tab for the device within PEM. Each tab provides an opportunity to create an XML file that will be used for device configuration. IT selects the tab that corresponds to the devices being deployed, modifies required settings and saves the XML. This file must be manually copied or pushed via deployment tools to a specific location on the users system. If supported by the specific device, IT can also choose to password protect device settings to prevent modification by the user. Once the XML file is deployed to the users system, this password is applied to the device as well. This prevents the user from attempting to overwrite IT settings by simply plugging the device into a different system. IMPORTANT NOTE: Once a password has been set on the device, there is no way to change or remove this password centrally. The password can only be changed or removed at the client workstation via the Plantronics Control Panel. As an alternative to setting a password, IT can modify the installation (using Install Customization tab) to prevent the install of the Plantronics Control Panel. This will effectively remove the user s ability to change these settings. This option will provide IT with a similar level of control without the requirement to manage a password. Device Customization Setup 1 Select the tab that corresponds to the device you want to customize 2 Modify settings you would like to change and select the lock icon for any settings you would like to password protect. NOTE: The tool currently does not provide a way to change this password on a mass scale. If you set a password and later need to change it, you will need to do so on the client. 5

6 3 If you have locked any settings, enter a password and select Save. If you have not locked any settings, the password entry is not required. 4 Save the resulting XML file to a known location in preparation for deployment. Note that the filename must not be changed from what is generated by PEM. 5 Using an IT deployment tool, copy the XML file(s) to: Windows XP: C:\Documents and Settings\All Users\Application Data\Plantronics\ PlantronicsURE Vista and Win7: C:\ProgramData\Plantronics\PlantronicsURE User Preference Customization The User Preferences tab provides IT with the ability to modify the default settings that are found on the User Preference tab in the Plantronics Control Panel. For Spokes deployments where the Plantronics Control Panel is not provided to the user, this gives IT the ability to manage certain features on behalf of the user. User Preference Customization Process 1 Select the User Preferences tab 2 Modify settings you would like to change. NOTE: The settings found on this tab are specific to certain device models. Check the Settings Matrix and the end of this document for descriptions and device applicability. 3 Save the resulting XML file to a known location in preparation for deployment. 4 Using an IT deployment tool, copy the UserPreference.XML file to: Windows XP: C:\Documents and Settings\All Users\Application Data\Plantronics\ PlantronicsURE Vista and Win7: C:\ProgramData\Plantronics\PlantronicsURE MSI Customization Component Overview The install customization tab allows IT to select which modules they want supported in their environment. The modules can be broken into six functional areas: softphone, media player, Plantronics Battery Status, Plantronics Control Panel, usage statistics and Update Manager. 6

7 1 Softphone Modules Installation of a softphone module will provide integration between the Plantronics device and the corresponding softphone. By installing a corresponding softphone module, the user will benefit from features such as the ability to remotely answer/end the call using the button on the Plantronics device. The module will also enable mute synchronization between the device and the softphone (user mutes call using the Plantronics device and mute status is reflected in the softphone client and vice versa). Each softphone module is a DLL that has median size of 30 KB. If your company policy doesn t require that you reduce the installed modules, then it is recommended that you install all modules for future compatibility. The process that manages these modules is the PlantronicsURE.exe and consumes approximately 11 MB of private set memory on Windows 7. 2 Media Player Modules Installation of a media player module will provide integration between the Plantronics device and the corresponding media player. By installing a corresponding media player module, the playback of music by the media player will be paused upon receiving a call and will resume play when the call is terminated. This behavior can be customized by the user via the Plantronics Control Panel. Each media player module is a DLL that has a median size of 20 KB. 3 Plantronics Battery Status Installation of the Battery Status application will provide the user with a visual indication of low battery notifications for wireless devices in the notification area (system tray). The disk footprint is approximately 350 KB with the process consuming approximately 8 MB of private set memory on Windows 7. 7

8 4 Plantronics Control Panel Installation of the Plantronics Control Panel will provide the user with access to user preferences (media player options, dial-tone enablement etc) and device specific settings (bandwidth settings, auto-answer options etc). The control panel is not a required component. IT can prevent users from modifying device settings by either locking those settings via device configuration XML files or by not installing the Plantronics Control Panel. The disk footprint for the Plantronics Control Panel is approximately 900 KB. When the application is running, the corresponding process consumes approximately 10 MB of private set memory on Windows 7. 5 Usage Statistics Enabling this feature will suppress the collection of usage data. The data collected by default is anonymous and is used solely for the purpose of improving the software features in future releases. No personal or company information is collected. Checking this option will cause the feature to be disabled in the Plantronics Control Panel and prevent modification by the end user. 6 Update Manager The installation of the Update Manager will install a separate module providing software and firmware update notifications to the user. This does not auto-update but rather checks daily and notifies the user when updates become available. The user must have administrative rights to install any software updates but administrative rights are not required to apply firmware updates. To prevent these notices and maintain IT control of all updates, select the disable remote software/firmware updates checkbox on the Install Customization tab. The disk footprint for the Update Manager is approximately 1.2 MB. MSI Customization Setup 1 Select the Install Customization tab 2 Uncheck any modules you do not want installed in your environment. Refer to the preceding Component Overview section for information on the various modules. 3 Select Save As to save the MSI file to a known location in preparation for deployment. 8

9 Deployment Scenarios Use Case 1 IT is deploying Savi W7xx devices, wants to manage all software updates centrally, and needs Bluetooth disabled with no possibility of users re-enabling post install. IT wants users to manage other settings such as default line and media player settings. 1 Select the Savi W7xx tab and set the Bluetooth Enabled setting to Off. 2 Select the lock icon next to the setting, set a password and save the XML file in preparation for IT deployment. 3 Select Install Customization tab to select the Disable remote software/firmware updates checkbox and save the customized MSI file. 4 Deploy the MSI and copy the Savi W7xx XML file into the predefined directory on the users system. Result: Following the IT push of the MSI and the XML file, clients will have the Spokes for Windows software installed including the Plantronics Control Panel. All GS should be modifiable in the Plantronics Control Panel excluding the Bluetooth Enabled setting which is greyed out and not selectable. The Plantronics Update Manager is not installed therefore all software updates will have to be managed/pushed by IT. Use Case 2 IT is deploying Savi Office devices, wants support for all Cisco softphones, and needs to enable/ manage Audio (Noise@Work) features. Users have administrative rights on the desktops and IT wants users to manage their own updates and device settings/user preferences but does not want users to be able to change the Audio (Noise@Work) features. 1 Use the Savi Office tab to customize the Audio (Noise@Work) features as required for your company. 2 Select the lock icon next each setting, set a password and save the XML file in preparation for the IT deployment. 3 Select the Install Customization tab to deselect all the softphone modules excluding the Cisco modules and save the customized MSI file. 4 Deploy the MSI and copy the Savi Office XML file into the predefined directory on the users system. Result: Following the IT push of the MSI and the XML file, the clients will have the Spokes for Windows software installed including the Plantronics Control Panel. Because the other softphone modules were deselected, users will only have call control and mute sync for Cisco softphones. The Update Manager will be installed and users will be notified of both firmware and software updates. When users view the Plantronics Control Panel, they are able to modify all settings excluding the Audio (Noise@Work) features. Use Case 3 IT is deploying Savi W7xx devices, wants users to experience the benefit of answering Avaya one-x Communicator calls with the Plantronics device. IT also wants the music paused/ resumed when a call is answered and terminated and wants users to receive low battery alerts. IT requires the minimal amount of software be installed on the system to achieve these goals, does not want the user to change device settings or user preferences and needs to manage all software updates internally. 9

10 1 Select the Install Customization tab to deselect all the softphone modules excluding the Avaya one-x Communicator. Leave all media player modules and the Plantronics Battery Status module selected. 2 Deselect the Plantronics Control Panel module. 3 Select the Disable remote software/firmware updates checkbox. 4 Deploy the MSI and copy the Savi Office XML file into the predefined directory on the users system. Result: Following the IT push of the MSI, the clients will have the Spokes for Windows software installed and the Battery Status application will be the only entry found in the Plantronics start menu. User will not be notified of updates and will only have integration with Avaya one-x Communicator. Music will pause/resume during a call start/end for itunes, Windows Media Player and Winamp. Use Case 4 IT is deploying Savi W7xx devices to three buildings on campus but the buildings have different needs. Building A is using Avaya one-x Communicator and houses the call center. Building B and C are using Cisco Unified Personal Communicator and house the Finance team. For building A, IT needs to ensure Avaya one-x Communicator is supported and needs to enable the autoanswer feature on the the Savi W7xx (it is disabled by default). This will allow the calls coming into the call center to be answered automatically. Also for building A, IT wants to restrict the users to modify settings so they are not going to install the Plantronics Control Panel. These users do not have admin rights so IT will not install the Update Manager. For building B and C, IT needs to ensure Cisco Unified Personal Communicator is supported. IT wants to give these users the ability to manage their own preferences and will install the Plantronics Control Panel for these users. These users do have admin rights so IT will install the Update Manager and allow users to manage their firmware and software updates. IT also wants music to be paused during incoming calls for all buildings and wants all media players supported. Since all buildings are using the Savi W7xx, they can all benefit from the Battery Status notifications and will want this application installed throughout. Company policy states that IT must not install any components that are not being fully utilized which usually requires IT create customized installation packages. Building A 1 Select the Install Customization tab to deselect all the softphone modules excluding the Avaya one-x. Leave all media player modules and the Plantronics Battery Status module selected. 2 Deselect the Plantronics Control Panel module. 3 Select the Disable remote software/firmware updates checkbox. 4 Deploy the MSI and copy the Savi Office XML file into the predefined directory on the users system. Buildings B and C 1 Select the Install Customization tab to deselect all the softphone modules excluding the Cisco UC (CSF) Clients. Leave all media player modules and the Plantronics Battery Status, and Plantronics Control Panel module selected. 2 Deselect the Plantronics Control Panel module. 3 Ensure the Disable remote software/firmware updates checkbox is not selected. 10

11 4 Deploy the MSI and copy the Savi Office XML file into the predefined directory on the users system. Results for Building A Following the IT push of the MSI and the XML file, clients in building A will have the Spokes for Windows software installed and the Battery Status application will be the only entry found in the Plantronics start menu. Users will not be notified of updates and will only have integration with Avaya one-x Communicator. Music will pause/resume during a call start/end for itunes, Windows Media Player and Winamp. Auto-Answer will be enabled for the Savi W7xx devices. Results for Building B and C Following the IT push of the MSI, clients in building B will have the Spokes for Windows software installed which will include the Battery Status application, the Plantronics Control Panel, and the Update Manager. Users will be notified of updates and will only have integration with Cisco clients that are based on the CSF framework which includes the Cisco Unified Personal Communicator. Music will pause/resume during a call start/end for itunes, Windows Media Player and Winamp. 11

12 Frequently Asked Questions Does the device need to be plugged in when I deploy the MSI file to the users desktop? No, you can deploy the software and the XML file at any time during the device deployment process. How do force the device to pick up the settings in the device configuration XML file I ve deployed? The settings will be picked up during the next reboot. To force the settings to be picked up without a reboot, toggle the PlantronicsURE.exe process (open task manager and stop PlantronicsURE.exe process. Select Start, New Task and enter PlantronicsURE.exe and select Ok to restart). **Note the User Preference XML file has no such requirement. It is picked up immediately. Can the XML configuration files be edited manually or do I have to use the PEM tool? The XML files are just standard XML files. Plantronics Enterprise Manager is an IT tool created to make the modification of our XML files simple. The XML files can be modified manually using any text editor. How can a security password be remove/deleted from a device? To set the device back to the default password (removing your customized password) will require a call to our Technical Assistance Center. They will provide you with a skeleton password that can be used to set your device back to its native password. This is a required step to help ensure that a user doesn t simply download this document and overwrite your settings. With the assumption that you have previously set a password using PEM, pushed out/copied the XML to the proper location and settings have been applied to device, do the following: 1 Open the Plantronics Control Panel with the device attached to the system. 2 Select the Devices tab and ensure that the proper device is listed in the Devices dropdown. 3 Select Device Settings button, Security tab and enter the skeleton password into the Feature Set Lock area in both the Create New Password and Confirm new Password text boxes. 4 Select Set to change the password in the device. 5 You can now create new XML files using PEM without setting a password and the device will accept it. If I choose not to install the Plantronics Control Panel, how can I confirm that the settings from my XML file have been applied? The XML file has an Applied element that gets changed to True once the file has been applied and the device has assumed the settings. If I push out an XML file and realize later that I made a mistake, how can I modify? You can simply create a new XML file and overwrite the existing. Can a user overwrite my password protected settings by moving the device to a different system? No, the password is stored on the device and therefore moves with it. Moving the device to a different system reset the settings. What if a user needs to overwrite a setting that I ve previously password protected? 1 IT will need to provide the password to the user. 12

13 2 The user will have to open the Plantronics Control Panel and select the Security tab. Within the Feature Set Lock group box, enter the password in the text box provided and select OK. Once the password is accepted, the user can now modify the necessary settings. How do I update an existing installation of Spokes for Windows with a newer version? Pushing out an updated MSI that installs a new version of Spokes will uninstall the existing installation and install the new version. User settings will be retained. I ve already pushed Spokes for Windows out to my clients but I neglected to include a component. How do I update an existing installation with a new MSI for the same version of Spokes for Windows? Because Spokes is already installed, initiating a second install of the same version will invoke the Change, Repair, Remove dialog. To avoid this, IT can either create a transform file or uninstall the erroneous deployment before attempting to install the new MSI. We currently have.net 4.0 installed on our client desktops. Is this sufficient or does Spokes for Windows really require the.net 3.5 framework? Right now, Spokes for Windows requires that the.net framework version 3.5 sp1 be installed on the client desktop. The MSI will check for the existence of this version and if it s not found the install will abort. You will need to install the.net 3.5 sp1 framework prior to installing Spokes for Windows. What if I do not need to make any customizations to the install but I want the MSI file? Do I still need to use PEM? PEM contains an unmodified version of the Spokes for Windows MSI installation file. If PEM is already installed, you can simply select the Save As button from the Install Customization tab and save this unmodified installation file. The MSI is also available outside of the PEM environment at The PEM supplied MSI and the downloadable MSI are identical and both will behave the same with respect to reading and applying customization XML files. When I click on the download for Spokes for Windows from your website, it downloads a setup.exe installation file. What is the difference between this file and the MSI? The setup.exe file launches the MSI but first does an inspection to ensure the proper version of the.net framework exists on the system. If it does not, the setup.exe will install the framework prior to launching the installation of Spokes for Windows. I ve pushed out the device configuration XML file to the client but when I open the Plantronics Control Panel on the desktop, the settings have not been changed. What should I check? The device configuration XML file gets picked up and applied to the device by the PlantronicsURE.exe process. Toggling that process (open task manager and stop PlantronicsURE.exe process. Select Start, New Task and enter PlantronicsURE.exe and select Ok to restart) or rebooting the system will force Spokes for Windows to look for the XML file. More than one device being plugged into the system at the same time can also prevent the XML file from being found and applied. Be sure to unplug any additional Plantronics device(s) that don t correspond to the XML. NOTE the User Preference XML file does not require the toggling of the Plantronics process. The User Preference XML file is picked up automatically. 13

14 I want to customize both the installation and the settings on the device and put the final package on our intranet for users to download and install. How can I combine the MSI and XML files? You will need to build your own package that combines the components. PEM s to incorporate the XML files into the MSI is being considered for future versions. I am deploying Savi W7xx devices and would like to manage the bandwidth setting for these devices. Due to potential density issues, I want to ensure that the users cannot modify this setting. I am not using any softphone and don t anticipate using the USB interface. Is there still a way to utilize PEM to manage the settings? Yes, the bandwidth and other settings can be managed using PEM and can be locked down to prevent end user tampering but it does require that the device be plugged into the PC, at least temporarily. Once the settings have been applied to the device via the XML configuration file, the device can be unplugged from the PC. The settings and the password will be retained on the device even after it is no longer connected to the PC. Here are the steps: 1 Install the Spokes software on the PCs. 2 Use PEM to modify the bandwidth setting (or any setting you wish to customize) for the Savi W7xx. 3 Select the lock icon next to the bandwidth setting (or any settings you wish to lock). 4 Select Save As to create the XML file. 5 Push or copy the XML file to the proper directory on the PC. 6 Reboot the PC (alternatively, PlantronicsURE.exe process can be toggled). 7 Confirm the setting has been applied. This can be done by opening the Plantronics Control Panel confirming the setting is greyed out or by looking that the SaviW7xxconfig.XML file and confirming that the Applied element (<Applied>True</Applied>) is set to True. 8 The device now has the proper bandwidth setting which cannot be modified by the end user. 9 If desired, the Spokes for Windows software can now be uninstalled from the PC. I am deploying Savi W7xx devices, I need the Bluetooth functionality disabled and I am not able to install Spokes for Windows in my environment. Can PEM provide assistance with this task? No, using PEM to disable the Bluetooth feature does require the installation of the Spokes software. We do have separate tool, the Plantronics W7xx Bluetooth Configuration Tool, that is available from that provides IT with the ability to disable the Bluetooth functionality without installing Spokes for Windows. This tool is packaged as an MSI and when installed on the desktop, disables Bluetooth on the device. Users cannot turn this feature back on manually. See our website for more information on this utility. 14

15 Settings Matrix Action to Media Player Setting Description Default Action to Media Player controls behavior of itunes, Winamp, and Windows Media Player when a softphone call comes in; default is Pause/ Play with Mute/Unmute, Mute/Do Nothing, Pause/Do Nothing and Do Nothing/Do Nothing as additional options. When a call begins = Pause When a call ends = Play Anti-Startle Anti-startle provides advanced hearing protection against sudden loud noise. When Anti-Startle is set to ON, the system identifies and eliminates sudden loud sounds and instantly reduces them to a level similar to background noise. When Anti-Startle is set to OFF, receive audio is passed through unfiltered. However, the headset caps sound levels at 118 dba to protect your hearing. Off Audio Bandwidth The system will support both narrowband and wideband audio from the desk phone and PC. Wideband audio delivers heightened speech clarity and life-like fidelity. However, wideband audio consumes more battery power which reduces talk time and has more stringent access criteria which reduces the number of systems that can be deployed in a small area. Your desk phone must support wideband audio to experience the benefit of selecting wideband for that device. All PCs support wideband audio. Desk Phone = Narrowband PC = Narrowband Audio Limiting Audio Limiting provides advanced hearing protection for daily noise exposure. When Audio Limiting is turned ON, the system monitors noise to ensure action levels do not exceed 80 dba or 85 dba (whichever is selected) specified by current and imminent EU legislation. When Audio Limiting is set to OFF, receive audio is passed thru unfiltered. However, the headset caps sound levels at 118 dba to protect your hearing. Off Auto Answer Auto Connect to Mobile Phone Bluetooth Enabled Auto answer saves the user a button press to establish the radio link between headset and base unit. When Auto Answer is set to OFF you must press the headset call control button or base PC/desk phone talk button to answer an incoming call. When Auto Answer is set to ON an incoming call will be answered when the headset is removed from the charge cradle. Auto Connect to Mobile Phone feature allows you to have your Savi W7xx base automatically establish a Bluetooth link to the mobile phone whenever the headset is undocked from the base and the mobile phone is within range. Bluetooth Enabled feature allows you to enable/disable the Bluetooth radio in your Savi W7xx base. Off Enabled Enabled 15

16 Setting Description Default Default Line Default line sets user preference for outbound desk phone, mobile or PC when headset call control button is pressed. When Default Line is set to Desk Phone and you press the headset call control button to initiate a call, the desk phone will be taken off-hook. You then need to dial the phone number from the desk phone. When Default Line is set to PC and you press the headset call control button an audio link will be brought up between your PC and headset. You then can place an outbound call via your softphone application or listen to streaming audio via a media player. Desk phone Default Softphone Some Plantronics devices are capable of dialing digits or selecting a contact and initiate an outgoing call. This setting allows a particular softphone to be selected for such calls. The first one in the list Enable auto presence update on Microsoft OC/Lync and Skype This setting gives you the option to have Microsoft Lync and Skype presence status updated when you are on a phone call using a softphone supported by Plantronics, a desk phone connected to your Plantronics device or a mobile phone paired with your Plantronics device. Enabled Escalate IM to Voice for: This setting allows you to automatically start a voice call with the party with whom you have an active Microsoft OC/Lync, or Skype IM session by simply putting on the headset. This setting only applies to Voyager Pro UC v2. Do Nothing Feature Set Lock Password Enter the password previously created through the Security tab in order to lock/unlock the settings. This field will be disabled if there is no password has been created for the device from the Security tab. G616 G616 Acoustic Limiting provides additional hearing protection against acoustic shock When G616 Acoustic Limiting is set to ON, the system limits audio level to your ear to provide additional acoustic shock protection. Sound levels are limited to be less than the Acoustic Shock Protective Device Limit as recommended in the G616:2006 guideline issued by the Australian Communications Industry Forum (ACIF). When G616 Acoustic Limiting is set to OFF, audio level to your ear is passed through unfiltered. However, the headset caps sound levels at 118 dba to protect your hearing. Off Hours on Phone Per Day Specifying this setting helps optimize the use of Automatic Acoustic Level (AAL) related settings such as TWA and G616. Choose a value that best represents the typical use of your Plantronics device. Hours on phone per day can be set to 2, 4, 6, 8. 8 Initiate Mobile voice commands This setting allows you to enable or disable a feature of your W7xx system where you can put your mobile phone in voice command mode by simply pressing the mobile phone button on your W7xx base. Disabled 16

17 Maintain Headset to PC Link Over-the-Air Subscription Setting Description Default This setting forces the radio link to the PC to stay active even when the call has ended. This can eliminate the need to re-establish the radio link when switching between PC audio applications. Maintain Headset to PC Link can be set to Yes or No. **Wireless products Only Over-the-Air Subscription allows a headset to be subscribed to the base without physically docking the headset. Required when conferencing various models of Plantronics Savi Office headsets. When Over-the-Air Subscription is set to ON you can subscribe a headset to your base without physically docking the headset into the charge cradle. To subscribe a primary headset to the base using Over-the-Air Subscription, first make sure there is no active audio link between the base and headset. Next, double press the subscription button on the base. The subscription button will flash red and green. Next, put your primary headset into subscription mode by pushing the headset volume up button until the headset indicator light becomes solid green. When the subscription button on the base turns solid green you have successfully subscribed the primary headset to the base. To conference in up to three additional guest headsets to the base using Over-the-Air Subscription an active audio link must be present between the base and primary headset. Once an audio link is active press the subscription button on the base for less than one second. The subscription button will flash green and yellow. Next, put the guest headset into subscription mode by pushing the headset volume up button until the headset indicator light becomes solid green. The subscription light will turn solid yellow and the primary headset user will hear a tone indicating a guest wishes to join the call. If the primary headset user presses their call control button within five seconds the guest is joined to the call. When Over-the-Air Subscription is set to OFF you can only subscribe a headset to the base by physically docking the headset into the charge cradle. To subscribe a primary headset to the base when Over-the-Air Subscription is OFF dock your primary headset into the charge cradle. Next, double press the subscription button on the base. The subscription button will flash red and green. When the subscription button on the base turns solid green you have successfully subscribed the primary headset to the base. To conference in up to three additional guest headsets to the base when Over-the-Air Subscription is OFF first make sure an active audio link is present between the base and primary headset. Once an audio link is active, dock the guest headset (which will need to be the same model as the primary headset) into the charge cradle and press the subscription button on the base. The subscription button will flash green and yellow. Next, the subscription light will turn solid yellow and the primary headset user will hear a tone indicating a guest wishes to join the call. If the primary headset user presses their call control button within five seconds the guest is joined to the call. No On 17

18 Setting Description Default Range Range can be minimized to help with desk phone/pc buzzing, improve user density, or restrict range of users. When Range is set to HIGH a user will have up to 300 feet of range. When Range is set to MEDIUM a user will have up to 150 feet of range. When Range is set to LOW a user will have up to 50 feet of range. High Ring Both Headset and PC This setting gives you the option to have the PC ringtone played on both the headset as well as the PC speaker. When this setting is set to disabled, the PC ringtone will only be heard on either the headset or the PC speaker based on how the PC audio has been set up. When this setting is enabled, the PC ringtone will be heard on both the PC speaker as well as the headset. Disabled Stop auto connect to mobile when headset is docked If Auto Connect to Mobile Phone feature is enabled and your Savi W7xx base automatically establishes a Bluetooth link to the mobile phone whenever the headset is undocked from the base, this setting can force the Bluetooth connection to the mobile phone to be dropped whenever the headset is docked on the base. Disabled When headset is put on, set presence to: When headset is removed, set presence to: This setting allows you to have your presence status in Microsoft OC/ Lync and Skype changed automatically when you wear the headset. This setting can be set to Available, Busy, Do not disturb, Be right back, Offline and Do Nothing. This setting allows you to have your presence status in Microsoft OC/ Lync and Skype changed automatically when you remove the headset. This setting can be set to Available, Busy, Do not disturb, Be right back, Offline or Do Nothing. Do Nothing Do Nothing 18

19 Terms Client End user desktop Deployment The method to transport and install software. This is most commonly done by: Burning the deployment package to a disk Placing the software in a commonly accessible network drive Using IT tools to push the packages to the desktops End User The person that will use a Plantronics device to manage their communications IT or IT Staff The group that will use PEM to customize the software and device settings MSI The Microsoft Installer Package PEM PEM Plantronics Device A communication device, such as a headset, used for speech communications PlantronicsUREConfiguration.msi This is PEM installation package. Runtime Engine The runtime engine is a required component that runs at startup as a process on the system. The PlantronicsURE.exe can be viewed in the Process tab within the Windows Task Manager. This process manages the interactions between the Plantronics device and the softphone(s). It also handles the application of any device XML files that are created. Softphone Communication software that runs on a PC. Spokes for Windows Spokes for Windows is the end user control and application software that is installed on the PC to manage the communications between desk phones, softphones, and cell phones. Update A process to revise software on PC or firmware on the device 19

20 NEED MORE HELP? plantronics.com/support Plantronics, Inc. 345 Encinal Santa Cruz, CA United States 2012 Plantronics, Inc. All rights reserved. (11.12)