Lync Push Notifications: 504 Timeout Error

I ran into an issue at a customer recently where push notifications for mobility were not working. Upon further investigation, the messages were receiving a 504 timeout with the Push Notification Clearing House (PNCH).

 

For reference, the push process interacts with the PNCH, and then on to the Apple or Microsoft Push Services. This happens through Lync Federation, through a Lync Edge Server.

clip_image001

When you are testing push notifications, Test-CSMCXPushNotification is the cmdlet to use. This will actually attempt to send a push message to the clearing house and report back any errors.

When using this cmdlet, use the following syntax: Test-CSMCXPushNotification – AcessEdgeFQDN <INTERNAL EDGE POOL>

In my case, the error below was displayed:

PS C:\Users\rwintle> Test-CsMcxPushNotification -AccessEdgeFqdn edgepool.contoso.com

Test-CsMcxPushNotification : A 504 (Server time-out) response was received from the network and the operation failed. See the exception details for more information.

At line:1 char:27

+ Test-CsMcxPushNotification <<<<  -AccessEdgeFqdn edgepool.contoso.com
+ CategoryInfo          : OperationStopped: (:) [Test-CsMcxPushNotificatio
n], FailureResponseException
+ FullyQualifiedErrorId : WorkflowNotCompleted,Microsoft.Rtc.Management.Sy
ntheticTransactions.TestMcxPushNotificationCmdlet

After some investigation, Microsoft has confirmed that the Federation SRV record is required for push notifications to work properly.

The PNCH will perform a look up on the SIP Domain for the Federation SRV record (_sipfederationtls._tcp.contoso.com). If this does not succeed, a 504 error will be thrown.

To fix this issue, you must configure that SRV record to point to your access edge server used for outbound Lync Push Federation Requests.

(1211)

If you like it, share it!

    Posted on by Randy Wintle in Uncategorized 15 Comments

    15 Responses to Lync Push Notifications: 504 Timeout Error

    1. Pingback: Lync Push Notifications: 504 Timeout Error | Microsoft UC Made Easy « JC’s Blog-O-Gibberish

    2. Ivo

      Hi,

      “To fix this issue, you must configure that SRV record to point to your access edge server used for outbound Lync Push Federation Requests.”

      You mean I should have this record on our internal DNS?

      Kind regards,
      Ivo Frenken

       
      • Randy Wintle

        No that SRV record needs to exist in public DNS.

        That record should point to the public FQDN of your access edge server.

         
    3. Eric

      Hey Randy, my public DNS SRV is set up correctly but I’m still receiving this error…I also get it when I run Test-CsFederatedPartner but all other partners I’m federated with test fine.
      It’s an OCS edge but everything (appears) to be configured correctly.

       
      • Randy Wintle

        Did you recently put that DNS record in, or was it already there?

        I think there is a long wait in the MS servers updating DNS records which is why I ask.

         
        • Eric

          It’s been there for a couple of years and hasn’t been changed at all.

          I just ran a trace and seen this in the failure:
          “Allowed partner domain resolved by DNS SRV to a FQDN that matches a different routing rule”
          not sure what that means though

          Cheers!

           
    4. Pingback: What to do when you get a “504 (Server time-out) response” for Lync mobile push notifications? | I'm a UC Blog

    5. Peter

      Excellent post. Your blog is a tremendous help for all of my Lync deployments.

       
    6. Ameer

      Hey Randy, i have the same problem but i cant create srv record for my edge server, as my FQDN is using local domain not the public domain, what i have to do in my case ?

      Note that i have two DNS servers one for external use and one for internal use, and we are hosting multiple SIP domains.

      thanks .

       
      • Randy Wintle

        You should be using public name space for your external edge interface.
        If you don’t want to change your configuration around, you can actually just update the certificate on that server to have a public name, and point a DNS record there.

         
        • Ameer

          Hi Randy, i did not understand you correctly, what i have is an Edge server configured with FQDN “LyncEdge.contoso.local”, and Active Directory domain is contoso.local, public domain is contoso.com, i have public SAN certificate that includes the following (Sip.contoso.com, Webconf.contoso.com) and its assigned to the Edge services, i have created SRV record “_sipfederationtls._tcp.contoso.com” targeting “SIP.Contoso.com” on my public DNS, but still it did not worked, how can i solve this problem; does changing FQDN for the edge to “LyncEdge.contoso.com” and adding edge public FQDN to SAN certificate? do i have another solution?

           
          • LB

            Ameer, we have the same problem as you. Did you solve the problem?

             
            • Hazem

              I think you need to make sure that port 5061 is opened on the edge or hardware firewall infront of edge

          • Josh

            Same issues. Did you resolve the problem Ameer?

             
        • Ameer

          Hi Randy, i did not understand you correctly, what i have is an Edge server configured with FQDN “LyncEdge.contoso.local”, and Active Directory domain is contoso.local, public domain is contoso.com, i have public SAN certificate that includes the following (Sip.contoso.com, Webconf.contoso.com) and its assigned to the Edge services, i have created SRV record “_sipfederationtls._tcp.contoso.com” targeting “SIP.Contoso.com” on my public DNS, but still it did not worked, how can i solve this problem; does changing FQDN for the edge to “LyncEdge.contoso.com” and adding edge public FQDN to SAN certificate? do i have another solution?

           

    Add a Comment