The instructions in this Best Practice assume the SBC Edge node is running and connected to the WebUI.
This best practice document defines the suggested configuration for both the SBC and Skype/Lync Server in order for Third Party Presence to be published.
The example configuration items are used to configure the SBC Edge for Skype for Business (in order for Third Party Presence to be published):
A SIP Server must be configured to point to a Presence Server. A Presence Server runs on a Skype/Lync front-end pool. MTLS is required for communication between the SBC and the Presence Server. Therefore, the transport protocol of the SIP server must be TLS.
Configure Skype/Lync Presence Server as follows:
The SIP Server you select for the Presence Destination can be None or a SIP Server that has been defined with a transport protocol of TLS.
Enable Skype/Lync Presence as follows:
Normalize Cache parameter must be set to False for the Presence feature to work.
Typically, a non-Lync endpoint desiring its presence to be published, will want the connection of both incoming and outgoing calls to trigger presence. This can be accomplished by defining one Transformation Table with two entries This transformation table will be used by an Action Set (defined in subsequent) Steps.
It is mandatory to have an entry in the Active Directory (AD) that is associated with the non-Lync endpoint; this AD attribute can be any field (ipPhone, homePhone, etc...). Options have been added to the transformation WebUI to make configuring Presence as straightforward as possible. When Presence - Called Address/Number is selected for Input Field Type (or Presence - Calling Address/Number), all of the remaining fields will be filled in with the most typical selections. See the figure below for an example. Note that the Input Field Value and Output Field Value are editable drop down boxes; they present the most likely selections, but also allow the user to overwrite with any value desired.
The example below will do an AD cache look-up for homePhone and match against the Called Address/Number. If there is a match, the msRTCSIP-PrimaryUserAddress of that AD entry will be copied into the Presence - Called Address/Number Output Field. It is this called presence value that will be used in the Request URI, To and From headers of the Publish message that announces the presence status. Similar configuration should be defined for the Presence - Calling Address/Number. The default value for the Input Field Value when the Input Field Type is Presence - Called(ing) Address/Number will be AD:ipPhone
Input Field Value and Output Field Value are editable list boxes. They present the most likely selections, but also allow you to overwrite the predefined values.
Create a Transformation entry as follows:
In the example below, the default value for Input Field's Value field is "==homePhone==" when the Type field is "Presence Calling Address/Number.
A Route Call Action configuration should be defined. This allows routing to take place at the end of the Action set used for Presence.
In order for the Action Set to be applied, it must be attached to a Signaling Group.
Attach as follows:
This topology change requires Lync 2013 Server to be updated to at least version 5.0.8308.866 released on 12/31/2014 as Cumulative Update CU5 HF7.1.
Lync 2013 Server versions earlier than 5.0.8308.866 will not allow the SBC to be configured as Trusted Application Server.
Before executing the steps below make sure that SBC is defined in the PSTN gateway section of the Lync topology.
Execute Get-CsSite cmdlet to find out the Site Id number
Execute New-CsTrustedApplicationPool cmdlet to create new pool that will host presence application
–Identity – FQDN of the SBC providing presence updates to Lync Server
–Registrar – FQDN of the Registrar service for the pool
–Site – Site Id obtained in Obtain the site ID.
Use any Front End or SBA for the Registrar, ideally choosing the most reliable connection to the SBC.
Execute New-CsTrustedApplication cmdlet to add a presence application to trusted application pool.
–ApplicationId – The name of the application
–TrustedApplicationPoolFqdn – The FQDN of the trusted application pool created in Create a Trusted Application Pool.
–Port – The port number on which the application will run (5061)
Execute Enable-CsTopology cmdlet for topology changes to take effect