Cisco Cub for Microsoft Groups Direct Routing (Necessary) – Loopy Networking

When setting Cisco Cub for direct rooting of Microsoft groups, there are quite a few key necessities and constructions to think about. The next is a complete chief that will help you by way of this course of.

1. Regular necessities

• Public, Web Routeable IP Deal with: Be sure to have a public IP deal with for the exterior interface.
• Non-public, inside IP deal with: Assign personal IP deal with for inside interface.
• Totally certified area title (FQDN): The dice ought to have FQDN out of your public area.
• Public certificates: Get a public certificates for Dice FQDN from Microsoft Certificates Authority. (* Certificates will work)
• DNS A Data: Create DNS A document in public DNS server for SBC FQDN mapping at public IP deal with.
• Firewall guidelines: Add guidelines of the firewall described within the part of firewall necessities.

2. Firewall necessities

2.1 SIP Signaling: IP deal with limits

The Cisco Dice Router will start a dialog with the next FQDN:

• sip.pstnhub.microsoft.com – International FQ DN
• SIP2.pstnhub.microsoft.com – Secondary FQDN
• SIP3.pstnhub.microsoft.com – Teri FQ DN

These FQDNS decide to IP addresses throughout the following subtters:

• 52.112.0/14
• 52.122.0.14

2.2 SIP Signaling: Ports

Port limits for SIP signaling are as follows:

2.3 SIP Media: IP deal with limits

The bounds of IP deal with for Media Visitors are:

• 52.112.0.0/14 (52.112.0.0 to 52.115.255.255 to IP addresses)
• 52.120.0.0/14 (52.120.0.0 to 52.123.255.255 to IP addresses)

2.4 SIP Media: Ports

Port limits for SIP Media are as follows: