Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c87befb553017c1aa323650024, userName='null'}
JIRAIDAUTHCHOR-8548
REV5UserResourceIdentifier{userKey=8a00a0c87befb553017c1aa323650024, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86a61778d016a7d0876df0017, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86a61778d016a7d0876df0017, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4


The

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

Step 1 - Select Scenario
Anchor
Step 1 - Select Scenario
Step 1 - Select Scenario

Start

  1. In the WebUI, click the Tasks tab.

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

    Tip
    titleTip

    Make sure the

    Spacevars
    0product2
    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 configuration are added as new configuration elements.


  3. From the Application dropdown list, select IP PBX ↔ Microsoft Teams.
  4. Configure per the field definitions below and click Next.


Scenario Field Definitions

FieldDescription
Scenario Parameters
ApplicationConfiguration template used: IP PBX ↔ Microsoft Teams.
Scenario Description

Name to describe the setup.

Info
titleNote

The Easy Config adds the scenario description as a prefix for all SBC configuration elements created for this deployment.


Telephone CountryCountry in which the IP PBX ↔ Microsoft Teams is set up.
Emergency Services

Defines the Emergency Services for outgoing numbers. For the purpose of this illustration above, Emergency Services is not selected. Related field descriptions follow.

Options:

    • ELIN Identifier
    • E911/E112
    • None
Info
titleNote

The E911 Elin number from the "CompanyName" field configured in Skype 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 1First 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 2Second 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 NumberDefines the Public Safety Answering Point Number. Valid entry: 1 - 127 characters. This field displays only when ELIN Identifier or E911/E112 is the value set for the Emergency Services field.
SIP Sessions (SIP Properties)Specifies the number of simultaneous SIP-to-Destination sessions required for the deployment.
IP PBX
Type 

Specify the type of the PBX used in the deployment. Valid options:

    • Cisco CUCM
    • Other IP PBX
    • Avaya SM/CM
Microsoft Teams
Teams Connection

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

    • Teams Direct Routing
    • Teams Downstream SBC



Step 2 - Configure PBX and Teams Details for Endpoints

Start

  1. Configure the IP PBX provider information (see below for field definitions).
  2. Configure the connection type information (see below for field definitions).
  3. Click Next.

    Microsoft Teams: Teams Direct Routing - Standalone Direct Connection


    Microsoft Teams: Teams Direct Routing - Local Media Optimization


    Microsoft Teams: Teams Downstream SBC


Field Definitions

FieldDescription
IP PBX: <Type>
HostSpecify the IP address or FQDN for the host in the deployment.
Protocol

Specify the protocol to use for communicating with the IP PBX. Valid options:

  • UDP 
  • TCP
Port NumberSpecify the port number used for sending SIP messages to and receiving SIP messages from the IP PBX.
Use Secondary ServerEnables or disables a secondary server for the deployment. 
Secondary Server HostSpecifies the Secondary Server Host. This field is available only when Use Secondary Server is Enabled.
ProtocolThe Protocol used for communicating with the Secondary Server Host. Valid options:
  • UDP 
  • TCP

This field is available only when Use Secondary Server is Enabled.

Port NumberThe Port Number used for sending and receiving messages between SBC and the Secondary Server Host. This field is available only when Use Secondary Server is Enabled.
Microsoft Teams: Teams Direct Routing

Teams Connection Type: Standalone Direct Connection

Signaling/Media Source IP (Teams Attributes)External (Internet-facing) IP address of the Microsoft Teams Direct Routing 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 options:

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


Info
titleNote

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 Portfolio for NAT Traversal.


Public IP AddressSpecifies 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 Access Control List (ACL) is applied to the Microsoft Teams connection. An ACL provides security to an SBC using a Public IP.

Valid options:

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

ProtocolHard-coded value for protocol used with federated FQDN: TLS.
Server Port NumberHard-coded value for the port used for TLS: 5061.
Listening Port NumberPort number used for sending and receiving SIP messages between the SBC and the Border Element Server.
Teams Connection Type - Local Media Optimization (Microsoft Teams Direct Routing media flow uses the shortest path to improve the SBC Edge's media quality and bandwidth usage)
Signaling/Media Source IP (Teams Attributes)External (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media. 
Private Media Source IPPrivate IP address that handles routing of messages for 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 options:

    • Enable: Network Address Translation is used for the NAT device's Public IP address.
    • Disable: Network Address Translation address translation is not used.
Info
titleNote

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 Portfolio for NAT Traversal.


Public IP AddressSpecifies 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 Access Control List (ACL) is applied to the Microsoft Teams connection. An ACL provides security to an SBC using a Public IP.

Valid options:

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

ProtocolHard-coded value for protocol used with federated FQDN: TLS.
Server Port NumberHard-coded value for the port used for TLS: 5061.
Listening Port NumberPort number used for sending and receiving SIP messages between the SBC and the Border Element Server.
Protocol (Downstream Attributes)Hard-coded value for protocol used with federated FQDN: TLS.
Downstream SBC Signaling Listen PortPort number used for sending and receiving SIP messages between the Downstream SBC and the Border Element Server. Valid entry: 1024-65535.
Max. Users per Downstream SBCMaximum number of users per Downstream SBC. Valid entry: 1 - 1000.
Microsoft Teams: Teams Downstream SBC
Signaling/Media Source IPExternal (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media.
Teams Proxy SBCThe IP/FQDN for the Proxy SBC for TLX to properly establish.
ProtocolHard-coded value for protocol used with federated FQDN: TLS.
Port NumberThe port used for TLS. Valid entry: 1024 - 65535.
SBC FQDNFQDN for the SBC.


Step 3 - Confirm and Submit Configuration

This step displays a summary of the the configuration items from Step 1 and Step 2.

Start

  1. Click Finish. 


This example displays an IP PBX ↔ Microsoft Teams with an Other IP PBX type.