Skype for Business cloud connector deployment



Skype for Business cloud connector deploymentShankar Paulrajcenter850008549640September 8, 2017 1000000September 8, 2017 VersionDateAuthorChange Description1.021 Sep 2016Shankar PaulrajInitial draft1.110 Oct 2016Shankar PaulrajInclude configuration for CLID manipulation, Call Transfer & MOH.1.217 Aug 2017Shankar PaulrajUpdate procedure for CCE 2.0.11.308 Sep 2017Shankar PaulrajAmend Media BypassContents TOC \o "1-3" \h \z \u Overview PAGEREF _Toc492623550 \h 2Prepare your environment for Cloud Connector PAGEREF _Toc492623551 \h 3IP Address Requirements PAGEREF _Toc492623552 \h 3External Firewall Requirements PAGEREF _Toc492623553 \h 4Outgoing Traffic from Edge PAGEREF _Toc492623554 \h 4Incoming Traffic to Edge PAGEREF _Toc492623555 \h 4Internal Firewall Requirements PAGEREF _Toc492623556 \h 5Outgoing Traffic from Mediation Server PAGEREF _Toc492623557 \h 5Incoming Traffic to Mediation Server PAGEREF _Toc492623558 \h 5Edge Certificate Requirements PAGEREF _Toc492623559 \h 5Download CCE Setup File on Host Machine PAGEREF _Toc492623560 \h 7Install CCE Setup on Host Machine PAGEREF _Toc492623561 \h 7Verify Installation Directory PAGEREF _Toc492623562 \h 8Setup external certificate path on Host Machine PAGEREF _Toc492623563 \h 8Create virtual switches in Hyper-V Manager PAGEREF _Toc492623564 \h 9Update the CloudConnector.ini file PAGEREF _Toc492623565 \h 9Download Sample ini file PAGEREF _Toc492623566 \h 21Download the bits to the Site Directory PAGEREF _Toc492623567 \h 21Prepare Base Virtual Disk from Windows Server 2012R2 ISO file PAGEREF _Toc492623568 \h 22Set the PowerShell Execution policy to RemoteSigned PAGEREF _Toc492623569 \h 24Change local Group Policy to not forcefully unload the user registry at user logoff PAGEREF _Toc492623570 \h 24Download the Skype for Business Online module for PowerShell PAGEREF _Toc492623571 \h 24Deploy a single site in Cloud Connector PAGEREF _Toc492623572 \h 25Register the appliance PAGEREF _Toc492623573 \h 25Install appliance PAGEREF _Toc492623574 \h 25Configure Cloud Connector integration with your Office 365 tenant PAGEREF _Toc492623575 \h 27Update Public DNS for your domain PAGEREF _Toc492623576 \h 27Setup Hybrid and Configure O365 PAGEREF _Toc492623577 \h 27Test Client Sign-In and PSTN Dial out PAGEREF _Toc492623578 \h 28Modify the configuration of an existing Cloud Connector deployment PAGEREF _Toc492623579 \h 30Additional Configuration PAGEREF _Toc492623580 \h 31Remove Country code from SFB Client CLID PAGEREF _Toc492623581 \h 31Disable REFER support PAGEREF _Toc492623582 \h 32Enable Client Music on Hold PAGEREF _Toc492623583 \h 32Enable Media bypass PAGEREF _Toc492623584 \h 32Check if the Media bypass web service is reachable on CCE Mediation server. PAGEREF _Toc492623585 \h 33Configure Tenant for Media Bypass PAGEREF _Toc492623586 \h 33Verify if the changes made on SfB online is synchronized to CCE. PAGEREF _Toc492623587 \h 33Verify if SfB Client downloaded the configuration. PAGEREF _Toc492623588 \h 35Reference PAGEREF _Toc492623589 \h 35OverviewThis guides covers steps involved in downloading and installing Skype for Business Cloud Connector Edition 2.0.1.Microsoft TechNet link was used as reference throughout the deployment.To perform a successful deployment, do spend more time on planning and modifying the configuration file “CloudConnector.ini” with accurate values.The topology assumed here is single instance of Cloud Connector within a single PSTN site.Typically, CCE is deployed in DMZ, the only server that talks to customer LAN is mediation server.High-level Requirements1 x Host Server with Windows 2012R2 Data Center Edition1 x PSTN Gateway (makes no sense to test the CCE without an On-Premise PSTN Gateway)1 x Public SSL Cert1 x Public IP for the Edge Access1 x Working O365 Tenant with E5 LicensePrepare your environment for Cloud ConnectorIP Address RequirementsPlan the IP address for your environment.Host IP Address GatewayRemarksAD172.16.40.161/24172.16.40.1SfB Corp LANCMSServer172.16.40.162/24172.16.40.1SfB Corp LANMediationServer172.16.40.163/24172.16.40.1SfB Corp LANEdgeServer172.16.40.164/24NASfB Corp LAN172.16.50.118/24172.16.50.1SfB Ext LANNAT to <public IP>One Public IP Needed for Edge External InterfaceGateway1172.16.100.11NAPSTN Gateway listening on Port: 5068External Firewall RequirementsNote: Minimum Ports used, refer TechNet for recommended option.Outgoing Traffic from EdgeSource IPDestination IPProtocolDestination PortPort DescriptionCCE Edge External interface IP172.16.50.118SFB Online IPs and FQDNs *.TCP5061CCE to Cloud SIP TrafficCCE Edge External interface IP172.16.50.118 on Public CATCP80FQDN of your cert providerCCE Edge External interface IP172.16.50.118External DNS (8.8.8.8)UDP53DNS ResolutionCCE Edge External interface IP172.16.50.118External DNS (8.8.8.8)TCP53DNS ResolutionCCE Edge External interface IP172.16.50.118SFB Online IPs and FQDNs *.TCP443For Audio and Video Session with SFB OnlineCCE Edge External interface IP172.16.50.118SFB Online IPs and FQDNs *.UDP3478For Audio and Video Session with SFB OnlineIncoming Traffic to EdgeSource IPDestination IPProtocolDestination PortPort DescriptionSFB Online IPs and FQDNs *.CCE Edge External interface IP172.16.50.118TCP5061Cloud to CCE SIP TrafficSFB Online IPs and FQDNs *.CCE Edge External interface IP172.16.50.118TCP443For Audio and Video Session with SFB OnlineSFB Online IPs and FQDNs *.CCE Edge External interface IP172.16.50.118UDP3478For Audio and Video Session with SFB OnlineInternal Firewall RequirementsOutgoing Traffic from Mediation ServerSourceTargetProtocolDestination PortPort DescriptionCCE Mediation Server172.16.40.163Client SubnetTCP50,000-50,019Media port rangeCCE Mediation Server172.16.40.163Client SubnetUDP50,000-50,019Media port rangeIncoming Traffic to Mediation ServerClient SubnetCCE Mediation Server172.16.40.163TCP49,152- 57, 500Media port rangeClient SubnetCCE Mediation Server172.16.40.163UDP49,152- 57, 500Media port rangeEdge Certificate RequirementsOptionDescriptionNotesSingle Site & Single SIP domain SNProvide the SN for your certificateaccessedgepool.SANProvides the SAN for your certificatesip., acessedgepool.From any machine, run DigiCert Certificate Utility and create CSR.Copy CSR and generate Cert using public CA.Obtain & Install the certificate on the machine from which CSR was created.Export the certificate with private key and take note of the password.Download CCE Setup File on Host Machine CCE Setup on Host MachineVerify Installation DirectorySetup external certificate path on Host MachineCopy the certificate created previously to the Host machine folder C:/CertsSet the certificate path for CCESet-CcExternalCertificateFilePath -Path <Full path to External certificate, including file name> -Target EdgeServerCreate virtual switches in Hyper-V ManagerOpen Hyper-V Manager > Virtual Switch Manager, and select New Virtual Switch Manager.Create an External virtual switch and bind it to the physical network adapter that is connected to your internal network domain.Select Allow management operating system to share this network adapter for this virtual switch.Create an External virtual switch and bind it to the physical network adapter that is connected to the Internet and has a public IP address assigned.Select Allow management operating system to share this network adapter for this virtual switch.Set the name of the switch that is connected to your perimeter network to your internal network domain to SfB CCE Corpnet Switch.Set the name of the switch that connects your perimeter network to the internet SfB CCE Internet Switch.Update the CloudConnector.ini fileSite parametersDescriptionNotesSIP DomainsDomain(s) registered on O365.Support multiple domains separated by space. First domain is the default Virtual machine domain nameDomain name for the internal components of Cloud Connector. This domain must be different from the production domain. The name must be the same across all Cloud Connector appliances.Name in .ini file: “VirtualMachineDomain”sfbhybridtest.localCloud Connector domain controller nameName of the domain controller.Name in .ini file: “ServerName”ADCloud Connector domain controller IP/subnet maskIP address of the domain controller.Name in .ini file: “IP”172.16.40.161O365 Online service FQDNsMust be the default in most cases for the world-wide O365 instance.Name in .ini file: “OnlineSipFederationFqdn”sipfed.online.SiteNameSkype for Business site name; for example, Seattle.Name in .ini file: “SiteName”For Release 1.4.1 and later, site name must be different for each site and the name must match the PSTN site, if it exists, defined in Office 365. Note that PSTN sites will automatically be created when registering the first appliance in a site.RadianceLABHardwareTypeRelease 1.4.1 and laterType of hardware. The default value is Normal. You can also set to Minimum.MinimumCountry CodeCountry Code for Dialing.Name in .ini file: “CountryCode”SGCityCity (Optional).Name in .ini file: “City”SGStateState (Optional).Name in .ini file: “State”SGBase VM IP addressThe IP address of the temporary base VM that will be used to create the VHDX for all Cloud Connector virtual machines. This IP must 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”Base VM Requires accesss to Internet.WSUSServerRelease 1.4.1 and laterThe 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.?Subnet mask for internal networkCloud Connector configures an IP network for internal communication between Cloud Connector components. Edge also must be connected to another subnet which allows Internet connectivity.Name in .ini file: “CorpnetIPPrefixLength” under “Parameters for a pool of VM network”24Subnet mask for external networkFor the external network of the Edge component.Name in .ini file: “InternetIPPrefix” under “Parameters for a pool of VM network”24Switch name for internal networkName 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 networkSfB CCE Corpnet SwitchSwitch name for external networkName for switch that will be used for the external Cloud Connector network.In most cases the default suggested value can be used.Name in .ini file: “InternetSwitchName” under “Parameters for a pool of VM networkSfB CCE Internet SwitchDefault Gateway for internal networkThis gateway must 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 network172.16.40.1Default Gateway for external interface of Edge componentWill be configured on external interface of Edge component.Name in .ini file: “InternetDefaultGateway” under “Parameters for a pool of VM network172.16.50.1DNS server for internal networkWill be configured on internal interface of temporary VM. Must 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 network172.16.50.254DNS Server for external interface of Edge componentWill be configured on external interface of Edge.Name in .ini file: “InternetDNSIPAddress” under “Parameters for a pool of VM network8.8.8.8Management switch nameManagement 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 must be a different subnet from any other networks used in Cloud Connector.In most cases the default suggested value can be used.Name in .ini file: “ManagementSwitchName” under “Parameters for a pool of VM networkSfB CCE Management SwitchManagement subnet address/subnet maskManagement 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 must 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 network192.168.213.024Central Management Store (CMS) MachineSingle 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 ServiceCMSServerCMS Machine IP addressIP address for CMS Server (internal in perimeter network).Name in INI file: “IP” under “Parameters for Primary Central Management Service172.16.40.162File Share NameFile Share Name to be created on CMS server for Skype for Business replication data (for example, CmsFileStore).In most cases the default suggested value can be used.Name in .ini file: “CmsFileStore” under “Parameters for Primary Central Management ServiceCmsFileStoreMediation component Pool NamePool 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”mspoolMediation component nameComponent 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”MedServerMediation component Machine IP addressInternal Corpnet IP for Mediation component (internal in perimeter network).Name in .ini file: “IP” under “Parameters for a pool of Mediation Servers”172.16.40.163Edge pool internal namePool 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”edgepoolEdge Server internal nameComponent 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”EdgeServerEdge server internal IPInternal 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”172.16.40.164Access Pool External NameName 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”accessedgepool“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 EdgeExternal 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”172.16.50.118Media Relay nameName 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”mrExternal IP of Media Relay EdgeCurrently 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”172.16.50.118External 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”your pubic IPVoice Gateway 1 Make and ModelSpecify 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 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 Gateway 1 NameUsed 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 AddressIP Address of Voice Gateway.172.16.100.11Voice 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.5068Voice Gateway 2 Port #Port that the Voice Gateway SIP trunk will listen on, e.g. 5060.?Voice Gateway 1 Protocol for SIP TrafficTCP or TLS.TCPVoice 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 componentTCP/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 999Media port range to communicate to/from the Mediation component via the internal firewallUDP 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 firewallFor 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 019Public Certificate passwordMust be provided in the script.Passw0rdSafe Mode Administrator PasswordVersion 1.4.2 onlySafe mode administrator password for internal CC domain.?Cloud Connector Domain Administrator passwordVersion 1.4.2 onlyPassword for Cloud Connector Domain Administrator (different from your production domain). User name is Administrator. You cannot change the user name.?Virtual Machines Administrator PasswordVersion 1.4.2 onlyUsed to configure management network during the deployment.User name is Administrator. You cannot change the user name.?CABackupFileVersion 2.0 and laterUsed for saving the Certification Authority Service from the Active Directory server to a file when deploying multiple appliances in a Cloud Connector site. Be sure to use the same password for all appliances within one Cloud Connector site in order to import the CA backup file to new added appliance successfully.?CCEServiceVersion 2.0 and laterUsed for the Cloud Connector Management service; needs access to the Cloud Connector site directory. Be sure to use the same password for all appliances within one Cloud Connector site.?Office 365 Tenant AdminThe account is used by Cloud Connector to update and manage tenant settings for Cloud Connector:Version 2.0 and later: Credentials for a dedicated Office 365 account with Skype for Business Administrator rights.Versions previous to 2.0: Credentials for a dedicated Office 365 account with Global Tenant Administrator rights.?Enable REFER supportThis 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 see Qualified IP-PBXs and Gateways.TRUEEnableFastFailoverTimerVersion 2.0 and laterWith the default value “True”, if outbound calls are not answered by the gateway within 10 seconds they will be routed to the next available gateway; if there are no additional trunks then the call will be dropped automatically.However, in an organization with slow networks and gateway responses, or when the process of establishing calls takes more than 10 seconds, this could potentially result in calls being dropped unnecessarily.When placing calls to some countries, for example the UAE or Afghanistan, call establishing process can take more than 10 seconds. You will need to change the value to False if you encounter similar issues. Do not forget to change the corresponding setting on the connected SBC or GatewayTRUEForwardCallHistoryVersion 2.0 and laterThis parameter is used to turn on SIP headers that are used to report the initial caller in Simultaneous Ringing, Call Forwarding, and Call Transfer scenarios. Setting the parameter to True will turn on two SIP headers:History-InfoReferred-ByThe value can be True or False. The default value is False.FALSEForward PAIVersion 2.0 and laterPAI is a private extension to SIP that enables SIP servers to assert the identity of authenticated users. For the SIP trunk provider, PAI may be used for bill-to purposes in the event that History-Info and Referred-By headers are not present. When Forward P-Asserted-Identity is enabled in the configuration, the Mediation Server will forward PAI headers with SIP & Tel URI’s from Cloud Connector onto the SIP Trunk. The Mediation Server will forward PAI headers with tel URI’s & E.164 numbers ONLY received on the SIP trunk to Cloud Connector. The Mediation Server will also forward any Privacy headers received in either direction. If the SIP Request sent by the Mediation Server includes a Privacy header of the form - “Privacy: id” in conjunction with the PAI header, then the asserted identity should be kept private outside of the network trust domain.The value can be True or False. The default value is False.FALSEDownload Sample ini fileCopy the sample ini file from C:\Users\Administrator\CloudConnector\ApplianceRootRename the file to CloudConnector.ini and edit the file to suit your environment.Download the bits to the Site Directory>Start-CcDownloadDownload time depends on network conditions. Run the Get-CcDownloadProgress cmdlet to check the download status.Prepare Base Virtual Disk from Windows Server 2012R2 ISO fileThis step prepares a virtual hard disk (VHDX) file from the Windows Server 2012 ISO image. The VHDX will be used to create virtual machines during deployment. A temporary virtual machine (base VM) will be created and Windows Server 2012 will be installed from the ISO file. After the VM is created, some necessary components will be installed. At the end, the base VM will be generalized (sysprep) and cleaned up, leaving only the generated virtual disk file.Download the ISO file “WindowsServer2012R2.iso” on Host Server.Sample command: Convert-CcIsoToVhdx -IsoFilePath c:\Users\Administrator\Downloads\WindowsServer2012R2.iso -PauseBeforeUpdateEnsure that the VM has internet access and then type “Y”.After almost 3 long hours,Set the PowerShell Execution policy to RemoteSignedOn the Host machine ensure that execution policy is set “RemoteSigned”If it is not set to "RemoteSigned," run the following cmdlet to change it: lefttop>Set-ExecutionPolicy RemoteSignedChange local Group Policy to not forcefully unload the user registry at user logoffThe CceService account is created during the Skype for Business Cloud Connector Edition (CCE) deployment. It runs the CCE Management Service and requires permission to uninstall the cloudconnector.msi.To change the Group Policy settingOpen the Group Policy Editor by running gpedit.msc.In the Group Policy Editor, navigate to Administrative Templates > System > UserProfile > Do not forcefully unload the user registry at user logoff.Set its value to be Enabled.Download the Skype for Business Online module for PowerShellDownload and install SFB online module for PowerShell a single site in Cloud ConnectorRegister the appliance>Register-CcApplianceEnter necessary password for accounts.Install appliance>Install-CcApplianceVerify the Virtual MachinesVerify CCE status from SfB Online Admin PortalConfigure Cloud Connector integration with your Office 365 tenantUpdate Public DNS for your domainTYPE SERVICEPROTOCOLPORTTARGETNAMESRV_sip_tls443sipdir.online.@SRV_sipfederationtls_tcp5061sipfed.online.@RECORDS FOR THE EDGE SERVERTYPE HOSTNUMERIC IPAaccessedgepool<your edge public ip>Amr<your edge public ip>Setup Hybrid and Configure O365Import Module SkypeOnlineConnectorConnect to O365 TenantImport SessionSetup Hybrid Connectivity>Set-CsTenantHybridConfiguration -PeerDestination <External Access Edge FQDN> -UseOnPremDialPlan $false>Set-CsTenantFederationConfiguration -SharedSipAddressSpace $TrueConfigure Tel URI for UsersAssumption: User is configured in O365 and assigned E5 license.Set-CsUser -Identity "<User name>" -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI <tel:+phonenumber>Test Client Sign-In and PSTN Dial outMake Test CallsModify the configuration of an existing Cloud Connector deploymentFollow below procedure ONLY if there is a need to change any of the CCE settings that was configured using the INI file previously.If there is only one appliance in the site, when you want to change the configuration settings after the appliance is deployed, you can modify the CloudConnector.ini file and start the deployment again.Run the following cmdlet to uninstall all existing virtual machines on host server:>Uninstall-CcApplianceRun the following cmdlet to unregister the appliance>Unregister-CcApplianceUpdate the CloudConnector.ini file in the Appliance Directory.Modify INI file to include the changes that you may want.Run the following cmdlet to register the appliance again>Register-CcApplianceRun the following cmdlet to install Skype for Business Cloud Connector Edition:>Install-CcApplianceAdditional ConfigurationRemove Country code from SFB Client CLIDManipulate SFB Client CLID from the Mediation ServerNew-CsOutboundCallingNumberTranslationRule -Parent "site:Site1" -Name EightDigit -Description "Converts a dialed number to eight digits" -Pattern '^\+65(\d{8})$' -Translation '$1'Disable REFER supportBased on the PSTN gateway used there might be a need to disable REFER support on the trunk configuration, otherwise the call transfer feature may not function correctly.Disable REFER support from the Mediation ServerSet-CsTrunkConfiguration –Identity Site:Site1 -EnableReferSupport $falseEnable Client Music on HoldEnable MOH from Skype Online.Connect to Skype online and issue the following command.Set-CsClientPolicy -Identity Global -EnableClientMusicOnHold $trueEnable Media bypassBy default, media bypass is disabled, the rtp traffic to PSTN gateway flow through the CCE mediation server “172.16.40.163”.SfB Client IP: 172.16.160.22Below packet capture confirms the same.Check if the Media bypass web service is reachable on CCE Mediation server.Access URL from client machine.Note: In the production DNS server configure DNS A record for CCE mediation server.Configure Tenant for Media BypassConnect to SfB online using PowerShell and issue below command,Set-CsTenantHybridConfiguration -HybridConfigServiceInternalUrl $mediabypass = New-CsNetworkMediaBypassConfiguration -AlwaysBypass $true -Enabled $trueSet-CsNetworkConfiguration -MediaBypassSettings $mediabypassVerify if the changes made on SfB online is synchronized to CCE.Get-CsTenantHybridConfiguration -LocalStoreGet-CsNetworkConfiguration -LocalStoreVerify if SfB Client downloaded the configuration.Once media bypass is enabled, the rtp traffic from SfB client flow directly to the PSTN gateway.Below packet capture confirms the same.SfB Client IP: 172.16.160.213PSTN Gateway (DSP or Media Gateway): 172.16.150.254Reference ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download