NEWAI Voice Agents for Microsoft Teams are now generally available. AI Voice Agents for Teams. Try it live →
Metaswitch · Microsoft Teams

Metaswitch and Microsoft Teams integration. Your Metaswitch service, inside Teams.

Put your Metaswitch calling on the Teams dial pad, under your own brand. Each Teams user registers to Metaswitch, and CommPortal opens in a tab inside your Teams app.

Free 30-day proof of concept for service providers.

Microsoft ISV Partner · Microsoft Certified for Co-sell100% Microsoft Azure based, 9 geographic regionsSOC 2 Type 2 certified
80+PBX types tested
9Azure regions
500+service providers
18countries
The basics

What is Metaswitch Microsoft Teams integration?

It connects Metaswitch to Microsoft Teams so your customers can handle their Metaswitch calls without leaving Teams. TeamMate does this with PBX Connector: each Teams user registers to their own Metaswitch line, and TeamMate automates the Direct Routing link and supplies the session border controllers. Metaswitch stays the phone system, and you keep the customer.

In Teams

What Metaswitch users get in Teams.

Calls on the Teams dial pad

Teams Calls becomes a softphone on Metaswitch, using the user’s Metaswitch number or extension, on desktop, browser and mobile.

Metaswitch features kept

Hold, transfer and voicemail still run on Metaswitch. Custom soft keys put the Metaswitch functions you choose one tap away.

Voicemail alerts

New Metaswitch voicemail notifications arrive in Teams, so messages are not missed away from the desk phone.

Your portal in Teams

Open CommPortal or your customer portal from a tab in your branded Teams app.

Pro Transfer

Transfer a Metaswitch call to anyone in Teams, with the transfer reported back to Metaswitch. How Pro Transfer works

Screen pops

Show caller details from your CRM or other systems as a card in Teams before the call is answered.

Built for Metaswitch

More than a dial pad.

CommPortal inside Teams

Show the Metaswitch CommPortal in a tab of your branded Teams app, so users manage call settings without leaving Teams.

SIP auto-provisioning

TeamMate can take a user’s SIP details from your provisioning server instead of having them typed in, and has been tested with Metaswitch.

Your brand

Sell it as your own service, with a white-label portal and Teams app.

How it works

Metaswitch in Teams in three steps.

Set up your portal

Add your branding and connect the customer’s Microsoft 365 tenant with minimal permissions.

Add Metaswitch and users

Enter the Metaswitch SIP details and add users by hand or with SIP auto-provisioning. TeamMate builds the Direct Routing link.

Add CommPortal to your Teams app

Enter the CommPortal address in your Teams app settings and allow Teams in the CommPortal security headers.

Options

Three ways to connect Metaswitch to Teams.

Most Metaswitch and Teams integrations use one of three approaches. They differ in where the call is answered and how many Metaswitch features come along.

Cross launch

A Teams app opens a separate Metaswitch softphone. Calls move out of Teams, and you support a second client on every desktop.

Twinning

Metaswitch also rings a separate Teams number. Calls are answered in Teams, but Metaswitch features are lost and each user needs an extra number or trunk.

Registration (TeamMate)

Each Teams user registers to Metaswitch like any SIP phone. Calls are answered in Teams with Metaswitch features kept and no extra number per user.

More integrations

Other phone systems in Teams.

TeamMate also connects Mitel, 3CX, BroadWorks, NetSapiens, Avaya, Cisco to Microsoft Teams, along with 80+ PBX types and variants tested with PBX Connector.

FAQ

Metaswitch and Teams questions.

Does Microsoft Teams integrate with Metaswitch?

Yes. TeamMate PBX Connector registers each Teams user to their own Metaswitch line, so Metaswitch calls ring on the Teams dial pad on desktop, browser and mobile.

Can CommPortal open inside Teams?

Yes. Enter the CommPortal address as the website in your branded Teams app, and users get CommPortal in a tab. With Remember me checked, they usually sign in only once.

What does the Metaswitch administrator need to change?

To show CommPortal in Teams, its Content-Security-Policy header must allow teams.microsoft.com, *.teams.microsoft.com and *.skype.com as frame ancestors. If you use access lists or a firewall, we provide the addresses to allow.

Does it work with SIP auto-provisioning?

Yes. TeamMate can take a user’s SIP details from a provisioning server, and this has been tested with Metaswitch.

Do users need a Microsoft Teams Phone license?

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.

Do we need a session border controller (SBC)?

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.

Can we sell it under our own brand?

Yes. Service providers get a white-label portal and a Teams app with their own name and logo, and can provision customers in the portal or through a REST API. With Bespoke Access, customers can even complete Microsoft setup inside your own portal.

How is it priced, and can we try it?

It is priced per user, per month. Service providers can start with a free 30-day proof of concept on their own system.

Put Metaswitch in Microsoft Teams.

See it in a live demo, or start a proof of concept on your own Metaswitch system.

Free 30-day proof of concept for service providers.