Plan requirement
| Subscription | UC-Essential or higher |
One small program on your computer unlocks headset buttons, screen sharing, Outlook and the fax printer. Without it, none of them work.
What it is for
Collaboration runs in a browser, and a browser is not allowed to reach into your hardware and your other applications. The Integration Service is the piece that bridges that gap.
It is the reason a support answer so often begins with "is the integration service installed". It usually is not.
What stops working without it
- Headset buttons. Answering and hanging up from the headset itself, and the busy light that tells the room you are on a call.
- Screen sharing, including letting a colleague take control of your screen.
- Outlook. Your presence following your calendar, click-to-call, incoming calls looked up against your Outlook contacts.
- The fax printer, which lets you print a document to a fax number.
- Clicking a phone number anywhere on the computer and having Wildix place the call.
- Cloud Analytics, for the people who use it.
Installing it
- Open your Collaboration settings with the gear icon and choose Extensions in the left menu.
- Choose Install next to the Integration Service.
- Follow the installer for your operating system.
- Reload Collaboration afterwards.
Installing needs local administrator rights on most company computers, so check with whoever manages them before you start.
Outlook is inside it now
It used to be a separate download. It is now part of the Integration Service, and you switch it on in the service's own settings rather than installing anything else.
If the Outlook tab does not appear after installing, install the Integration Service again and reload Collaboration. That sounds like folk wisdom and it is the documented fix.
Older Windows applications
Some Windows software expects a TAPI driver to place calls. That driver installs from the same Extensions list, and afterwards you point the application at it through Phone and Modem in Control Panel. Windows only; there is no macOS equivalent.
Installed but nothing works
The service talks to itself over a local address, and a corporate network that filters DNS can break that without breaking anything else. If it is installed, running, and still does nothing, that is worth mentioning to whoever runs your network.
For a whole team, deploy it centrally. Asking everyone to install it themselves means half of them never do, and you spend the next year answering the same question.
Comments
0 comments
Article is closed for comments.