Configure SIP Trunk with Microsoft Teams

Click the arrow to select the scenario that describes your deployment. In this case, select SIP Trunk ↔ Microsoft Teams.

Type up to 32 characters as a descriptive name for the SIP Trunk ↔ Microsoft Teams scenario.

The country in which the SIP Trunk↔ Microsoft Teams deployment originates.

Defines the Emergency Services for outgoing numbers. For the purpose of this illustration above, Emergency Services is not selected. Field definitions are defined below.

Options:  ELIN Identifier, E911/E112 or None.

Call Back Number in string format. This field is displayed only when ELIN Identifier or E911/E112 is selected from Emergency Services.

Second Call Back Number in string format. This field is displayed only when ELIN Identifier or E911/E112 is selected from Emergency Services.

Defines the Public Safety Answering Point Number. Valid entry 1 - 127 characters.

Number of simultaneous SIP sessions allocated. Valid entry 1 - 960.

The SIP trunk used for connection to the Microsoft Teams environment. For SBC 1000/2000 and SBC SWe Edge, valid options are: ATT SIP Trunk, KDDI SIP Trunk, NTT DOCOMO Officelink, Other SIP Trunk, SoftBank ConnecTalk, SoftBank White Office, Telstra Enterprise SIP Connect, Verizon SIP Trunk, and Twilio SIP Trunk. 

The SIP Trunk selected determines the field options displayed in Step 2. For more information, refer to Step 2 - Configure SIP Details for Endpoint.

The Teams connection type used for the network. Valid selections:

• Teams Direct Routing
• Teams Downstream SBC

The FQDN or IP address of the Remote Peer service provider.

The IP protocol used for sending and receiving SIP messages between the SBC and the Border Element Server. Valid entries: UDP or TCP.

The port number for the SIP server used to send and receive SIP messages between the SBC and the Border Element Server.

Enables or disables the secondary Remote Peer service provider configured. 

Specifies the Secondary Border Element Service provider. Valid entry: IP Address or FQDN. This field is available only when Use Secondary Border Element Server is Enabled.

The Protocol used for communicating with the Secondary Border Element Server. Valid entry: UDP or TCP. This field is available only when Use Secondary Border Element Server is Enabled.

The Port Number is used for sending and receiving messages between SBC and the Secondary Border Element server. This field is available only when Use Secondary Border Element Server is Enabled.

Indicates whether the AT&T Simultaneous Ring feature is supported. Valid entry: Yes or No.

Indicates whether the AT&T Toll Free option is enabled or disabled. Valid option: Enabled or Disabled.

The Toll Free Access Number to use when the AT&T IP Toll Free option is enabled.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

Type the FQDN for the service provider's SIP server.

Hardcoded to UDP.

Type the port number used for sending and receiving SIP messages between the SBC and the Border Element Server.

The main telephone number associated with the KDDI SIP trunk.

  Type the city code and office code for setting up transformation rules for the FMC service.

 Type the Address of Record of the client that is registered on the SIP server.

Type the host and port information for the FQDN or IP address used in the From Header. Valid options: FQDN[:port] or IP4 [:port] or [IP6]:port

Specifies a user name to use in response to a challenge.

The password for the Authentication ID.

Re-enter the password for the Authentication ID.

Click () to specify the DNS server IP address (IPv4 or IPv6) of the DNS server. The DNS Server IP address is for an SBC 1000/2000 that uses Split DNS with a primary DNS server, secondary DNS server, and a domain-specific DNS server for resolving FQDNs as required on internal and external networks.

Specify the domain name associated with the DNS IP address.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

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.

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.

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. I

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The FQDN or IP address of the Remote Peer service provider.

The IP protocol used for sending and receiving SIP messages between SBC and the Border Element Server. Valid entry UDP or TCP.

The SIP Server Port number used for sending and receiving SIP messages between SBC and the Border Element Server.

Enables or disables the secondary Remote Peer service provider configured. 

Specifies the Secondary Border Element Service provider. Valid entry: IP Address or FQDN. This field is available only when Use Secondary Border Element Server is Enabled.

The Protocol used for communicating with the Secondary Border Element Server. Valid entry: UDP or TCP. This field is available only when Use Secondary Border Element Server is Enabled.

The Port Number used for sending and receiving messages between SBC and the Secondary Border Element server. This field is available only when Use Secondary Border Element Server is Enabled.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

The SBC inserts the configured FQDN in the requests and responses sent toward Microsoft Teams. Microsoft Teams can then reach the SBC successfully based on the configured FQDN.

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The host IP address or FQDN of the primary SIP server.

Re-enter the password for the router that serves as the network gateway.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

Allows you to configure the SBC behind a NAT device, and uses the IP of the NAT device for all outgoing messages. If you enable this field, you must configure the Public IP address field. This field has the following options:

• Disabled - The SBC does not use the NAT for the NAT device's public IP address.
• Enabled - The SBC uses the NAT for the NAT device's public IP address.

NOTE: You must enable this field when the SBC interface has a private IP and the NAT device uses a public IP. For details on configuring an SBC behind the NAT, refer to Configuring the SBC Edge Portfolio for NAT Traversal.

Specifies whether an Access Control List (ACL) applies to the Microsoft Teams connection. An ACL provides security to an SBC that uses a Public IP. This field has the following options:

• True - Applies the ACL.
• False - Does not apply the ACL.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The method used for connecting networks. Options are: Routerless and Router. On selection of Routerless, the Easy Config displays the Signaling/Media Source IP field and the SIP Server field. On selection of Router, the Easy Config displays the SIP Server field only.

Click the arrow and select the user-specified IP address to be used for SIP signaling messages. The Signaling/Media Source IP field does not display when the option selected for the WAN Link field is Router.

The host IP address or FQDN for the SIP server

The ID used for authenticating with the router at the gateway of the network

The password used for authenticating with the router at the gateway of the network.

Re-entry of the password for the router serving as network gateway.  

The public address that points to the domain for users, for use in the Contact Registrant Entry. For example, enter GatewayID@SIPServer.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The public interface used for Network Address Translation (NAT).

The state to use in configuring the outbound proxy for the Provider SIP Trunk. Options include: Australia Capital Territory, New South Wales, Northern Territory, Queensland, South Australia, Tasmania, Victoria, and Other (a user-specified FQDN).

Hard coded as UDP and Port 5060.

The IPv4 address used to create a Split DNS entry for the Telstra domain.

The SIP Connect Domain or Realm to which the specified IP address will map.

The User ID for use in authentication.

The password to use when authenticating with the User ID.

The re-entered password for confirmation.

The 9-digit pilot number Telstra assigned for use with the SIP Connect trunking service.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The FQDN or IP address of the Remote Peer service provider.

The IP protocol used for sending and receiving SIP messages between the SBC and the Border Element Server. Valid entries: UDP or TCP.

The port number for the SIP server used to send and receive SIP messages between the SBC and the Border Element Server.

Enables or disables the secondary Remote Peer service provider configured. 

Specifies the Secondary Border Element Service provider. Valid entry: IP Address or FQDN. This field is available only when Use Secondary Border Element Server is Enabled.

The Protocol used for communicating with the Secondary Border Element Server. Valid entry: UDP or TCP. This field is available only when Use Secondary Border Element Server is Enabled.

The Port Number is used for sending and receiving messages between SBC and the Secondary Border Element server. This field is available only when Use Secondary Border Element Server is Enabled.

Select the external (Internet-facing) IP address for the server that handles routing of messages for signaling and media.

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.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

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.

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.

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.

The FQDN or IP address of the Remote Peer service provider.

The IP protocol to use for sending and receiving SIP messages between SBC and the Border Element Server. This value is fixed at UDP.

The SIP Server Port number used for sending and receiving SIP messages between SBC and the Border Element Server.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

The SBC inserts the configured FQDN in the requests and responses sent toward Microsoft Teams. Microsoft Teams can then reach the SBC successfully based on the configured FQDN.

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments

The FQDN or IP address of the Remote Peer service provider.

The IP protocol to use for sending and receiving SIP messages between SBC and the Border Element Server. This value is fixed at UDP.

The SIP Server Port number used for sending and receiving SIP messages between SBC and the Border Element Server.

The Teams connection type used for the network. Valid selections:

• Standalone Direct Connection
• Local Media Optimization

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

The SBC inserts the configured FQDN in the requests and responses sent toward Microsoft Teams. Microsoft Teams can then reach the SBC successfully based on the configured FQDN.

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.

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.

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.

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

Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing: 

• 52.112.0.0, with netmask 255.252.0.0
• 52.120.0.0, with netmask 255.252.0.0

For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments