Make and take Cisco calls on the Teams dial pad. Each Teams user registers to their own SIP line on Cisco Unified Communications Manager (CUCM), so numbers and call features stay on Cisco.
Free 30-day proof of concept for service providers.
It connects Cisco calling to Microsoft Teams so people can handle their calls without leaving Teams. TeamMate does this with PBX Connector: each Teams user registers to their own SIP line on Cisco Unified Communications Manager, and TeamMate automates the Direct Routing link and supplies the session border controllers. Service providers on Cisco BroadWorks can connect too.
Teams Calls becomes a softphone on Cisco, using the user’s Cisco number or extension, on desktop, browser and mobile.
Hold, transfer and voicemail still run on Cisco. Custom soft keys put the Cisco functions you choose one tap away.
New Cisco voicemail notifications arrive in Teams, so messages are not missed away from the desk phone.
On a Cisco call, Teams shows On a Call automatically. Presence Pause stops calls ringing through to Teams during meetings.
Transfer a Cisco call to anyone in Teams, with the transfer reported back to Cisco. 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 a SIP line on CUCM, so people can use Teams, a Cisco phone or both.
Service providers can put BroadWorks calling in Teams under their own brand. BroadWorks integration
ChatBridge links Teams and Webex chat in real time. Teams and Webex chat
Connect your Microsoft 365 tenant with minimal permissions.
Create a SIP line for each Teams user on CUCM, as you would for a third-party SIP phone, and enter the details. TeamMate builds the Direct Routing link.
Cisco calls ring in Teams on desktop, browser and mobile, alongside Cisco phones.
Most Cisco and Teams integrations use one of three approaches. They differ in where the call is answered and how many Cisco features come along.
A Teams app opens a separate Cisco softphone. Calls move out of Teams, and you support a second client on every desktop.
Cisco also rings a separate Teams number. Calls are answered in Teams, but Cisco features are lost and each user needs an extra number or trunk.
Each Teams user registers to Cisco like any SIP phone. Calls are answered in Teams with Cisco features kept and no extra number per user.
TeamMate also connects Mitel, 3CX, BroadWorks, Metaswitch, NetSapiens, Avaya 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 SIP line on Cisco Unified Communications Manager, so Cisco calls ring on the Teams dial pad on desktop, browser and mobile.
A SIP line for each Teams user, set up as you would for a third-party SIP phone. Numbers, call routing and carriers stay as they are.
Yes. Service providers on BroadWorks can connect it to Teams under their own brand. See the BroadWorks integration page.
Yes. ChatBridge links Microsoft Teams and Cisco Webex for real-time messaging between the two.
Yes. When a user is unavailable in Teams, Presence Pause can set them to Do Not Disturb on CUCM, using the standard SIP event package (RFC 6665).
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 Cisco system.
Free 30-day proof of concept for service providers.