Lync Server Mobility PushNotificationProxyUri value causes push notifications to fail

When an iPhone, iPad, or Windows Phone mobile client is not active, the Mobility service can send notifications, called push notifications, to the mobile device for events such as new or missed IM invitations, missed calls, and voice mail. However, push notifications for Lync mobile clients can fail if the PushNotificationProxyUri is configured incorrectly.

Use the information listed below to make sure that the value being used for the Lync Server PushNotificationProxyUri in the Microsoft Lync Server Mobility Service configuration is correct. Use the Lync Server Logging Tool on the Lync Server Edge server to gather SipStack logging:

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

Microsoft Lync Server 2013 Debugging Tools

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, use the 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 the 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 push notification flow using Lync Server PowerShell synthetic transaction cmdlet as per the example listed below:
   
   Test-CsMcxPushNotification -AccessEdgeFqdn LyncEdge.contoso.com
   
   
6. Wait for the Test-CsMcxPushNotification 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 Server Edge server and locate the following diagnostic information:

Start-Line: SIP/2.0 504 Server time-out
From: <sip:McxUser38453540-1e9f-4b46-84ca-c134d0ab3e23@contoso.com>;epid=B0CEE08135;tag=5c56bbb13
To: <sip:incorrect@push.lync.com>;tag=7D712188B1AABC752C702CFE05DF6790

Note The “To” field show the incorrect value set in the Microsoft Lync Server Mobility Service configuration for PushNotificationProxyUri