Make and take Grandstream UCM calls on the Teams dial pad. Each Teams user registers to their own UCM extension, like any SIP phone, so numbers, ring groups, queues and voicemail keep working, with no trunk to set up on the UCM.
Free 30-day proof of concept for service providers.
It connects your Grandstream UCM IP PBX to Microsoft Teams so people can handle their UCM calls without leaving Teams. TeamMate does this with PBX Connector: each Teams user registers to their own UCM extension, and TeamMate automates the Direct Routing link and supplies the session border controllers. Your UCM stays the phone system. Teams becomes the place people use it.
Grandstream documents the setup in its own knowledge base: Connecting UCM and Microsoft Teams via TeamMate.
Teams Calls becomes a softphone on the UCM, using the user’s UCM number or extension, on desktop, browser and mobile.
Hold, transfer, ring groups, queues and voicemail still run on the UCM, and calls show in the UCM call records like any other endpoint.
New UCM voicemail notifications arrive in Teams, so messages are not missed away from the desk phone.
On a UCM call, Teams shows On a Call automatically. Presence Pause stops calls ringing through to Teams during meetings.
Transfer a UCM call to anyone in Teams, with the transfer reported back to the UCM. How Pro Transfer works
Show caller details from your CRM or other systems as a card in Teams before the call is answered.
Grandstream partners can package TeamMate with the UCM in one of two ways, and use both for different customers.
Each Teams user registers to their own UCM extension, so UCM queues, transfers, voicemail and presence carry over to Teams. PBX Connector
Connect the UCM to Teams as a SIP trunk, and TeamMate automates the Direct Routing build, users and call paths. SIP Trunk Connector
Sell either option as your own service, with a white-label portal and Teams app.
Add your branding and connect the customer’s Microsoft 365 tenant with minimal permissions.
Enter the UCM hostname, transport and port, then link each Teams user to their UCM extension and SIP credentials. TeamMate builds the Direct Routing link.
UCM calls ring in Teams on desktop, browser and mobile, alongside Grandstream Wave and desk phones.
Most Grandstream and Teams integrations use one of three approaches. They differ in where the call is answered and how many UCM features come along.
A Teams app opens a separate softphone such as Grandstream Wave. Calls move out of Teams, and you support a second client on every desktop.
The UCM also rings a separate Teams number. Calls are answered in Teams, but UCM features are lost and each user needs an extra number or trunk.
Each Teams user registers to the UCM like any SIP phone. Calls are answered in Teams with UCM features kept and no extra number per user.
TeamMate also connects 3CX, Mitel, BroadWorks, Metaswitch, NetSapiens, Avaya, 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 UCM extension, so UCM calls ring on the Teams dial pad on desktop, browser and mobile, with UCM features like ring groups, queues, transfer and voicemail. Grandstream documents the setup in its own knowledge base.
Grandstream documents the integration for the UCM6300 series and UCM6300 Audio series. Other UCM models that accept third-party SIP softphones generally work the same way, and we confirm your model and firmware during a proof of concept.
No. With PBX Connector each Teams user is simply another endpoint on a UCM extension, so there is no trunk to set up on the UCM. Calls appear in the UCM call detail records like any other phone.
The UCM hostname or IP address, transport and port, reachable from the internet or over a VPN, and support for G.711 or G.722. For each user: the UCM extension, SIP user ID, authentication ID and password.
Use PBX Connector when you want each Teams user to be a UCM extension with UCM features. Use SIP Trunk Connector when you want Teams to handle calling natively, with the UCM as the trunk.
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.
Yes. Grandstream partners and 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.
It is priced per user, per month. Service providers can start with a free 30-day proof of concept on their own UCM.
See it in a live demo, or start a proof of concept on your own UCM.
Free 30-day proof of concept for service providers.