For additional port requirements for media bypass scenarios, see Plan for media bypass with Direct Routing Note: The firewall port requirements below assume media bypass is not enabled. If your firewall supports DNS name resolution, the FQDN resolves to all IP addresses listed above. The FQDNs, and will be resolved to one of the following IP addresses: Provide failover when connection from an SBC is established to a datacentre that is experiencing a temporary issue.Provide optimal experience (less loaded and closest to the SBC datacentre assigned by querying the first FQDN).Placing these three FQDNs in order is required to: – Tertiary FQDN – geographically maps to the third priority region.– Secondary FQDN – geographically maps to the second priority region.The IP address returned corresponds to the primary FQDN The assignment is based on performance metrics of the datacenters and geographical proximity to the SBC. When the SBC sends a request to resolve this name, the Microsoft Azure DNS servers return an IP address pointing to the primary Azure datacenter assigned to the SBC. The connection point for Direct Routing are the following three FQDNs: This is useful in environments where I may want to route some calls to existing on-premises infrastructure (call centres, analogue endpoints, other 3 rd party telephony infrastructure), but have the bulk of my organisation’s PSTN calls route via a Telstra Calling Plan (ignore “Microsoft Calling Plan” in the diagram below, in Australia it’s known as a Telstra Calling Plan): This means we now have greater flexibility in deployment options: I can choose to have some calls route via on-premises infrastructure, and other calls to route to the PSTN network direct from the cloud via Telstra Calling. The other key differentiator with Direct Routing is that I no longer need to deploy the Cloud Connector Edition virtual machines as well as an SBC to provide connectivity to the Office 365 cloud: a certified SBC is all that is required.Īnother major difference with Direct Routing is that it can be deployed side by side with Telstra Calling for Office 365 Calling Plans. However, CCE will support PSTN connectivity for Skype for Business Online only, not Microsoft Teams. Microsoft Cloud Connector edition was a great way to enable PSTN connectivity for Skype for Business Online users, particularly as native cloud calling plans are only now available in Australia. Requires on-premises infrastructure (SBC & Hyper-V Host with VMs). Cloud Connector Edition (CCE) – enables PSTN connectivity for Skype for Business Online only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |