Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

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

...

Microsoft Teams Direct Routing Configuration

Consult the Microsoft documentation for the Direct Routing interface configuration guidelines, including the RFC standards and the syntax of SIP messages.

...

Caption
0Table
1SBC Edge Requirements


RequirementDetails
SBC Behind the NAT*

Public IP address of NAT device and Private IP address of the SBC.

SBC with Public IPPublic IP address of SBC is required.
Network Address Translation (NAT)* ConfigurationRequired for deployment of an SBC behind a NAT.
Public FQDN The Public FQDN must point to the Public IP Address.
Public certificate associated with the Public FQDN

Certificate must be issued by one of the supported certification authorities (CAs). Wildcard certificates are supported.

Static IP Address

Required for deployment of an SBC behind a NAT, the Public IP address on the NAT must be static.

*NAT translates a public IP address to a Private IP address.

...


Anchor
nomedia
nomedia
Basic Firewall Settings for All Call Flows

Inbound Public (Internet to SBC)

  • SIP TLS: TCP 5061*

  • Media for SBC 1000: UDP 16384-17584**
  • Media for SBC 2000: UDP 16384-19384*

Outbound Public (SBC to Internet)

  • DNS: TCP 53

  • DNS: UDP 53

  • NTP: UDP 123

  • SIP TLS: TCP 5061

  • Media: UDP 49152-53247

Public Access Information

The tables below represent ACL (Access Control List) examples that protect the SBC Edge; these attributes are automatically provisioned if the Teams-related Easy Configuration wizards are used (applies to the greenfield deployment scenario only).

...

Info

The Teams Client IP address cannot be predicted. As a result, allow Any IP (0.0.0.0/0).

Inbound Public (Internet to SBC) 

Media for SBC 1000: UDP 17586-21186**

Media for SBC 2000: UDP 19386-28386**

Outbound Public (SBC to Internet)

Media: UDP 50000-50019

If the device that handles the NAT between the Teams Client and SBC Public IP is performing PAT (Port Address Translation), verify that this device has the source port range of the Teams Client media or open all the ports from 1024 to 65535.

...

For SBC not using NAT, there must be access between the firewall and the SBC's Public IP.

Public Access

The tables below represent ACL (Access Control List) examples that protect the SBC Edge; these ACL attributes are automatically provisioned if the Teams-related Easy Configuration wizards are used (applies to the greenfield deployment scenario only).

...