Make and take Avaya calls on the Teams dial pad. Each Teams user registers to their own Avaya SIP extension, so numbers and call features keep working, and nothing changes on your Avaya system.
Free 30-day proof of concept for service providers.
It connects your Avaya phone system to Microsoft Teams so people can handle their Avaya calls without leaving Teams. TeamMate does this with PBX Connector: each Teams user registers to their own Avaya SIP extension, and TeamMate automates the Direct Routing link and supplies the session border controllers. It works with Avaya Aura and IP Office.
Teams Calls becomes a softphone on Avaya, using the user’s Avaya number or extension, on desktop, browser and mobile.
Hold, transfer and voicemail still run on Avaya. Custom soft keys put the Avaya functions you choose one tap away.
New Avaya voicemail notifications arrive in Teams, so messages are not missed away from the desk phone.
On a Avaya call, Teams shows On a Call automatically. Presence Pause stops calls ringing through to Teams during meetings.
Transfer a Avaya call to anyone in Teams, with the transfer reported back to Avaya. How Pro Transfer works
Show caller details from your CRM or other systems as a card in Teams before the call is answered.
Each Teams user becomes an Avaya SIP extension, so people can use Teams, a desk phone or both, and you move at your own pace.
The ACS Call App add-on connects Avaya to Teams without Microsoft Phone System licenses.
When a user is unavailable in Teams, Presence Pause can set them to Do Not Disturb on Avaya.
Connect your Microsoft 365 tenant with minimal permissions.
Create a SIP extension for each Teams user on Avaya and enter the details. TeamMate builds the Direct Routing link.
Avaya calls ring in Teams on desktop, browser and mobile, alongside your desk phones.
Most Avaya and Teams integrations use one of three approaches. They differ in where the call is answered and how many Avaya features come along.
A Teams app opens a separate Avaya softphone. Calls move out of Teams, and you support a second client on every desktop.
Avaya also rings a separate Teams number. Calls are answered in Teams, but Avaya features are lost and each user needs an extra number or trunk.
Each Teams user registers to Avaya like any SIP phone. Calls are answered in Teams with Avaya features kept and no extra number per user.
TeamMate also connects Mitel, 3CX, BroadWorks, Metaswitch, NetSapiens, Cisco to Microsoft Teams, along with 80+ PBX types and variants tested with PBX Connector.
Yes. TeamMate PBX Connector registers each Teams user to their own Avaya SIP extension, so Avaya calls ring on the Teams dial pad on desktop, browser and mobile.
Avaya Aura and IP Office. TeamMate connects over SIP, the same way a SIP phone does. Running another Avaya system? Tell us which one and we will confirm before you start.
No. Your numbers, call routing and carriers stay as they are. Each Teams user needs a SIP extension on Avaya, and Teams becomes another endpoint for that user.
Yes. When a user is unavailable in Teams, for example in a meeting, Presence Pause can set them to Do Not Disturb on Avaya so calls follow their busy handling. This uses the standard SIP event package (RFC 6665), which Avaya supports.
With PBX Connector, yes, as with any Direct Routing setup. If you would rather not buy Teams Phone licenses, the ACS Call App add-on lets users make and take calls in Teams without them.
An SBC is needed for any SIP connection to Microsoft Teams, and it is included. TeamMate runs SBCs in 9 Microsoft Azure regions, so there is nothing to install.
It is priced per user, per month. Service providers can start with a free 30-day proof of concept on their own system.
See it in a live demo, or start a proof of concept on your own Avaya system.
Free 30-day proof of concept for service providers.