---
title: "Configure Connector for BroadWorks"
slug: "configure-connector-for-broadworks"
updated: 2026-01-21T22:47:33Z
published: 2026-01-21T22:47:33Z
canonical: "kb.connecttoteams.com/configure-connector-for-broadworks"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.connecttoteams.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Connector for BroadWorks

The field types used in this system to define **PBX Location** and **PBX User** details may vary depending on the PBX platform. For enterprises using **BroadWorks** platform, we've provided this dedicated guide to assist with setup.

**BroadWorks** is a widely used multi-tenant PBX platform. The information required to set up a BroadWorks system maps directly to the fields needed to connect a BroadWorks SIP user to Microsoft Teams using ConnecttoTeams:

![](https://cdn.elev.io/file/uploads/lWNkjTie1mEAGuhwq3R2SqTFcax3a6BIA1xEV-d9OvM/IyiNwZGAsI-btEo3z8DiU60bkdQDNVyFMfRiw8LGsHM/1612384391349-RDU.png)

To configure the PBX Location, complete the fields shown above using the reference table below:

| Field | Selection | Description |
| --- | --- | --- |
| PBX Type | BroadWorks | PBX Manufacturer |
| PBX Location | Label as you see fit | Label the PBX something descriptive, particularly if the enterprise will have multiple PBXs. |
| PBX DNS Lookup type | [SRV](/v1/docs/dns-srv) | The method to look up the SIP registration locations. |
| PBX Outbound Transport Type | UDP | Transport type: UDP, TCP, TLS or combination UDP/TCP. UDP is preferred, but has [implications for PIDF/LO emergency calls.](/v1/docs/teams-dynamic-emergency-calling) |
| PBX SIP Domain | PBX Domain |  |
| PBX SIP Domain Proxy | Outbound Proxy |  |
| PBX SIP Domain Proxy Port | 5060 - Standard Port | If you are using a non-standard port enter it in this field. This field only appears when using HOST lookup. |
| Voicemail Feature Code | Feature Code for Voicemail access from a registered phone. | The Feature Code used to dial into Voicemail from a registered Phone (i.e. *86) |
| Codecs | Choose which codecs you wish to use in the order you want them to be attempted |  |

---

## Add User

To set up a BroadWorks User with the PBX Connector, you will need to complete the fields below per the instructions in the Table.

![](https://cdn.elev.io/file/uploads/lWNkjTie1mEAGuhwq3R2SqTFcax3a6BIA1xEV-d9OvM/dY1F0VDxRhqIwGssqfXvoS359A7Ag3uUSNnIwReNgSI/1652484524354-sU4.png)

| Field | Selection | Description |
| --- | --- | --- |
| PBX Locations | Choose desired PBX location from the dropdown | It is common for enterprises to only have one PBX location. |
| Available Voice Routes | Choose desired voice route from the dropdown | It is common for enterprises to only have one voice route. Best practice is to choose the route geographically closest to the user. |
| Teams User | Teams User to be connected | Teams Users with the right licensing will be presented in the dropdown for selection |
| Phone Number | 3 to 15 digits | Number or extension associated with the PBX User |
| SIP User | SIP User ID | BroadWorks AoR for the User |
| SIP Authentication ID | Line ID |  |
| SIP Password | SIP Password |  |
| Disable Voicemail in Teams? | Check box if the user will be using PBX voicemail over Teams voicemail | See [here](/v1/docs/what-does-disable-voicemail-in-teams-actually-do) for details. |

---

### FAQ

#### Can I connect two BroadWorks Enterprises to the same Microsoft Teams tenant?

No.

Each **ConnecttoTeams enterprise** represents a single **Microsoft 365 tenant**. However, within that enterprise, you can create **multiple PBX configurations** to support different BroadWorks entities.

**PBX configurations are associated with a SIP domain, but that domain could exist in one or more BroadWorks entities** (like departments, groups, enterprises, or service providers). You can have multiple PBX Locatoins – possibly associated with the same or different domains – in the same ConnecttoTeams enterprise.

This allows voice services from multiple BroadWorks sources to be routed into a single Microsoft Teams tenant.

A voice route, also called gateway, refers to the configuration settings that determine how incoming and outgoing phone calls made through Microsoft Teams are directed to the appropriate phone number on the PSTN, essentially defining the path a call takes based on the dialed number. This is represented as a "online voice routing policy" within the Microsoft Teams Admin Center.