Not supported by SBC SWe Lite.
Usage of the Easy Configuration wizard to configure the SBC Edge (SBC) does not modify existing configuration. The wizard will simply add the new configuration elements to the SBC.
The SBC Easy Configuration interface includes a built-in step-by-step wizard, which enables end-users to quickly deploy the SBC and Microsoft Teams. The SBC can be configured to connect a Microsoft Teams environment with a PSTN Provider through ISDN.
Step 1 - Configure Scenario
Select the Application type (ISDN PTSN ↔ 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
One unassigned ISDN Signaling port must be available for the ISDN application options to be displayed.
The scenario in which the configuration template is provided. In this case, select ISDN PSTN ↔ Microsoft Teams.
Enter the name to describe the ISDN PSTN ↔ Microsoft Teams setup.
This value will be prefixed on all the SBC configuration elements created by the Setup Wizard pertaining to this deployment.
The country in which the ISDN PSTN ↔ Microsoft Teams setup originates.
The E911 Elin number from the "CompanyName" field configured in Lync location services is used as the authoritative Call Back number for outgoing E911 calls, and is always the preferred configuration. Specifically, it will take precedence over any Callback Number number configuration in Lync Setup. For more information, see Creating and Modifying Entries to Transformation Tables.
Defines the Emces for outgoing numbers. For the purpose of this illustration above, Emergency Services is not selected. Related field descriptions follow.
- None. Does not use Emergency Services.
Emergency Callback Number 1
Callback Number in string format. This field is displayed only when the value for the Emergency Services field is ELIN Identifier or E911/E112.
Emergency Callback Number 2
Second Callback Number in string format. This field is displayed only when the value for the Emergency Services field is ELIN Identifier or E911/E112.
Specifies the Public Safety Answering Point Number. Valid entry 1 - 127 characters.
Sets the Provider Type to ISDN.
Defines the user type as Microsoft Teams.
Step 2 - Configure Provider and User Side Information
Enter the scenario configuration details based on the endpoint selected. Once completed, click Next to move to Step 3 (or Previous to return to the previous screen).
ISDN - Field Definitions
Specifies the physical T1/E1 port used for this Signaling Group. Valid option: T1 or E1.
The physical T1/E1 port number to which the PSTN line is physically connected. DS1 entries are configured with the following command buttons: Up (move a DS1 port up in the list), Down (move a DS1 port down in the list), Add (adds a DS1 port), and Remove (deletes a DS1 port).
For example, click Add. Select the desired PSTN port and OK.
Specifies the ISDN variant for the port type in the ISDN Signaling Group.
- ATT 4EES
- ATT 5EES
- DMS 100
- Euro ISDN
- Japanese ISDN
ISDN Number Translation
Determines if the SBC should translate dialed PSTN digits as phone extensions. Valid options: Translation Extension (translates digits into phone extensions) or Passthrough Untranslated (does not translate digits).
The numbers to prefix for the translated phone extension. This field is available only when ISDN Number Translation is set to Translation Extension.
The number of digits used to account for the PSTN extension. Valid options: 2, 3, 4, or 5.This field is available only when ISDN Number Translation is set to Translation Extension.
Specifies the source of the systems transmit clock.
- System: The built-in oscillator is used to transmit data over synchronous links.
- Network: The clock is derived from the data received from the peer devices on the network.
Specifies the ISDN user/network side for this signaling group to be created by this wizard.
Specifies 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.
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.
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
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
Hard-coded value for the port used for TLS: 5061
Step 3 - Confirm and Submit Configuration
This steps displays a summary of the configuration items from Step 1 and Step 2. Click Finish to submit (to cancel the configuration, click Cancel).
This example displays a ISDN PSTN ↔ Microsoft Teams setup.