Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Info |
---|
Support for an SBC behind a NAT is in SBC Edge 1000/2000 Release 8.0.2 and later only; support in SBC SWe Lite is planned for a later release. |
Anchor | ||||
---|---|---|---|---|
|
In the WebUI, click the Tasks tab.
In the left navigation pane, go to SBC Easy Setup > Easy Config Wizard.
Tip | ||||
---|---|---|---|---|
Make sure the
|
Caption | ||||
---|---|---|---|---|
| ||||
Panel | ||||
---|---|---|---|---|
| ||||
The scenario in which the configuration template is provided. In this case, select IP PBX ↔ Microsoft Teams. |
Panel | ||||
---|---|---|---|---|
| ||||
Type a short description of the IP PBX ↔ Microsoft Teams deployment.
|
Panel | ||||
---|---|---|---|---|
| ||||
The country from which the SIP Trunk ↔ IP PBX set up originates. |
Panel | ||||
---|---|---|---|---|
| ||||
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.
|
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Panel | ||||
---|---|---|---|---|
| ||||
Specify the number for the Public Safety Answering Point. Valid entry: 1 - 127 characters. |
Panel | ||||
---|---|---|---|---|
| ||||
Specify the number of simultaneous SIP-to-Destination sessions required for the deployment. |
Panel | ||||
---|---|---|---|---|
| ||||
Specify the type of the PBX used in the deployment. Valid entry: Cisco CUCM, Other IP PBX, or Avaya SM/CM. |
Panel | ||||
---|---|---|---|---|
| ||||
Specify the type of user that will access services provided in the deployment. |
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.
Caption | ||||
---|---|---|---|---|
| ||||
Panel | ||||
---|---|---|---|---|
| ||||
Specify the IP address or FQDN for the host in the deployment. |
Panel | ||||
---|---|---|---|---|
| ||||
Specify the protocol to use for communicating with the IP PBX. Valid entry: UDP or TCP. |
Panel | ||||
---|---|---|---|---|
| ||||
Specify the port number used for sending SIP messages to and receiving SIP messages from the IP PBX. |
Panel | ||||
---|---|---|---|---|
| ||||
Indicate whether a secondary server is required for the deployment. Valid entry: Enabled or Disabled. |
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 1: sip.pstnhub.microsoft.com |
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 2: sip2.pstnhub.microsoft.com |
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 3: sip3.pstnhub.microsoft.com |
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN for use with Microsoft Teams Direct Connect: sip-all.pstnhub.microsoft.com |
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for the port used for TLS: 5061 |
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.
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|