| Add_docset_workflow |
|---|
| APPRJID | SYM-18217, SYM-18216 |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c078f, userName='null'} |
|---|
| DEV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7f3007b, userName='null'} |
|---|
| LDEV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c078f, userName='null'} |
|---|
| SVT1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'} |
|---|
| LSVT1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c078f, userName='null'} |
|---|
| AUTHJID | SYM-18215 |
|---|
|
| Section |
|---|
| Column |
|---|
width | 800px |
|---|
| Column |
|---|
|
| Info |
|---|
The instructions in this Best Practice assume the Sonus SBC 1000/2000 the node is running and connected to the WebUI. |
...
The example configuration items are used to configure the Sonus SBC 1000/2000 the
for Skype for Business (in order for Third Party Presence to be published):
- Skype/Lync Presence server has the FQDN of lyncpool.example.com.
- An analog phone connected to FXS port (phone number 2222) needs presence published when a call is connected/disconnected.
- CAS SG (Phones) defines an Action Set with Transformation Tables to alert the system that presence needs to be published.
- Phone number 2222 is defined in AD as attribute homePhone for a Lync user (msRTCSIP-PrimaryUserAddress = lync1@example.com). It is this relationship that allows the FXS phone at 2222 to publish presence for the Lync user.
Step 1. Configure the Skype/Lync Presence Server
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:
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Lync Presence Server Screen Example |
|---|
|  Image Modified
|
|
Step 2. Enable Skype/Lync Presence
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Node-Level SIP Settings Screen Example |
|---|
|  Image Added Image Removed
|
|
Step 3. Define AD Configuration/Domain Controller for AD Cache Look Up
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Active Directory (AD) Configuration |
|---|
|  Image Removed Image Added
|
|
Configure Domain Controller (DC)
| Tip |
|---|
| Sonus recommends selecting "msRTCSIP-PrimaryUserAddress=*" string as "LDAP Query" to select only Lync enabled AD users. |
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Domain Controllers Table |
|---|
|  Image Removed Image Added
|
|
Step 4. Configure Transformation Entries for Presence
...
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.
| Info |
|---|
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. |
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Presence - Called Example |
|---|
|  Image Added Image Removed
|
|
Step 5. Define An Action Configuration
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Action Configuration Table Screen Example |
|---|
|  Image Removed
|
|
...
 Image Added
|
|
Step 6. Define An Action Set for Presence
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Action Set for Presence - Called |
|---|
|  Image RemovedImage Added
|
|
Step 7. Attach An Action Set To The Desired Signaling Group(s)
...
| Panel |
|---|
|
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Signaling Group Table Screen Example |
|---|
|  Image Removed Image Added
|
|
Configure Lync Server
| Info |
|---|
SBC needs to be configured in Lync Topology as Trusted Application Server/Trusted Application. To configure, execute the following steps using the Lync Server Management Shell. |
| Note |
|---|
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. |
...
| Note |
|---|
Use any Front End or SBA for the Registrar, ideally choosing the most reliable connection to the SBC. |
Create A Trusted Application
...
| Note |
|---|
Ensure the port number matches the port number configured in Step 1. |
Enable The Lync Server Topology
...
| Code Block |
|---|
Enable-CsTopology |