Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Running Connectivity Check

To check connectivity required for services and ports used with CCE and Teams, complete the following steps:

  1. In the WebUI, click the Diagnostics tab.
  2. In the left navigation pane, click Teams Direct Routing > Connectivity Check.


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


    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_Check_Results


  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

Specify the values for fields to specify the services for which Connectivity Check will verify port readiness.

Server Type

Panel
bgColor#FAFAFA
borderStylenone
The Service for which connectivity requires checking. Valid options: DNS (UDP)DNS (TCP)NTP (UDP); and SIP (TCP).

Destination

Panel
bgColor#FAFAFA
borderStylenone

The FQDN that is the destination for a service. The Destination field displays only for DNS Service Types.

Primary Server

Panel
bgColor#FAFAFA
borderStylenone

IP address of the primary server used with a service.

Info

For CCE, Connectivity Check uses the primary server only to perform checks for the SIP/MTLS service.

Secondary Server

Panel
bgColor#FAFAFA
borderStylenone

IP address of the secondary server used with a service. For CCE, the secondary server is not used for checking connectivity for SIP services. 

Third Server

Panel
bgColor#FAFAFA
borderStylenone

IP address of the third server used with a service; the Third Server field displays only for SIP (TCP). For CCE, the third server is not used for checking connectivity for SIP services.

Destination Port

Panel
bgColor#FAFAFA
borderStylenone
Port used to access the service's destination

Connectivity Check - Results
Anchor
Connectivity_Check_Results
Connectivity_Check_Results

The following table describes the services for which Connectivity Check verifies port readiness and the format for results.


Div
classpdf6pttext


Connectivity Check Results

Service and ProtocolPort
CCE
Teams
Direct
Routing
DescriptionConnectivity Check Results
Inbound
SIP/MTLS (TCP)5061
(tick)Image Removed

Handles signaling for voice communications
STUN (TCP)443
(tick)Image Removed

STUN/TURN negotiation of candidates
STUN (UDP)3478
(tick)Image Removed

Determines the version of the Edge Server with which the
Skype server is communicating

SIP/TLS (TCP)5061
(tick)Image Removed

Image Added

Handles signaling for voice communications; primary and secondary server IP addresses are hard-coded.
RTP (UDP)16384 - 17584
(tick)Image Removed(tick)Image Removed

Image Added

Handles media for voice communications
Outbound
DNS (UDP/TCP)53
(tick)Image Removed

Image Added

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
(tick)Image Removed

Image Added

Service to support timestamps in certificate usage
HTTP (TCP)80
(tick)Image Removed

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.


RTP (UDP)49152-65535
(tick)Image Removed

Image Added

Handles media for voice communications
SIP/TLS (TCP)5061
(tick)Image Removed

Image Added

Handles signaling for voice communications; primary and secondary server IP addresses are hard-coded.


For Teams Direct Routing, the SIP target can be the Microsoft SIP signaling server; Connectivity Check routes to: sip.pstnhub.microsoft.comsip2.pstnhub.microsoft.comsip3.pstnhub.microsoft.com.


STUN (TCP)443
(tick)Image Removed

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
(tick)Image Removed

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
(tick)Image Removed

Service to resolve Microsoft Signaling Server Public FQDN

For CCE, the Connectivity Check routes to sip

.

YourSbcDomain