Lync Server Mobility Allowed Domain value causes push notifications to fail

Applies to: Lync Server 2010 Enterprise EditionLync Server 2010 Standard EditionLync Server 2013

Symptoms

Use the steps listed below to ensure that the value being used for the Lync Server allowed domain is correct:


Note Use the following link to download and install the OCS logger utility for Lync Server 2013 to take SipStack logging from specific Lync Server 2013 Edge servers

Microsoft Lync Server 2013 Debugging Tools

Use the following steps to launch the Lync Server Logging Tool from the Windows Server console:


Using Windows Server 2012
  1. For Lync Server 2013 press the Windows function key and choose the Search option
  2. Type in Explore.exe and click on the Search icon
  3. Use Windows Explorer to browse to <local drive:>\Program Files\Microsoft Lync Server 2013\Debugging Tools,  usethe Windows Explorer details pane to locate OcsLogger.exe and double click on it
  4. For Lync Server 2010 press the Windows function key to access the Start page
  5. Click on the Lync Server Logging Tool tile
Using Windows Server 2008 or Windows Server 2008 R2

  1. Click on Start, All Programs, Microsoft Lync Server and then choose Lync Server Logging Tool
Use the following steps to continue with taking SipStack logging:
  1. Select SipStack logging component from the Logging Options selection
  2. Check the All Level, and then check All Flags
  3. Click on the Start Logging button
  4. Launch the Lync Server Management Shell from the Windows Server console
  5. Test federation with the Push notification Clearing House using Lync Server Test-CsFederatedPartner PowerShell cmdlet as per the example:

    Test-CsFederatedPartner –TargetFqdn accessproxy.contoso.com –Domain push.lync.com

  6. Wait for the Test-CsFederatedPartner Lync Server PowerShell cmdlet to complete
  7. Click on the Lync Server Logging Tool's Stop Logging button
  8. Click on the Lync Server Logging Tool's View log Files button to open the SipStack log in a text format
  9. Research the Sipstack logs from the Lync Edge server and locate the following diagnostic information:

    Result-Code: 0xc3e93d79 SIPPROXY_E_EPROUTING_MSG_UNKNOWN_DOMAIN

Cause

The allowed domain list has an incorrect value or is missing the entry for push.lync.com setting on the Lync Server.

Resolution

Use the steps listed below to resolve this issue:
  1. Launch the Lync Server Management Shell from the Windows Server console
  2. Use the Remove-CsAlloweddomain Lync Server PowerShell cmdlet to remove the unwanted hosting provider information as per the example:

    Remove-CsAllowedDomain -Identity fabrikam.com

  3. Use the New-CsAllowedDomain Lync Server PowerShell cmdlet to add the correct hosting provider information as per the example:

    New-CsAllowedDomain -Identity "contoso.com"

  4. Use the Invoke-CsManagementStoreReplication Lync Server PowerShell cmdlet to initiate Central ManageMent Store (CMS) replication to all replica stores in the Lync Server enterprise per the example:

    Invoke-CsManagementStoreReplication

    Note There could be a two to three minute delay as changes are processed by the Master Replicator

More Information

New-CsAllowedDomain

Remove-CsAllowedDomain

Test-CsFederatedPartner

Invoke-CsManagementStoreReplication

Lync Server 2013 supports the use of the Centralized Logging Service. For detailed information on how to configure the Centralized Logging Service for Instant Messaging (IM) and Presence.

Using the Centralized Logging Service

Lync server push notification flow

Push Notification Flow