IT Consultant Everyday Notes

Just some problems/solutions storage

Lync: Mobility

I am testing migration from Lync 2010 Enterprise Edition to Lync 2013 Standard Edition. One of thing which does not work is Lync 2013 Mobile for users already migrated to the new server. Let’s put it this way – it works when a user is outside of my internal WiFI network.

 

When the same Client is on internal network that is what I see in the Client logs:

 

</ReceivedResponse>
2013-05-07 16:51:51.796 Lync[2000:3540] INFO TRANSPORT CHttpRequestProcessor.cpp/266:Sending event to main thread for request(0x4c0cb18)
2013-05-07 16:51:51.796 Lync[2000:3540] INFO APPLICATION CUrlRedirectAndTrustResolver.cpp/605:UrlRedirectAndTrustResolver complete with url = http://lyncdiscoverinternal.mydomain.com/, Hops = 1, status = E_BadGateway (E2-3-35)
2013-05-07 16:51:51.796 Lync[2000:3540] INFO APPLICATION CTransportRequestRetrialQueue.cpp/692:Response received for req. UrlTrustResolver(04C0CB18): E_BadGateway (E2-3-35) (RemoteNetworkPermanentError); Done with req.; Stopping resend timer
2013-05-07 16:51:51.796 Lync[2000:3540] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/393:CUcwaAutoDiscoverGetUserUrlOperation::onEvent received.  Status = E_BadGateway (E2-3-35), url = http://lyncdiscoverinternal.mydomain.com/
2013-05-07 16:51:51.796 Lync[2000:3540] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation completed with url = http://lyncdiscoverinternal.mydomain.com/?sipuri=sip:alex.ig@mydomain.com, userUrl = , status = E_BadGateway (E2-3-35)
2013-05-07 16:51:51.796 Lync[2000:3540] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1476:AutoDiscovery: Falling back to probing external urls
2013-05-07 16:51:51.797 Lync[2000:3540] INFO APPLICATION CUrlRedirectAndTrustResolver.cpp/77:Starting CUrlRedirectAndTrustResolver with url = https://lyncdiscover.mydomain.com/?sipuri=sip:alex.ig@mydomain.com, maxHops = 10
2013-05-07 16:51:51.797 Lync[2000:3540] INFO APPLICATION CUrlRedirectAndTrustResolver.cpp/201:CUrlRedirectAndTrustResolver::processUrl called with url = https://lyncdiscover.mydomain.com/, hopCount = 0, maxHops = 10
2013-05-07 16:51:51.797 Lync[2000:3540] INFO APPLICATION CUrlRedirectAndTrustResolver.cpp/605:UrlRedirectAndTrustResolver complete with url = https://lyncdiscover.mydomain.com/, Hops = 0, status = S0-0-0
2013-05-07 16:51:51.797 Lync[2000:3540] INFO TRANSPORT CCredentialManager.cpp/164:getSpecificCredential for serviceId(4) returning: credType (1) signInName (alex.ig@mydomain.com) domain () username (alex.ig@mydomain.com) password.empty() (1) compatibleServiceIds(4)
2013-05-07 16:51:51.797 Lync[2000:3540] INFO TRANSPORT TransportUtilityFunctions.cpp/638:<SentRequest>
GET https://lyncdiscover.mydomain.com/?sipuri=sip:alex.ig@mydomain.com
Request Id: 04C0DD08
HttpHeader:Accept application/vnd.microsoft.rtc.autodiscover+xml;v=1

 

I tried http://lyncdiscoverinternal.mydomain.com from my Browser and received the following configuration:

{"_links":{"self":{"href":"https://lync02.mydomain.com/Autodiscover/AutodiscoverService.svc/root?originalDomain=mydomain.com"},"user":{"href":"https://csweb-ext.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain=mydomain.com"},"xframe":{"href":https://csweb-ext.mydomain.com/Autodiscover/XFrame/XFrame.html}}}

 

So I decided to add a record for my external web site to my internal DNS and point it to my Lync 2013 server. Same error.

Resolution: On Internal DNS I pointed csweb-ext.mydomain.com to Reverse Proxy listener, so basically I sent my internal Wifi Clients via Proxy instead of route them directly to Lync. For some reasons that resolved the issue and Lync Mobile works now for internally connected and externally connected users.

 

Note: my domain name in logs is changed.

Advertisements

One response to “Lync: Mobility

  1. Alex905 May 20, 2013 at 9:48 pm

    I have exactly the same issue, and because of this I never turn on WiFi at work. But this give me hope that it can be fixed. I will try next week and if it will work it will resolve my issue as well. Thanks for this solution!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: