Put your BroadWorks calling on the Teams dial pad, under your own brand. Each Teams user registers as a BroadWorks user, so numbers, features and voicemail stay on BroadWorks.
Free 30-day proof of concept for service providers.
It connects Cisco BroadWorks to Microsoft Teams so your customers can handle their BroadWorks calls without leaving Teams. TeamMate does this with PBX Connector: each Teams user registers to BroadWorks with their own address of record, and TeamMate automates the Direct Routing link and supplies the session border controllers. BroadWorks stays the phone system, and you keep the customer.
Teams Calls becomes a softphone on BroadWorks, using the user’s BroadWorks number or extension, on desktop, browser and mobile.
Hold, transfer and voicemail still run on BroadWorks. Custom soft keys put the BroadWorks functions you choose one tap away.
New BroadWorks voicemail notifications arrive in Teams, so messages are not missed away from the desk phone.
On a BroadWorks call, Teams shows On a Call automatically. Presence Pause stops calls ringing through to Teams during meetings.
Transfer a BroadWorks call to anyone in Teams, with the transfer reported back to BroadWorks. How Pro Transfer works
Show caller details from your CRM or other systems as a card in Teams before the call is answered.
Add a PBX location for each BroadWorks source, on the same or different SIP domains, so groups, enterprises or service providers can all route calls into one Microsoft 365 tenant.
DNS SRV or host lookup, UDP, TCP or TLS transport, your outbound proxy and your codec order.
TeamMate’s platform team previously worked at BroadSoft, Cisco and VoIP Logic. About TeamMate
Add your branding and connect the customer’s Microsoft 365 tenant with minimal permissions.
Enter the SIP domain, outbound proxy, lookup type, transport and voicemail feature code. For each user, add their address of record, line ID and SIP password. TeamMate builds the Direct Routing link.
BroadWorks calls ring in Teams on desktop, browser and mobile, alongside existing phones and clients.
Most BroadWorks and Teams integrations use one of three approaches. They differ in where the call is answered and how many BroadWorks features come along.
A Teams app opens a separate BroadWorks softphone. Calls move out of Teams, and you support a second client on every desktop.
BroadWorks also rings a separate Teams number. Calls are answered in Teams, but BroadWorks features are lost and each user needs an extra number or trunk.
Each Teams user registers to BroadWorks like any SIP phone. Calls are answered in Teams with BroadWorks features kept and no extra number per user.
TeamMate also connects Mitel, 3CX, 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 BroadWorks with their own address of record, so BroadWorks calls ring on the Teams dial pad on desktop, browser and mobile, with BroadWorks features and voicemail.
The user’s address of record as the SIP user, their line ID as the authentication ID, and the SIP password. For the location, the SIP domain, outbound proxy and voicemail feature code.
Yes. Add a PBX location for each BroadWorks source, on the same or different SIP domains, and route them all into the customer’s single Microsoft 365 tenant.
Yes. You choose per user whether to use BroadWorks voicemail instead of Teams voicemail.
Yes. When a user is unavailable in Teams, for example in a meeting, Presence Pause can set them to Do Not Disturb on BroadWorks so calls follow their busy handling. This uses the standard SIP event package (RFC 6665), which BroadWorks 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.
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.
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 BroadWorks system.
Free 30-day proof of concept for service providers.