Sign in
 
HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs
TechCenter >
> 
> 
Lync Mobility Autodiscover URLs

Answered Lync Mobility Autodiscover URLs

  • Friday, December 16, 2011 10:13 PM
     
     
    Sign In to Vote
    0

    We now have Lync mobility enabled internally and externally, but are having issues with the autodiscover URLs working properly. Ironically enough, autodiscover works fine for Droid clients, but for Windows Mobile clients I have to enter the full external autodiscover address for clients to connect. I have added all of the necessary autodiscover DNS records internally and externally (which again, are setup correctly because Droid clients work fine) We are using Forefront TMG as our reverse proxy with a Lync Standard Server.

    Thanks in advance.

     

All Replies

  • Sunday, December 18, 2011 4:55 AM
     
     
    Sign In to Vote
    0

    Hi ¡¡

    Have already double checked your TMG policy? If you test you web publishing policy , what you got? Remember use port bridging for your rule ....4443 and 8080 are used for external Lync web services, but the client request from the external clients are expected on 443 and 80. That’s why you have to do the port bridging.

    Trace at your TMG maybe you can find more clues of what’s happening.

     

    Amado Imperial
     
  • Sunday, December 18, 2011 9:43 AM
     
     
    Sign In to Vote
    0
    Same here, Android clients working fine but windows phone not working at all. In my case we are using iis url rewrite as reverse proxy.
     
  • Monday, December 19, 2011 12:27 PM
     
     Answered
    Sign In to Vote
    0

    Try checking the web.config file in the root folder of your external website.

    This file should contain lyncdiscover rewrite rules. If it doesn't, ensure that you copied the Mcx setup file into the lync deployment folder and that the bootstrapper process ran without error. This is where the rewrite rule gets created.

    The WP7 client visits http://lyncdiscover.example.com/?sipuri=user@example.com and then expects the URL to be rewritten to the full path, where the Android client oddly enough uses the full path by default.

    If the rewrite rule doesn't exist, you should be getting a 403 or 404 error, depending on various configuration parameters. 

     
  • Tuesday, December 20, 2011 5:38 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,dskurtzjr,

    You can enable and capture Lync logging on Windows Phone mobile as follows:

    1)On any of the main Lync for Windows Phone screen touch the ellipses … to bring up the menu and tap settings.
    2)On the settings page, tap to toggle Diagnostic logging.
    3)Exit Lync , launch, sign-in and reproduce the issue.
    4)Tap the ellipses to bring up the menu and tap about.
    5)On the about page, tap send diagnostic logs. On the Logs are in your Saved Picture folder tap ok and attach the image to the email that opens.

    You will get more specific information to find which connection steps it failed.

    Regards,

    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. This can be beneficial to other community members reading the thread.
     
  • Tuesday, December 27, 2011 6:10 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,dskurtzjr,

    Have you fixed the issue?

    Any updates please let us know.Thanks!

    Regards

    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. This can be beneficial to other community memb