Deploy multiple sites in Cloud Connector
Important
Cloud Connector Edition will retire July 31, 2021 along with Skype for Business Online. Once your organization has upgraded to Teams, learn how to connect your on-premises telephony network to Teams using Direct Routing.
Learn about deploying multiple PSTN sites in Cloud Connector Edition.
This section describes how to deploy multiple Public Switched Telephone Network (PSTN) sites. Sites are deployed one at a time using the same steps as deploying a single site. This topic describes the considerations for and differences between sites in a multiple site deployment.
Multiple Public Switched Telephone Network (PSTN) Sites
The following shows an example configuration to deploy Skype for Business Cloud Connector Edition for different PSTN sites. Make sure your configuration settings are correct before you start a deployment.
PSTN Site 1
[Common]
SiteName=Site1
[EdgeServer]
InternalMachineName= cc-edge1
InternalPoolName=cc-edgepool
InternalMachineIPs=192.168.0.241
ExternalSIPPoolName=access1
ExternalSIPIPs=192.168.1.4
ExternalMRFQDNPoolName=mr1
ExternalMRIPs=192.168.1.4
ExternalMRPublicIPs=23.99.115.35
PSTN Site 2
[Common]
SiteName=Site2
[EdgeServer]
InternalMachineName= cc-edge2
InternalPoolName=cc-edgepool
InternalMachineIPs=192.168.0.242
ExternalSIPPoolName=access2
ExternalSIPIPs=192.168.1.5
ExternalMRFQDNPoolName=mr2
ExternalMRIPs=192.168.1.5
ExternalMRPublicIPs=104.42.226.134
For each PSTN site that you want to add, follow the steps in Deploy a single site in Cloud Connector.
Important
The shared folder for preparing High Availability (HA) is per PSTN site. The shared folder must be different between PSTN sites. Do not use the same shared folder for multiple sites.>
Single site with High Availability (HA) compared to multi-site deployments
The following table lists the differences between single site with HA support and a multiple site deployment.
| Category | Item | Single-Site with HA | Multi-Site |
|---|---|---|---|
| Configure |
Appliance Host Name |
Different across appliances |
Different across PSTN sites |
| Setup |
Shared folder |
Requires the same shared folder across appliances |
Requires a different shared folder across appliances |
| Configure |
VirtualMachineDomain |
Requires the same domain across appliances |
Requires the same domain across PSTN sites |
| Configure |
SIPDomains |
Domain names and order should be the same across appliances |
Domain names and order should be the same across PSTN sites |
| Configure |
Site name |
Same Site Name across appliances |
Different Site Name across PSTN sites |
| Configure |
Server names |
Different across appliances |
Different across PSTN sites |
| Configure |
Internal pool FQDNs |
Same across appliances |
Same across PSTN sites |
| Configure |
Internal IPs |
Different across appliances |
Different across PSTN sites |
| Configure |
External FQDN |
Same across appliances |
Different across PSTN sites |
| Configure |
External IPs |
Different across appliances |
Different across PSTN sites |
| Configure |
PSTN GW settings |
Same across appliances |
Different across PSTN sites |
| Configure |
DNS record |
Add records with the same External Access FQDNs and different IP addresses |
Add records with different External Access FQDNs and different IP addresses |
| Setup |
Hybrid tenant |
Set HybridPSTNSite Set PeerDestination for fallback |
Set HybridPSTNSite Set PeerDestination for fallback |
| Setup |
Gateway |
MS GW M:N mapping in this site |
PSTN gateway(s) in each PSTN site should only connect to the Mediation Server(s) in the same site |
| Setup |
User |
Set UserPSTNSettings |
Set UserPSTNSettings |