Add_workflow_for_techpubs |
---|
AUTH2 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c857f0393d015845e3e4d4000f, userName='null'} |
---|
JIRAIDAUTH | SYM-24704 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c857f0393d015845e3e4d4000f, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a0c856ed5c6701572cb23680000b, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} |
---|
|
This section describes using Connectivity Check to verify inbound and outbound service requirements for Cloud Connector Edition (CCE) and to check connectivity for interfacing with Microsoft Teams Direct Routing.
...
- In the WebUI, click the Diagnostics tab.
In the left navigation pane, click Teams Direct Routing > Connectivity Check.
Caption |
---|
0 | Figure |
---|
1 | Running Connectivity Checks
Image Modified
- Specify the values for each field for the service for which you need to verify port readiness. For SIP/TLS (TCP), the primary and secondary server IP addresses are hard-coded (not editable).
Click Apply. Service connectivity is checked and the Connectivity Check results display. Caption |
---|
0 | Figure |
---|
1 | Example of Connectivity Check Results
Image Modified
For example, after connectivity is checked for DNS (TCP), the message: "DNS TCP check on <ip address>: Port (<ip address:port number>) is open" displays in the Connectivity Check Results. A second result using the same format displays the results for the Secondary Server specified. For more information, refer to Working with Connectivity Check - Verifying Service and Port Requirements for CCE and Teams.
- Repeat Steps 3 and 4 for each service that requires verification of port readiness.
Connectivity Checks - Field Definitions
Anchor |
---|
| Connectivity_Check_Fields |
---|
| Connectivity_Check_Fields |
---|
|
...
The following table describes the services for which Connectivity Check verifies port readiness and the format for results.
Div |
---|
| Caption |
---|
0 | Table |
---|
| 1 | Connectivity Check ResultsService and Protocol | Port | CCE | Teams Direct Routing | Description | Connectivity Check Results |
---|
Inbound |
SIP/MTLS (TCP) | 5061 | Image Modified |
|
| Handles signaling for voice communications |
|
|
STUN (TCP) | 443 | Image Modified |
|
| STUN/TURN negotiation of candidates |
|
|
STUN (UDP) | 3478 | Image Modified |
|
| Determines the version of the Edge Server with which the Skype server is communicating |
| |
| Image Modified | Handles signaling for voice communications; primary and secondary server IP addresses are hard-coded. |
|
| Image Modified | Handles media for voice communications |
|
|
Outbound |
DNS (UDP/TCP) | 53 | Image Modified | Image Modified | For the service that resolves the Public FQDN for the Microsoft Signaling Server, the Connectivity Check populates a default destination from the Host Name and Domain Name attributes in Host Information (that is, Web UI's Settings > System > Node-Level Settings). The tool opens the UDP socket and sends a homemade DNS packet. | If the remote server responds with a DNS response packet the port is reported as open. Otherwise, the port is reported as closed. |
NTP (UDP) | 123 |
|
| Image Modified | Service to support timestamps in certificate usage |
|
|
HTTP (TCP) | 80 | Image Modified |
|
| Certificate revocation check and Certificate Revocation List (CRL) retrieval The host field is filled by default with the FQDN found in the SBC certificate, under the attribute: CRL Distribution Point. |
|
| Image Modified | Handles media for voice communications |
| |
| Image Modified | Handles signaling for voice communications; primary and secondary server IP addresses are hard-coded. |
|
|
STUN (TCP) | 443 | Image Modified |
|
| For the service handling STUN/TURN negotiation of candidates, the Connectivity Check opens a UDP socket and sends a homemade STUN packet. | If the remote server does not respond with a STUN error packet, the port is reported as closed. The remote peer is the Microsoft Cloud Edge Server and the STUN protocol determines the Public IP address. |
STUN (UDP) | 3748 | Image Modified |
|
| For the STUN service that determines the version of the Edge Server with which the Skype server is communicating, Connectivity Check populates a default destination from from the Host Name and Domain Name attributes in Host Information (that is, Web UI's Settings > System > Node-Level Settings). The tool opens the UDP socket and sends a homemade DNS packet. | If the remote server responds with a DNS response packet the port is reported as open. Otherwise the port is reported as closed. |
SIP/MTLS (TCP) | 5061 | Image Modified |
|
| Service to resolve Microsoft Signaling Server Public FQDN For CCE, the Connectivity Check routes to sip.YourSbcDomain |
|
---|