The administrator needs to configure the Presence Services cluster as a trusted application pool that can be referred to in a Front End static route and a trusted application definition.
On Front End server for S4B, run Management Shell for S4B Server and on Skype for Business Front End server, run Skype for Business Server Management Shell.
Create a trusted application pool. Use the New-CsTrustedApplicationPool cmdlet to create a trusted application pool sc-8209-cl-03.avaya.com to host trusted application.
For more information, see help of the New-CsTrustedApplicationPool cmdlet.
Identity is the FQDN of the new pool and it is the Avaya Breeze® platform cluster Load Balancer FQDN.
Registrar is the FQDN of the Front End pool to which this trusted application pool belongs.
You can find the Register parameter with cmdlet Get-CsPool | Where-Object {$_.Services -match "Registrar:"}.
-Site is Site ID to which this trusted application pool belongs; use Get-CsSite cmdlet to retrieve the SiteId.
-ComputerFqdn defines the FQDN of the first Avaya Breeze® platform Security Module FQDN in the trusted application pool.
Add other Avaya Breeze® platform node to the trusted application pool for multi-nodes cluster setup. Use the New-CsTrustedApplicationComputer cmdlet to add other Avaya Breeze® platform server(s) to the trusted application pool.
-Identity is Avaya Breeze® platform Security Module FQDN of the 2nd node. (For single node cluster, skip this step).
-Pool is the trusted application pool defined in step 2.
By adding all Avaya Breeze® platform nodes to the trusted application pool, it provides load-balanced setup for the Presence/IM services from all the hosts.
Repeat this step for each node in a multi-node cluster.
Note:
When creating a trusted application pool (and trusted application computer) in this way, Skype for Business will issue a warning:
Other:
Machine xxx from the topology you are publishing was not found in Active Directory and will result in errors during Enable-CsTopology as it tries to prepare Active Directory entries for the topology machines.
This warning can be safely ignored as the Avaya Breeze® platform nodes are not domain joined in Microsoft Active Directory, and you should answer “Yes” to this warning.
Create a trusted application representing Presence Services. Use the New-CsTrustedApplication cmdlet to create a trusted application represents the Presence Services.
-ApplicationID is friendly identifier for the trusted application.
-TrustedApplicationPoolFqdn is the trusted application pool created in step 2.
Create a static route for Aura Presence/IM domain routing and associate this route with trusted application pool. Use the New-CsStaticRoute & Set-CsStaticRoutingConfiguration cmdlets to create Static Route associated with global routing table.
Set-CsStaticRoutingConfiguration -Identity global -Route @{Add=$newstaticroute}
-TLSRoute defines that the static route we are creating will use SIP TLS transport.
-Destination is the FQDN of the next hop server for routing Presence or IM messages.
In this example, the routing destination is the Avaya Breeze® platform cluster Load Balancer FQDN.
-Port is the Presence Service port for federation, default is 5063.
-MatchUri is the domain suffix used to determine if the Presence/IM message is being sent to an Aura user handle by this route. In this example, Skype client watching Aura client aura-user@bvwlab.com will use the defined static route, sending to destination at FQDN sc-8209-cl-03.avaya.com.
Note:
Microsoft Federation supports a shared domain setup, in which the Microsoft domain can be the same as Aura Presence or IM domain. In this shared domain configuration, Skype for Business will only send Presence or IM requests to Aura client which is not defined as Skype client. And Microsoft Federation also supports different domains between MS domain and Aura Presence or IM domain. If static routes for additional domains are required, re-run the two cmdlets above, substituting the -MatchUri parameter with desired Aura Presence or IM domain name.
Enable the new Topology. Use Enable-CsTopology cmdlet to enable the newly create topology.
