![]() This information is passed to, and used by, the Plantronics Hub application for the purpose of user group identification. Plantronics Manager/Plantronics Manager Pro does not directly connect to your LDAP or Active Directory servers. This process allows Windows users without administrative permissions to upgrade Plantronics Hub.ĭoes Plantronics Manager/Plantronics Manager Pro need to connect to my LDAP server? PlantronicsUpdate.exe is also a process that runs at start up. PLTHub.exe is the Plantronics Hub process that runs at start up providing all of the functionality expected from Plantronics Hub. What services/processes run at start up on the Windows operating system? Using the clients available from within your tenant will ensure the correct tenant connectivity. How does Plantronics Hub know which tenant to connect to?Įnsure you install the version of Plantronics Hub that is provided from within your tenant. All connection information is housed in this area. How can I easily tell if Plantronics Hub has successfully connected to a tenant?įrom the Plantronics Hub client select Help > Support and expand the troubleshooting details section. Close Plantronics Hub, locate and delete the file called nfig found in C:\Users\\AppData\Local\Plantronics or %appdata%. If a connection to a tenant had happened previously then this file would exist and Plantronics Hub could get confused. Once the Plantronics Hub software connects to a tenant, a user specific configuration file is created. If the TenantID has a value of System, then Plantronics Hub is attempting to connect to our Consumer tenant, not your enterprise tenant. All connection information can be found in this location. From the Plantronics Hub client, select Help > Support and expand the Troubleshooting Details section. Ensure Plantronics Hub is connecting to the correct tenant.Got to Plantronics Hub > Help > Support > Network Assessment and run a test. Ensure that Plantronics Hub has been downloaded and deployed. ![]() This download contains the SDK files in the "Spokes3GSDK. Spokes3GSDK - the Mac SDK static library.Resources (including PlantronicsDevices.xml).Support files, including PlantronicsDevices.xmlĬontains the files required at runtime to support the Plantronics Native Library API.Plugins for Avaya, Skype and iTunes (media management).CustomActions startup actions for SDK runtime (PLTHub.exe)Īlso contains the file to support Plantronics Native Library (PlantronicsDevices.xml).Once the SDK is installed, this MSI can be found here: %programfiles(x86)%PlantronicsSpokes3G NET Interop and REST Service APIsįor this option these 3 must be deployed in conjunction: Once the SDK is installed, this MSI can be found here: %programfiles(x86)%PlantronicsSpokes3G SDKĬontains the additional files required at runtime to support the Plantronics COM Service, COM Service. On your development machine go to: and download the SDK via the download link. ![]() Or for COM/.NET/REST APIs these 3 must be deployed in conjunction: Ĭontains the files required at runtime to support the Plantronics Native Library API (Spokes.dll).Ĭan be deployed alone for Native Library API. When Hub is present your application can talk to the Plantronics device. ![]() Normally with this model you would advise the end-user or their IT department to install Hub. COM interface types for the COM Service APIsĬan be deployed alone for access to all 4 Plantronics Windows APIs.CustomActions startup actions for Hub (PLTHub.exe).Plugins for the ~13 Plantronics-supported softphones.PLTSpokes.exe + its support DLLs and files.What deployment models are available for Plantronics SDK v3.x? Deployment Packageįull Plantronics software to support device config, multi-softphone support, Plantronics software and firmware upgrades.Īlso contains all the files and configuration to support Plantronics Native Library, COM Service, Com Service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |