Ribbon Documentation Portal will be unavailable Thursday February 2nd 2023 between 2:00 PM EST ~ 12:00 PM. More Info
Skip to end of metadata
Go to start of metadata

The SBC Easy Config interface includes a built-in, step-by-step configuration wizard that enables quick and easy set up of the SBC  in a deployment that includes endpoints for an IP PBX and Microsoft Teams.

Step 1 - Select Scenario

  1. In the WebUI, click the Tasks tab.

  2. In the left navigation pane, go to SBC Easy Setup > Easy Config Wizard

    Make sure the SBC Easy Configuration wizard is running. For details, refer to Using the Easy Configuration Wizard. The Easy Config wizard on the SBC 1000/2000 creates the requested configuration by using the current configuration as a starting point. Existing configuration elements are retained, and the requested endpoint configurationa are added as new configuration elements

  3. Select the Application  (IP PBX↔ Microsoft Teams). Enter the scenario configuration details based on your deployment settings. Once completed, click Next to move to Step 2, or click Cancel to return to the main WebUI screen.

Scenario – Field Definitions

Step 1


The scenario in which the configuration template is provided. In this case, select IP PBX ↔ Microsoft Teams.

Scenario Description

Type a short description of the IP PBX ↔ Microsoft Teams deployment.

This value can be up to 32 characters long and is prefixed onto the names of all SBC configuration elements created by the Easy Config Wizard for the deployment.

Telephone Country

The country from which the SIP Trunk ↔ IP PBX set up originates.

Emergency Services

Defines the Emergency Services functionality for outgoing numbers. For optimal field display, Emergency Services is not selected in the screens provided as examples. Fields descriptions follow. Options: ELIN Identifier, E911/E112, or None.

The E911 Elin number from the "CompanyName" field configured in Lync location services is used as the authoritative Callback Number for outgoing E911 calls, and is always the preferred configuration. Specifically, the location services configuration for the calling client will take precedence over any Callback Numbers indicated in the Easy Config wizard. For more information, refer to Creating and Modifying Entries to Transformation Tables.

Emergency Callback Number 1

Specify the first Callback Number in string format. This field displays only when ELIN Identifier or E911/E112 is the value set for the Emergency Services field.

Emergency Callback Number 2

Specify the second Callback Number in string format. This field displays only when ELIN Identifier or E911/E112 is the value set for the Emergency Services field.

PSAP Number

Specify the number for the Public Safety Answering Point. Valid entry: 1 - 127 characters.

SIP Sessions (SIP Properties)

Specify the number of simultaneous SIP-to-Destination sessions required for the deployment.

Type (IP PBX)

Specify the type of the PBX used in the deployment. Valid entry: Cisco CUCM, Other IP PBX, or Avaya SM/CM.

User Type (Microsoft Teams)

Specify the type of user that will access services provided in the deployment.

Step 2 – Configure PBX and Teams Details for Endpoints

Specify the configuration details based on the User- and Provider-side endpoints used for the deployment. Once completed, click Next to move to Step 3. (Or, click Previous to correct values on the previous screen.)

These fields apply if you selected IP PBX in Step 1 - Select Scenario.

Other SIP Trunk



Specify the IP address or FQDN for the host in the deployment.


Specify the protocol to use for communicating with the IP PBX. Valid entry: UDP or TCP.

Port Number

Specify the port number used for sending SIP messages to and receiving SIP messages from the IP PBX.

Use Secondary Server

Indicate whether a secondary server is required for the deployment. Valid entry: Enabled or Disabled.

Signaling/Media Source IP (Microsoft Teams Direct Connect)

Click the arrow to select the external (Internet-facing) IP address of the Microsoft Teams Direct Connect server that handles routing of messages for signaling and media.

Outbound NAT Traversal

Allows the SBC to be placed behind a NAT device, and uses the IP of the NAT device for all outgoing messages. If this field is set to Enable, the Public IP address field configuration is required. Valid selections:

Enable: Network Address Translation is used for the NAT device's Public IP address.

Disable: Network Address Translation address translation is not used.

NOTE: This field is required when the SBC interface has a private IP and the NAT device is using a public IP. For details on configuring an SBC behind the NAT, refer to Configuring the SBC Edge for NAT Traversal.


Public IP Address

Specifies the Public IP address of the NAT device. The SBC uses this IP as the source IP for all the outgoing messages. This field is required only when Outbound NAT Traversal is configured to Enable.

Apply ACL

Specifies whether an ACL (Access Control List) is applied to the Microsoft Teams connection. An ACL provides security to an SBC using a Public IP.

Valid selection:

True: Applies the ACL

False: Does not apply the ACL. 

For details on configuring an ACL to be applied to an SBC, refer to Managing Access Control Lists.


Server Pool Host 1

Hard-coded FQDN for the location of the server list for Server Pool Host 1: sip.pstnhub.microsoft.com

Server Pool Host 2

Hard-coded FQDN for the location of the server list for Server Pool Host 2: sip2.pstnhub.microsoft.com

Server Pool Host 3

Hard-coded FQDN for the location of the server list for Server Pool Host 3: sip3.pstnhub.microsoft.com

Federated FQDN

Hard-coded federated FQDN for use with Microsoft Teams Direct Connect: sip-all.pstnhub.microsoft.com


Hard-coded value for protocol used with federated FQDN: TLS

Port Number

Hard-coded value for the port used for TLS: 5061

Step 3 – Confirm and Submit Configuration

This step displays a summary of the the configuration items from Step 1 and Step 2. Click Finish. This example displays the summary for an IP PBX↔ Microsoft Teams configuration.

Step 3