Page History

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.

...

1. In the WebUI, click the Diagnostics tab.

2. In the left navigation pane, click Teams Direct Routing > Connectivity Check.
   Caption0Figure1Running Connectivity Checks

   Image Modified

   
   

3. 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).
   

   Table of Contents
   maxLevel 4 minLevel 4

4. Click Apply. Service connectivity is checked and the Connectivity Check results display. Caption0Figure1Example 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. 

   
   

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

...

 

TableConnectivity Check Results

Div
class pdf6pttext
Caption
0
	1

Service and Protocol	Port	CCE	Teams Direct Routing	Description	Connectivity Check Results
Inbound
SIP/MTLS (TCP)	5061	Image Modified

STUN (TCP)	443	Image Modified

STUN (UDP)	3478	Image Modified

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

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