locked
Internal/External Mobil Users Connection Problem (ExposedWebURL) RRS feed

  • Question

  • Hi,

    I've tried to Lync Mobility Connection, but I have some problems.

    If ExposedWebURL setted "External" i can only join lync external network, but internal wifi users can not login mobil device.

    PS C:\> Get-CsMcxConfiguration
    Identity                       : Global
    SessionExpirationInterval      : 259200
    SessionShortExpirationInterval : 3600
    ExposedWebURL                  : External
    PushNotificationProxyUri       : sip:push@push.lync.com


    If ExposedWebURL setted "Internal" i can only join lync mobile Internal Wifi network but i have tried to external(3g) don't working
    PS C:\> Get-CsMcxConfiguration
    Identity                       : Global
    SessionExpirationInterval      : 259200
    SessionShortExpirationInterval : 3600
    ExposedWebURL                  : Internal
    PushNotificationProxyUri       : sip:push@push.lync.com

    I need to ensure the connection of two cases,

    Friday, February 24, 2012 9:29 AM

Answers

  • The recommended configuration is to have the ExposedWebUrl set to External, and then make the lyncdiscover.sipdomain.com resolvable to the external IP address of your reverse proxy both in internal DNS as well as external DNS.

    So your mobile clients on internal wifi should be able to route out to the external interface of your Reverse Proxy (effectively "hairpinning" the traffic). This removes complexity with certificates and establishes a consistent connection point for mobility.


    Justin Morris | Consultant | Modality Systems
    Lync Blog - www.justin-morris.net
    Twitter: @justimorris
    If this post has been useful please click the green arrow to the left or click "Propose as answer"

    • Proposed as answer by Greg Seeber Friday, February 24, 2012 4:53 PM
    • Marked as answer by Sharon.Shen Monday, February 27, 2012 9:23 AM
    Friday, February 24, 2012 10:49 AM

All replies

  • The recommended configuration is to have the ExposedWebUrl set to External, and then make the lyncdiscover.sipdomain.com resolvable to the external IP address of your reverse proxy both in internal DNS as well as external DNS.

    So your mobile clients on internal wifi should be able to route out to the external interface of your Reverse Proxy (effectively "hairpinning" the traffic). This removes complexity with certificates and establishes a consistent connection point for mobility.


    Justin Morris | Consultant | Modality Systems
    Lync Blog - www.justin-morris.net
    Twitter: @justimorris
    If this post has been useful please click the green arrow to the left or click "Propose as answer"

    • Proposed as answer by Greg Seeber Friday, February 24, 2012 4:53 PM
    • Marked as answer by Sharon.Shen Monday, February 27, 2012 9:23 AM
    Friday, February 24, 2012 10:49 AM
  • Agree with Justin. How ever there are some network in which if you create Lync external url A record in internal DNs pointing to TMG external interface doesnt work and seem to be spoofing on the network (This was my case). I have resolved it by poitning Lync external url A record in internal DNs to TMG internal Interface. In this case give one internal IP to TMG and in the lync publishing rule under litsening check the internal interface and give the new IP which is dedicated for Lync Mobility connectivity.

    Please mark it as answer if it answers your question also take a second to vote | MCITP LYNC | blog: salahuddinkhatri.wordpress.com


    SKHATRI

    Sunday, February 26, 2012 12:42 PM