Troubleshooting SIP issues

Owned by Yoav Crombie
Last updated: Apr 19, 2022 by Avi J. Levin (Unlicensed)
1 min read

Case: SIP filter does not respond to messages

Description: A customer reported that no message was blocked / replaced by the DLP when the message violated a certain rule. (In our case the Credit Card Number rule didn’t replace the number)

 

Steps to identify the issue:

  1. There is no auditing in the DLP Auditing table of a message sent that violates a DLP policy. Test with more than one rule to make sure the issue is not related to the rule

  2. There are no records in the SIP filter logs for the messages sent

  3. On the front end, run the following command via PowerShell:

    “Get-CsServerApplication” - Returns information about the server applications in use in your organization

    If the Lync_access_control “enabled” options are “false”, that means the service isn’t registered.

 

Solution:

The Symptoms above indicated that the SIP service is probably disabled or unregistered.

Use the following command to install the SIP:

“new-CsServerApplication -identity "Service:EdgeServer:<Edge Server Pool>/lync_access_control" -uri "http://www.agatsolutions.com/lync_access_control" -critical $false -enable $true -priority 0”

Check if the service is enabled. The following results should be expected when service is registered correctly:

 

Violate rules and see in the logs if the messages are shown.

Check if the DLP blocks or replaces the messages