Connect integrations
Configure Connect with desktop softphones and browser-based dialers. Prepare the audio path, apply the correct routing for each translation mode, and validate the complete call before going live.
Understand the two integration types
Connect works as an audio layer between your physical headset and the calling service. The important difference is where that service stores its microphone and speaker choices: an installed application keeps them in its own preferences, while a browser service may combine operating-system, browser, site-permission, and softphone settings.
Desktop applications
Open the dialer's own audio or device settings and choose the Connect virtual devices required by your translation mode. Changing only the Windows or macOS default may not replace a saved in-app selection.
Browser-based services
Allow microphone access for the site, verify the browser or softphone device menu, and reload the call tab after a device change. Browser permission and dialer routing are separate checks.
Prepare Connect before opening the dialer
Start with a known-good Connect audio path. This prevents an integration problem from being confused with a missing driver, muted physical microphone, or headset connection issue. Use a short test call to verify both directions and make sure the selected translation mode matches the routing.
- Verify the physical path.
- Connect the physical headset before opening Connect or the calling service.
- Inside Connect, choose the real headset under Available Microphones and Available Speakers.
- Verify the virtual path.
- Confirm Connect Mic and Connect Speaker are present in the operating system.
- If either device is missing, repair the virtual audio drivers before configuring the dialer.
- Complete the pre-call check.
- Run How I Sound? with one complete sentence and resolve silence, clipping, or an incorrect physical device.
- Select the source language, target language, voice, and translation type required for the call.
Route audio for the selected translation mode
The correct device pair depends on which side of the conversation must pass through translation. Use the table below as the common starting point for every listed integration. Compare the result in Connect and in the calling application before adjusting another part of the signal path.
| Connect mode | Dialer microphone | Dialer speaker | Result |
|---|---|---|---|
| Bidirectional | Connect Mic | Connect Speaker | Both sides pass through the Connect translation path. |
| Unidirectional — your voice | Connect Mic | Normal headset or default speaker | Your translated voice is sent; incoming audio remains direct. |
| Unidirectional reverse — incoming voice | Normal headset or default microphone | Connect Speaker | Incoming speech is translated; your voice remains direct. |
Some dialers expose separate devices for calls, notifications, ringtones, or communications. Change the call microphone and call speaker first. A ringtone output normally stays on the physical headset unless your dialer requires a different arrangement.
Configure an installed calling application
Desktop dialers usually remember device choices independently from the operating system. Configure the application after Connect and its virtual devices are available, then restart it if its menu still shows an old device list. Keep the installer version and device status available if the same step fails again.
- Close the dialer completely if it was open during Connect installation or driver recovery.
- Open Connect, confirm the physical headset, and leave Connect ready with CONNECT-ON off.
- Open the dialer and locate Audio, Devices, Voice & Video, or Advanced Audio.
- Select the microphone and speaker shown in the routing table for your Connect mode.
- Disable overlapping voice enhancement, automatic microphone processing, or noise reduction only when it degrades the Connect signal. Change one option at a time.
- Place an internal test call, press CONNECT-ON, and confirm that the session timer and live transcription respond.
Product menus can move between versions. If the labels differ, look for the controls that choose the active call input and output rather than relying on the exact wording in an older screenshot.
Configure a browser-based calling service
Web dialers can inherit the browser or operating-system default, but many also provide their own device menu. Verify each permission layer in order so that a blocked website is not mistaken for incorrect Connect routing. Use a short test call to verify both directions and make sure the selected translation mode matches the routing.
- Open the dialer's website in a supported browser and allow microphone access when prompted.
- Select the padlock or site-controls icon in the address bar and confirm microphone access is allowed for the current site.
- Open the dialer's audio settings and choose the Connect devices required by the selected mode.
- Reload the tab after changing devices. If the service opens calls in another tab or window, verify that surface as well.
- Close other tabs that are actively using the microphone, then place a short test call.
Integration directory
The Connect integration library contains sixteen platform guides with application-specific routes, audio controls, validation checks, and FAQs. Choose the exact calling platform below, or use one of the two universal routes when your application is not listed. Keep this shared routing guide available when comparing one-way and bidirectional configurations, and test every saved change before using the integration on a live conversation.
Desktop applications
8x8 Work
Desktop dialer audio routing
Avaya Agent
Application and advanced audio settings
Avaya one-X Agent
Agent audio device configuration
Avaya one-X Communicator
Communicator audio routing
Bria 4
Softphone microphone and speaker settings
Cisco Jabber
Audio and advanced device options
Discord
Voice & Video device routing
Genesys Activities
Activity audio configuration
MaX UC
Desktop calling device selection
Microsoft Teams
Meeting and call device settings
RingCentral
Desktop and browser call routing
SIP desktop applications
Generic SIP softphone routing
Talkdesk
Desktop dialer audio settings
Zoom
Meeting microphone and speaker settings
Browser-based services
Amazon Connect (AWS Connect)
Browser permission and contact-control audio
Genesys Cloud CX
Browser-based audio and direction routing
Universal routes
Any calling application
Generic softphone input and output setup
Browser-based calls
Chrome, Edge, Firefox, and site permissions
Validate the integration before a live call
A successful device selection is not enough on its own. Complete a short end-to-end test that proves the physical input, Connect processing, virtual route, and remote playback all work together. Keep the original setting noted so an unsuccessful adjustment can be reversed quickly. This makes the outcome easier to evaluate, explain, and reproduce across future calls.
- Run How I Sound? to confirm the physical microphone reaches Connect clearly.
- Join a test call with a colleague or second device and verify the dialer's active microphone and speaker.
- Press CONNECT-ON and confirm the session timer starts.
- Speak one complete sentence and verify that live transcription appears in Connect.
- Ask the remote participant whether they hear the translated output, your natural voice, silence, or both.
- Test the reverse direction when using Bidirectional or reverse Unidirectional mode.
Handle integration-specific differences
The same Connect devices are used across integrations, but each dialer can cache, rename, or separate its audio controls differently. Use the symptom to decide which layer to revisit. Use the guidance here to make one deliberate change at a time and preserve a clear baseline.
| What you see | Likely cause | Action |
|---|---|---|
| Connect devices are missing only in one application | The dialer cached its device list | Close it completely and reopen it after Connect is ready. |
| A browser site cannot use the microphone | Browser or site permission is blocked | Allow access for the exact site, then reload the call tab. |
| The remote participant hears your natural voice | The dialer is using the physical microphone | Select Connect Mic when outgoing translation is required. |
| You cannot hear incoming audio | The output does not match the translation mode | Use Connect Speaker only when incoming audio must pass through Connect. |
| Audio becomes clipped or metallic | Two applications are processing the same signal | Disable overlapping effects one at a time and retest. |
Frequently asked questions
These answers cover the decisions that apply across the complete integration directory. Verify that recommendation in a short test before changing another setting or workflow. If the result remains unclear, record the exact behavior and the conditions under which it occurs. This keeps troubleshooting focused and gives support enough context to reproduce the problem.
Do I need to change the operating-system default devices?
Usually no. Select Connect Mic and Connect Speaker inside the calling application or web dialer according to the translation mode. System defaults can remain on the physical headset unless a specific browser service inherits them and provides no device selector.
Why does a dialer still show the previous microphone after I changed it in Windows?
Many dialers save their own device choice and keep the device list loaded while the application is open. Change the microphone in the dialer's settings or close it completely and reopen it after Connect is ready.
Can I use Connect with an application that is not listed here?
It may work if the application lets you choose standard microphone and speaker devices. Start with the generic routing table, run an internal test, and confirm both directions before using it for a live conversation.
Why does the integration stop working after reconnecting a headset?
The physical device order or saved audio handle may have changed. Stop CONNECT-ON, reselect the physical headset in Connect, reopen the dialer or reload the browser tab, and verify its Connect device choices again.
Support
Need help? Get in touch with our Support Team for assistance. Include the calling application, operating system, selected microphone and speaker, translation direction, and the exact step that failed. A short description of the expected result and what happened instead helps the team respond more quickly.