locked
Lync Edge 2013 Push problem RRS feed

  • Question

  • Test-CsMcxPushNotification -AccessEdgeFqdn lyncedge.domain.com
    .com
    Test-CsMcxPushNotification : The workflow failed validation.
    At line:1 char:1
    + Test-CsMcxPushNotification -AccessEdgeFqdn lyncedge.domain.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Test-CsMcxPushNotification],
       WorkflowValidationFailedException
        + FullyQualifiedErrorId : System.Workflow.ComponentModel.Compiler.Workflow
       ValidationFailedException,Microsoft.Rtc.Management.SyntheticTransactions.T
      estMcxPushNotificationCmdlet

    error on the Lync 2013 Front End.
    Edge Server Lync 2013.
    Before moving to the edge lync 2013 it worked fine.
    Problem in a pool Lync 2013 and in 2010 the pool.
    For Lync 2010, Front End Test-CsMcxPushNotification-AccessEdgeFqdn lyncedge.domain.com works fine, but the push messages also do not work

    Test-CsFederatedPartner -TargetFqdn lyncedge.domain.com -Domain push.lync.com -ProxyFqdn sipfed.online.lync.com

    TargetFqdn : lyncedge.domain.com

    Result     : Success
    Latency    : 00:00:00
    Error      :
    Diagnosis  :

    https://www.testocsconnectivity.com reports that all is well

    certificates from GoDaddy, not wildcard. Worked fine for Lync Edge 2010.
    Outside calls work fine, but the push messages do not work.

    Thursday, November 8, 2012 9:11 AM

Answers

  • Hi,SIDERMANN,

    Let's clarify your scenario:You have Lync 2010 and Lync 2013 coexisted,before you upgrade from Lync 2010 Edge to Lync 2013 Edge,the test for Test-CsFederatedPartner and Test-CsMcxPushNotification  both return success,every thing about mobility works but push notification doesn't work;after moving Edge to Lync 2013 edge,the test for Test-CsFederatedPartner returns success too but the test for  Test-CsMcxPushNotification failed.Did all the other mobility function and external access work in this situation?

    Here are some suggestions:

    1)Check if you have enable site federation route assignment in your topology builder for the new Lync  Edge server/pool and re-publish the topology.

    2)Verify that you haven't enable IM filter or URL filter for IM and Presence in your Control panel.This is often caused the push notification testing successfully but noy working.

    3)Check if the federation SRV record also have updated and matched the default sip domain.

    4)Lync 2013 now use centralized logging service to replace the Lync logging tool to troubelshoot the issue,you can have a look at the guide http://technet.microsoft.com/en-us/library/jj688101(v=ocs.15).aspx and use it to collect the logs.

    5)Some old cases for your reference.

    http://social.technet.microsoft.com/Forums/da-DK/ocsclients/thread/a17eb01c-bbff-4bb6-adc0-90689d963ae9

    http://social.technet.microsoft.com/Forums/en-US/ocsmobility/thread/50219f42-d943-4856-8c84-e4a67809aa9c

    And also some other useful blog talking about push notification maybe helpful.

    http://outermonolog.wordpress.com/2011/12/22/lync-2010-mobility-push-notifications-and-default-sip-domains/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Regards,

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    • Marked as answer by Sharon.Shen Wednesday, December 5, 2012 2:02 AM
    Friday, November 16, 2012 8:16 AM

All replies

  • Also seeing the same thing, our certs are Comodo, I'm at a bit of a loss, hacking away at this all day but I can't really see anything happening using the Lync 2013 debug tools.

    Incidentally if you run the Test-CsMcxP2PIM command using negotiate does that work for you or fail?


    Simon Stearn - Militant South - Agile Architecture

    Thursday, November 8, 2012 2:45 PM
  • Test-CsMcxP2PIM - Success,

    But do not push notifications are sent during the test for Windows Phone!
    And to IOS should be sent! But it is through the Lync Client for them not to be sent.
    Do you have a name for the pool is in the Lync 2013 edge server certificate?
    I do not - maybe this is the reason

    But

    "https://www.testocsconnectivity.com reports that all is well"


    • Edited by SIDERMANN Thursday, November 8, 2012 7:11 PM
    Thursday, November 8, 2012 7:08 PM
  • Hi,SIDERMANN,

    Let's clarify your scenario:You have Lync 2010 and Lync 2013 coexisted,before you upgrade from Lync 2010 Edge to Lync 2013 Edge,the test for Test-CsFederatedPartner and Test-CsMcxPushNotification  both return success,every thing about mobility works but push notification doesn't work;after moving Edge to Lync 2013 edge,the test for Test-CsFederatedPartner returns success too but the test for  Test-CsMcxPushNotification failed.Did all the other mobility function and external access work in this situation?

    Here are some suggestions:

    1)Check if you have enable site federation route assignment in your topology builder for the new Lync  Edge server/pool and re-publish the topology.

    2)Verify that you haven't enable IM filter or URL filter for IM and Presence in your Control panel.This is often caused the push notification testing successfully but noy working.

    3)Check if the federation SRV record also have updated and matched the default sip domain.

    4)Lync 2013 now use centralized logging service to replace the Lync logging tool to troubelshoot the issue,you can have a look at the guide http://technet.microsoft.com/en-us/library/jj688101(v=ocs.15).aspx and use it to collect the logs.

    5)Some old cases for your reference.

    http://social.technet.microsoft.com/Forums/da-DK/ocsclients/thread/a17eb01c-bbff-4bb6-adc0-90689d963ae9

    http://social.technet.microsoft.com/Forums/en-US/ocsmobility/thread/50219f42-d943-4856-8c84-e4a67809aa9c

    And also some other useful blog talking about push notification maybe helpful.

    http://outermonolog.wordpress.com/2011/12/22/lync-2010-mobility-push-notifications-and-default-sip-domains/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Regards,

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    • Marked as answer by Sharon.Shen Wednesday, December 5, 2012 2:02 AM
    Friday, November 16, 2012 8:16 AM
  • Have same issue!

    MCSE:S, MCSE:M, MCITP, MCTS, CCNA, CCDA Infrastructure expert

    Friday, January 4, 2013 6:02 PM
  • Me too...

    Ivailo Tzenkov

    Tuesday, January 22, 2013 9:07 PM