skype for business cloud connector edition...

Skype for Business Cloud Connector Edition – CloudConnector.ini configuration settingsVersion 1.4.1, Published 08/23/2016

For each PSTN site you plan to deploy, you will need to gather the following information before you begin the deployment. You will need to provide this information when you update the CloudConnector.ini file. For convenience, you can print this document and use the table for reference while updating the CloudConnector.ini file.

When configuring gateway information, remember the following:

• If you only have one gateway, remove the section in the .ini file for the second gateway. If there are more than two gateways, follow the existing format to add new ones.

• Make sure the IP address and the port of the gateway(s) are correct. • To support PSTN gateway-level HA, keep the secondary gateway or add additional gateways.

(Optional) To restrict the outbound call numbers, update the LocalRoute value.

Site parameters Description Notes

Virtual machine domain name Domain name for the internal components of Cloud Connector. This domain should be different from the production domain. The name can be the same across all instances of Cloud Connectors.

Name in .ini file: “VirtualMachineDomain”

.local domain is preferred.

1


Cloud Connector domain controller name Name of the domain controller.

Name in .ini file: “ServerName”

Must be 15 characters or less. Enter Netbios name only.

Cloud Connector domain controller IP/subnet mask

IP address of the domain controller.

Name in .ini file: “IP”

O365 Online service FQDNs Should be the default in most cases for the world-wide O365 instance.

Name in .ini file: “OnlineSipFederationFqdn”

SiteName Skype for Business site name; for example, Seattle.

Name in .ini file: “SiteName”

For Release 1.4.1, site name must be different for each site and the name must match the PSTN site defined in Office 365.

HardwareType

Release 1.4.1 only

Type of hardware. The default value is Normal. You can also set to Minimum.

Country Code Country Code for Dialing.

Name in .ini file: “CountryCode”

2


City City (Optional).

Name in .ini file: “City”

State State (Optional).

Name in .ini file: “State”

Base VM IP address The IP address of the temporary base VM that will be used to create the VHDX for all Cloud Connector virtual machines. This IP should be in the same perimeter corporate network subnet defined in the next step and requires Internet access. Be sure to define the corporate default gateway and the DNS that is routable to the internet.

Name in .ini file: “BaseVMIP”

WSUSServer

WSUSStatusServer

Release 1.4.1 only

The address of the Windows Server Update Services (WSUS)—an intranet server to host updates from Microsoft Update.

You can leave blank if WSUS is not needed.

3


Subnet mask for internal network Cloud Connector configures an IP network for internal communication between Cloud Connector components. Edge also should be connected to another subnet which allows Internet connectivity.

Name in .ini file: “CorpnetIPPrefixLength” under “Parameters for a pool of VM network”

Subnet mask for external network For the external network of the Edge component.

Name in .ini file: “InternetIPPrefix” under “Parameters for a pool of VM network”

Switch name for internal network Name for switch that will be used for the internal Cloud Connector network.

In most cases the default suggested value can be used.

Name in .ini file: “CorpnetSwitchName” under “Parameters for a pool of VM network

Switch name for external network Name for switch that will be used for the external Cloud Connector network.


Name in .ini file: “InternetSwitchName” under “Parameters for a pool of VM network

4


Default Gateway for internal network This gateway should provide access to the Internet (Internet also requires setting the DNS server) and will be configured on internal interfaces of Cloud Connector components.

Name in .ini file: “CorpnetDefaultGateway” under “Parameters for a pool of VM network

Default Gateway for external interface of Edge component

Will be configured on external interface of Edge component.

Name in .ini file: “InternetDefaultGateway” under “Parameters for a pool of VM network

DNS server for internal network Will be configured on internal interface of temporary VM. Should provide name resolution for Internet names. Without providing a DNS server, internet connection will fail and deployment will not finish.

Name in .ini file: “CorpnetDNSIPAddress” under “Parameters for a pool of VM network

DNS Server for external interface of Edge component

Will be configured on external interface of Edge.

Name in .ini file: “InternetDNSIPAddress” under “Parameters for a pool of VM network

5


Management switch name Management switch is a temporary switch that will be created automatically, and that will be used for configuration of Cloud Connector during the deployment. It will be disconnected automatically after the deployment. It should be a different subnet from any other networks used in Cloud Connector.


Name in .ini file: “ManagementSwitchName” under “Parameters for a pool of VM network

Management subnet address/subnet mask Management subnet is a temporary subnet that will be created automatically, and that will be used for configuration of Cloud Connector during the deployment. It will be removed automatically after the deployment. It should be a different subnet from any other networks used in Cloud Connector.

Names in .ini file: “ManagementIPPrefix” and “ManagementIPPrefixLength” under “Parameters for a pool of VM network

6


Central Management Store (CMS) Machine Single FQDN used for Central Management Store (CMS). The AD Domain name will be used to generate the FQDN.

Name in .ini file: “ServerName” under “Parameters for Primary Central Management Service


(CMS Pool Name = Server Name)

CMS Machine IP address IP address for CMS Server (internal in perimeter network).

Name in INI file: “IP” under “Parameters for Primary Central Management Service

File Share Name File Share Name to be created on CMS server for Skype for Business replication data (for example, CmsFileStore).


Name in .ini file: “CmsFileStore” under “Parameters for Primary Central Management Service

Mediation component Pool Name Pool Name of Mediation component. Enter Netbios name only. The AD Domain name will be used to generate the FQDN.

Name in .ini file: “PoolName” under “Parameters for a pool of Mediation Servers”


7


Mediation component name Component Name of Mediation component 1. Enter Netbios name only. The AD Domain name will be used to generate the FQDN.

Name in .ini file: “ServerName” under “Parameters for a pool of Mediation Servers”


Mediation component Machine IP address Internal Corpnet IP for Mediation component (internal in perimeter network).

Name in .ini file: “IP” under “Parameters for a pool of Mediation Servers”

Edge pool internal name Pool Name of Edge component. Enter Netbios name only. The AD Domain name will be used to generate the FQDN.

Name in .ini file: “InternalPoolName” under “Parameters for a pool of Edge Servers”


Edge Server internal name Component Name of Edge component. Enter Netbios name only. The AD Domain name will be used to generate the FQDN.

Name in .ini file: “InternalServerName” under “Parameters for a pool of Edge Servers”


8


Edge server internal IP Internal perimeter network IP of Edge component to communicate with other components of Cloud Connector.

Name in .ini file: “InternalServerIPs” under “Parameters for a pool of Edge Servers”

Access Pool External Name Name of Access Edge; for example, AP. This name must match the name provided for the SSL certificate. Enter Netbios name only. The SIP Domain name will be used to generate the FQDN. One external pool name will be used for all Edge components in the pool. One Edge Access pool is required per PSTN site.

Name in .ini file: “ExternalSIPPoolName” under “Parameters for a pool of Edge Servers”


“sip” is reserved and therefore cannot be used as the name.

The generated FQDN name must match the name provided for the SSL certificate.

External IP of Access Edge External IP of Edge component – either Public IP if no NAT is available, or translated IP (please specify both addresses if mapped).

Name in .ini file: “ExternalSIPIPs” under “Parameters for a pool of Edge Servers”

9


Media Relay name Name of Audio Video Media Relay Edge; for example, MR. One external pool name will be used for all Edge components in a pool. One Edge Media Relay pool is required per PSTN site.

Name in .ini file: “ExternalMRFQDNPoolName” under “Parameters for a pool of Edge Servers”


External IP of Media Relay Edge Currently only one IP is supported, so this will be the same IP as Access Edge, either public or mapped IP (please specify both addresses if mapped). Can be the same address as Edge component External IP of Access Edge. Note if Edge is behind NAT, you also need to specify the value for the next parameter.

Name in .ini file: “ExternalMRIPs” under “Parameters for a pool of Edge Servers”

External IP of Media Relay Edge (if Edge is behind NAT)

If your Edge is behind NAT you also need to specify the public address of the NAT device.

Name in .ini file: “ExternalMRPublicIPs” under “Parameters for a pool of Edge Servers”

Voice Gateway 1 Make and Model Specify the make and model of the SBC/Voice gateway. Note that you can connect a device or SIP trunk from the list of tested devices at http://technet.microsoft.com/UCOIP.

10

http://technet.microsoft.com/UCOIP


Voice Gateway 2 Make and Model (copy this row if you have more than 2 gateways)

Specify the make and model of Voice gateway. Note that you can connect a device from the list of tested devices at http://technet.microsoft.com/UCOIP.

Voice Gateway 1 Name Used to generate the machine FQDN with AD Domain. Required if TLS will be used between the Mediation component and Voice Gateway. If you do not plan to use FQDN—for example, TLS is not required or Voice Gateway doesn’t support connection using FQDN (only IP)—please specify.

Voice Gateway 2 Name (copy this row if you have more than 2 gateways)

Used to generate the machine FQDN with AD Domain. Required if TLS will be used between Mediation component and Voice Gateway. If you do not plan to use FQDN—for example, TLS is not required or Voice Gateway doesn’t support connection using FQDN (only IP)—please specify.

Voice Gateway 1 IP Address IP Address of Voice Gateway.

Voice Gateway 2 IP Address (copy this row if you have more than 2 gateways)

IP Address of Voice Gateway.

Voice Gateway 1 Port # (copy this row if you have more than 2 gateways)

Port that the Voice Gateway SIP trunk will listen on, e.g. 5060.

Voice Gateway 2 Port # Port that the Voice Gateway SIP trunk will listen on, e.g. 5060.

11

http://technet.microsoft.com/UCOIP


Voice Gateway 1 Protocol for SIP Traffic TCP or TLS.

Voice Gateway 2 Protocol for SIP Traffic (copy this row if you have more than 2 gateways)

TCP or TLS.

External Media port range for traffic to and from Edge component

TCP/UDP port range for media traffic to and from external interface of edge. Must always start from 50 000. Refer to “Ports and Protocols” for more information.

50000 - 59 999

Media port range to communicate to/from the Mediation component via the internal firewall

UDP port range that the Mediation component will use to communicate to clients and gateways (recommendation 4 ports per call).

Media port range to communicate to/from Skype for Business client via internal firewall

For planning purposes, cannot be changed. Ports need to be opened in the internal firewall to communicate between Skype for Business clients within the internal network and with the Mediation component.

50 000- 50 019

Public Certificate password Must be provided in the script.

Safe Mode Administrator Password Safe mode administrator password for internal CC domain.

Cloud Connector Domain Administrator password

Password for Cloud Connector Domain Administrator (different from your production domain). User name is Administrator. You cannot change the user name.

12


Virtual Machines Administrator Password Will be used to configure management network during the deployment.

User name is Administrator. You cannot change the user name.

Enable REFER support This will define whether SIP REFER support is enabled or disabled on the Trunk Configuration to your IP/PBX. The default value is True. If your IP/PBX Gateway supports REFER support, please leave this as True. If it does not, this value needs to be changed to False. If you are not sure if your gateway supports REFER, please reference Microsoft Unified Communications Open Interoperability Program for Qualified IP-PBXs & Gateways.

Forward PAI

Release 1.4.1 only

Determines whether the PAI (P-Asserted-Identity) header field is forwarded from the Mediation Server to the gateways.

The value can be True or False. The default value is True.

13

https://technet.microsoft.com/en-us/office/dn788945



skype for business cloud connector edition...

Documents