Page History
...
CSS Stylesheet |
---|
img.confluence-embedded-image { display: inline-block !important; } |
Add_workflow_for_techpubs AUTH1 UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} JIRAIDAUTH SYM-28532 REV5 UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a0c86573c0900165b31a689f0052, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a0c86a61778d016a7d0876df0017, userName='null'}
Contents
Panel | ||||
---|---|---|---|---|
|
Tip | ||||
---|---|---|---|---|
Using the Easy Configuration wizard to configure the
|
...
- ATT SIP Trunk
- KDDI SIP Trunk
- NTT DOCOMO Officelink
- Other SIP Trunk
- SoftBank ConnecTalk
- Softbank White Office
- Telstra Enterprise SIP Connect Verizon SIP Trunk
- Twilio SIP Trunk
...
Spacevars | ||
---|---|---|
|
...
- SIP
...
- Other SIP Trunk
- Verizon SIP Trunk
Info |
---|
NTT DOCOMO Officelink, SoftBank ConnecTalk, Softbank White Office, Telstra Enterprise SIP Connect, ATT SIP Trunk, and KDDI SIP Trunk are supported in the SBC 1000-2000 only. |
...
Info |
---|
The E911 ELIN number from the "CompanyName" field configured in Lync Skype 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 SetupSkype Setup. For more information, see Creating and Modifying Entries to Transformation Tables. |
...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
The SIP trunk used for connection to the Microsoft Teams environment. For SBC 1000/2000 and
Spacevars | | 0 | series5, valid options are Other SIP Trunk, Telstra Enterprise SIP Connect, and Verizon SIP Trunk.
...
Panel | ||||
---|---|---|---|---|
| ||||
The Teams connection type used for the network. Valid selections:
NOTE: For
|
Step Step 2 - Configure SIP Details for Endpoint
...
ATT SIP Trunk - Field Definitions
...
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
...
KDDI SIP Trunk - Field Definitions
...
These fields apply if you selected KDDI SIP Trunk in Step 1 - Select Scenario.
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
...
NTT DOCOMO Officelink- Field Definitions
Include Page
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
...
Panel | ||||
---|---|---|---|---|
| ||||
The Teams connection type used for the network. Valid selections:
| ||||
|
Signaling/Media Source IP (Microsoft Teams Direct Routing)
...
Panel | ||||
---|---|---|---|---|
| ||||
This field is available for
The SBC inserts the 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. |
...
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.NOTE: This field is not applicable to
|
Public IP Address
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 | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
...
SoftBank ConnecTalk - Field Definitions
...
These fields apply if you select SoftBank ConnecTalk in Step 1 - Select Scenario.
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
The hard-coded value for the protocol that the SBC uses with the federated FQDN: TLS |
...
SoftBank White Office - Field Definitions
...
These fields apply if you selected SoftBank White Office in Step 1 - Select Scenario.
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
...
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for the port used for TLS: 5061 |
...
Twilio SIP Trunk - Field Definitions
These fields apply if you selected Verizon Twilio SIP Trunk in Step 1 - Select Scenario.
Border Element Server
Panel | ||||
---|---|---|---|---|
| ||||
The FQDN or IP address of the Remote the Remote Peer service provider. |
Protocol Protocol
Panel | |
---|---|
bgColor | #FAFAFA |
none | The IP protocol to use used for sending and receiving SIP messages between the SBC and the Border Element Server. This value is fixed at UDPValid entries: UDP or TCP. |
Port Number Number
Panel | |
---|---|
bgColor | #FAFAFA | borderStyle | none
The SIP Server Port number used for sending and receiving port number for the SIP server used to send and receive SIP messages between the SBC and the Border Element Server. |
...
Use Secondary Border Element Server
Panel |
---|
Enables or disables the secondary Remote Peer service provider configured. |
Secondary Border Element Server
Panel |
---|
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. |
Protocol
Panel |
---|
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. |
Port Number
Panel |
---|
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. |
Signaling/Media Source IP
Panel |
---|
Select the external (Internet-facing) IP address for the server that handles routing of messages for signaling and media. |
Outbound NAT IP
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:
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. |
Teams Connection Type
Panel | ||||
---|---|---|---|---|
| ||||
The Teams connection type used for the network. Valid selections:
|
Signaling/Media Source IP (Microsoft Teams Direct Routing)
Panel | ||||
---|---|---|---|---|
| ||||
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. |
Outbound NAT Traversal
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. |
Public IP Address
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. |
Apply ACL
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. |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
Verizon SIP Trunk - Field Definitions
These fields apply if you selected Verizon SIP Trunk in Step 1 - Select Scenario.
Border Element Server
Panel | ||||
---|---|---|---|---|
| ||||
The FQDN or IP address of the Remote Peer service provider. |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
The IP protocol to use for sending and receiving SIP messages between SBC and the Border Element Server. This value is fixed at UDP. |
Port Number
Panel | ||||
---|---|---|---|---|
| ||||
The SIP Server Port number used for sending and receiving SIP messages between SBC and the Border Element Server. |
Teams Connection Type
Panel | ||||
---|---|---|---|---|
| ||||
The Teams connection type used for the network. Valid selections:
| ||||
| ||||
The Teams connection type used for the network. Valid selections:
|
Signaling/Media Source IP (Microsoft Teams Direct Routing)
Panel | ||||
---|---|---|---|---|
| ||||
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. |
...
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| This field is available for ||||||||
Spacevars | 0 | series5|||||||
only with a Standalone Direct Connection. 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. |
Outbound NAT Traversal
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.NOTE: This field is not applicable to
|
Public IP Address
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. |
Apply ACL
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 |
Server Pool Host 2
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 2: sip2.pstnhub.microsoft.com |
Server Pool Host 3
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 3: sip3.pstnhub.microsoft.com |
Federated FQDN
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc -environments |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
Port
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for the port used for TLS: 5061 |
Twilio SIP Trunk - Field Definitions
These fields apply if you selected Twilio SIP Trunk in Step 1 - Select Scenario.
...
Border Element Server
Panel |
---|
The FQDN or IP address of the Remote Peer service provider. |
Protocol
Panel |
---|
The IP protocol used for sending and receiving SIP messages between the SBC and the Border Element Server. Valid entries: UDP or TCP. |
Port Number
Panel |
---|
The port number for the SIP server used to send and receive SIP messages between the SBC and the Border Element Server. |
Use Secondary Border Element Server
Panel |
---|
Enables or disables the secondary Remote Peer service provider configured. |
...
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
Port
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for the port used for TLS: 5061 |
Verizon SIP Trunk - Field Definitions
These fields apply if you selected Verizon SIP Trunk in Step 1 - Select Scenario.
Border Element Server
Panel | ||||
---|---|---|---|---|
| ||||
The FQDN or IP address of the Remote Peer service provider. |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
The IP protocol to use for sending and receiving SIP messages between SBC and the Border Element Server. This value is fixed at UDP |
Panel |
---|
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. |
Protocol
Panel |
---|
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. |
Port Number
Panel | ||||
---|---|---|---|---|
| ||||
The SIP Server Port Number is number used for sending and receiving SIP messages between SBC and the Secondary Border Element server. This field is available only when Use Secondary Border Element Server is Enabled.Server. |
Teams Connection Type
Panel | ||||
---|---|---|---|---|
| ||||
The Teams connection type used for the network. Valid selections:
|
Signaling/Media Source IP (Microsoft Teams Direct Routing)
Panel | ||||
---|---|---|---|---|
| ||||
Click the drop-down arrow to select Select the external (Internet-facing) IP address for the server of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media. |
Static Host FQDN/IP[;port]
Panel | ||||
---|---|---|---|---|
| ||||
The SBC inserts the configured FQDN in the requests and responses sent toward Microsoft Teams. |
Outbound NAT IP
Microsoft Teams can then reach the SBC successfully based on the configured FQDN. |
Outbound NAT Traversal
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. |
Teams Connection Type
Panel | ||||
---|---|---|---|---|
| ||||
The Teams connection type used for the network. Valid selections:
|
Signaling/Media Source IP (Microsoft Teams Direct Routing)
Panel | ||||
---|---|---|---|---|
| ||||
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. |
...
Public IP Address
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. |
...
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
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. |
Server Pool Host 1
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 1: sip.pstnhub.microsoft.com |
Server Pool Host 2
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. |
...
Hard-coded FQDN for the location of the server list for Server Pool Host 2: sip2.pstnhub.microsoft.com |
Server Pool Host 3
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 3: sip3.pstnhub.microsoft.com |
Federated FQDN
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments 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. |
Protocol
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for protocol used with federated FQDN: TLS |
Port
Panel | ||||
---|---|---|---|---|
| ||||
Hard-coded value for the port used for TLS: 5061 |
Pagebreak |
---|
Step 3 - Confirm and Submit Configuration
...
This example displays a SIP Trunk↔ Microsoft Teams with an Other SIP Trunk type.
Pagebreak |
---|
Anchor | top | top