Lync 2013 Mobility Client - Video Call Issue (Everything Else works).

Hey Technet’ies,
I have been struggling for a couple of weeks now to resolve one of the final issues with a Migration/Upgrade Project on Lync Server 2013.
I have nearly every Lync Client Scenario working well except the Mobility Client (outside of the domain) which cannot successfully complete a Video
Call to a Windows Desktop Client (inside the domain) – the toast pops up, but when we click accept - it just times out after 15 seconds
K
The strange thing is every other Video Call scenario works;
Mobility Client (Outside Domain)
àWindows Desktop Client (Inside Domain)
= Unsuccessful
Mobility Client (Inside Domain)
à Windows Desktop Client (Inside Domain) = Successful
Mobility Client (Inside Domain)
à Windows Desktop Client (Outside Domain) = Successful
Mobility Client (Outside Domain)
à Windows Desktop Client (Outside Domain) = Successful
Mobility Client (Inside Domain)
à Mac Desktop Client (Inside Domain) = Successful
Mobility Client (Inside Domain)
à Mac Desktop Client (Outside Domain) = Successful
Mobility Client (Outside Domain)
à Mac Desktop Client (Outside Domain) = Successful
Mobility Client (Outside Domain)
à Mac Desktop Client (Inside Domain) = Successful
Mobility Client (All Scenarios)
à Mobility Client (All Scenarios) = Successful
Our setup is pretty standard;
All OS servers are Win Server 2012 R2
Lync 2013 Standard FE Server
Lync 2013 Edge Server
Reverse Proxy IIS AAR (Also Win Server 20012 R2)
Lync 2013 Desktop Clients, Lync 2011 Mac Clients, IOS and Android Mobility Clients – all latest versions.
External NAT (via Cisco Routers ACL’s)
Internal Windows Firewall Currently off on all Servers
All Certs / DNS Configured as per Technet Recommendation
I have reviewed / analysed a number of log/trace files – looking for some/any information on the problem;
Mobility Client (cmlogX.log)
Windows Desktop Client (*.etl) / Microsoft Message Analyzer
Lync 2013 Server (CSController)
With all my looking I could not make out an error except a timeout (15 seconds) on the Mobility Client log (which I currently can’t find).
Clearly we are missing something and I have gone up and down our implementation a number of times, the only semi-unknown is our old 2010 Pool / Central Management Server (which is currently pretty much redundant but the majority of users still on).
I would really appreciate any feedback anyone can provide or any insight anyone may have on this challenge.
Thanks in advance, Alex.
Alex

Hi Andrew,
Thanks for the quick contact!!
Sorry - typo in my post, I have now corrected it;
Mobility
Client (Outside Domain) àWindows
Desktop Client (Inside Domain) = Unsuccessful
So I completely missed that blog post of yours (out of the 100's I have read) and you are the first person to clearly say (in simple terms) to point the lyncweb.contso.com to the public IP address on my internal DNS, I have just made that change and see
if it will correct the issue - will wait for replication.
Also I am running IIS / AAR as Reverse Proxy (not ISA) and had the Internal DNS Host A of lyncweb.contso.com and lyncdiscover.contso.com point back to my Reverse Proxy Internal NIC (i.e. 10.1.1.32) as the External NIC is isolated on in the Perimeter Network,
is this correct?
So it now goes like this
*Inside Domain*
lyncdiscover.contson.com --> 10.1.1.32 (Reverse Proxy Internal Nic) --> 10.1.1.26 (Front End Server)
lyncweb.contson.com --> 201.183.0.1 (Reverse Proxy External Nic - Public IP) --> 10.1.2.16 (Reverse Proxy External Nic) --> 10.1.1.26 (Front End Server)
Does this make any sense, I know ISA and IIS/AAR are pretty much interchangeable.
Thanks again Andrew and look forward to any feedback,
Alex.
Alex

Similar Messages

Lync 2013 mobile client can't see all fields in contact card

We have deployed Lync 2013 infra in our organization, now we observed, mobile Lync client users are not able to see other users mobile number on contact card rest all information is visible.
Is there any workaround or fix to resolve this issue. Appreciate quick help.

That's effectively by design (but a popular complaint). The workaround is to put the users who's mobile numbers you need in your Outlook contact list. There's another workaround related to setting the privacy relationship, but you have to coordinate
it with many people which is not too feasible.
Here are others upset about it:
http://ammarhasayen.com/2013/09/25/lync-2013-mobile-contact-card-not-showing-mobile-number/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Lync 2013 Mobile Client

have a test Lync 2013 onprem installation, everything works fine both from inside and outside, however the Lync Client for iphone does not function as supposed. I checked debug logs on all servers and see nothing that could cause the behaviour. The strange
thing is that for example IM is actually working, the problem is that it disconnects on every action.
So, the test scenario is as following
- User 1 is logged on Lync Client on Windows 7 - LAN
- User 2 is logged on on Lync Mobile on Iphone - public internet
User 1 sees presence of User 2
User 1 sends IM message to User 2 - no errors
User 2 successfully recieves the message - gets an error "Failed to process the server respons" and appears offline
User 2 signs out of Lync Mobile and signs back In- no errors
User 2 sends IM message back to User 1 - gets an error "Failed to process the server respons" and appears offline
User 1 recieves the IM message - no error
Any glues anyone? Where to look? I used debugging tools (S4 and SIPStack) both on Edge and FE and found nothing strange
Thanks in advance
Emin

Hi,
Which kind of Reverse Proxy did you use (TMG or IIS ARR)?
Did the issue only happen to you or for multiple users?
Did the issue only happen for IPhone or for all kind of mobile clients (IOS, Android, Windows Phone)?
If the issue happen only for you, please try to use another mobile and test the issue again.
If the issue happen for multiple users, and only happen for IOS client, try to update to the latest version for Lync IOS client and test again.
If the issue happen for multiple users, and happen for all kind of mobile platforms, double check the configuration of Reverse Proxy ( certificate, port).
For WP8 root certificates need to have HTTP URLs in the CRL (Certificate Revocation List). If root certs doesn’t contain these CRL attributes than the certificate won’t be accepted by WP8 and sign in would fail.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Mobile client on Windows phone

Hello All,
I am configuring Lync 2013 client and lync 2013 server.
When i try to sign in on Windows Mobile, it does not sign in. Log file also empty.
I uses IIS ARR as RP. Is there any way to see logs on IIS ARR ?
regards

Hi,
Did the issue happen only for you or for multiple users?
You can login manually in your Windows Lync client:
https://<ExtPoolFQDN>/Autodiscover/autodiscoverservice.svc/Root for external access
https://<IntPoolFQDN>/AutoDiscover/AutoDiscover.svc/Root for internal access
You can check Reverse Proxy (IIS ARR) with the help of the link below:
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

LYNC 2013 mobility clients disconnect and AAR bad response time

Good day,
I'm new to this, but have to implement LYNC 2013 for our company.
I have implemented Lync 2013 by following various instructions and all seems fine... apart from all mobile clients (internal/external - Andoid/IOS). They get disconnected after a few minutes. On Android the error is "unknown error" (very useful)
and on IOPS it's "unhandeled alert type 302 E_Badgateway (E2-3-35).
What I have noticed is that on AAR, on the LYNCWEB server farm (under " Monitoring and Management") the response time is huge (10000 + ms) and when the errors come up on the clients I get a "failed request".
I can not think what may be wrong but all is pointing to AAR?
AAR is version 3 running on 2021 R2
any ideas? been stuck for a week on this now.
Many thanks
DD

Hi,
From your description above, it seems to be the issue with IIS ARR.
You can check with the following steps:
Check if DNS records and certificate were appropriate.
Check if ExposedWebURL set to External.
Try to increase the time out value from 200 to 1800
More details:
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 mobile client (android/windows phone) can't sing in

Hello
We have deployed Lync 2013 Server (no CU)in our Organization, wehn we use desktop client or Metro App, all works fine. But when we trying to connect from android or windows phone App, we get notice:
"We cannot log you in beacuse your organization don't support this produkt version"
Some one can advice ?

Hi,
Agree with Michael.
What’s more, did you deploy Reverse Proxy on DMZ zone to support mobility devices to login Lync client?
If not, you need to deploy a Reverse Proxy firstly with the help of the link below:
http://technet.microsoft.com/en-us/library/gg398069.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 mobile client. Can't verify the certificate from the server. Please contact your support team

We upgraded Lync Server 2010 to Lync 2013.
Users are able to login on desktop clients but unable to connect on mobile client. We get following error message:
Can't verify the certificate from the server.
Please contact your support team

Please check the Root CA is installed on your mobile device.
Can you sign in externally?
Please check you have updated the DNS records for Lync mobile autodiscover service.
Lisa Zheng
TechNet Community Support

IPad calendar won't open march 2013 in month view; just this one specific issue, everything else works fine. I've reset to factory but it still happens.

Hmm.....
New iPad, not been fiddled with in any way. When I use calendar, everything is fine except when I try to view march 2013 in month view, whether by switching to "month" from a march day view, or by moving from another month already in month view.
The application just closes down. No issues with data loss. No issues with same calendar data on my mac or iPhone.
I've reset to factory setting and restored but it persists.
Any thoughts? Thanks, Andrew.

The workaround for this is to remove any all day events from April 1 or change from all day to something other than all day event.
The update to iOS 6.1 is supposed to have fixed the bug according to some of those that have posted today.

I updated my 4s to iOS 6.0, now i can no longer make phone calls. Everything else works.

I updated to the new iOS 6.0 software for my iphone 4s and now every phone call I make is ended before it rings. Messaging, voicemail, facetime, wifi, 3G/4G network are all still working. I've turned it off then on and reset the network settings and still nothing. any other ideas?

1. Reset iPhone (no data loss): Press both home and power buttons for at least 10 seconds, releasing when the Apple Logo appears
2. Settings > General > Reset > Reset Network Settings

Lync 2013 Mobility Issue

Hello,
I have a Lync 2013 server installed with CU1.
I can connect to it perfectly with the windows client and the mobile Lync 2010 client. However when i try to login to the server with the Lync 2013 mobile client, i get : "An error occured in Lync. Please retry. If the problem persists, contact your
support team."

Hi Barry,
i have fixed the certificate issue, now i get an xml file when going to the web address.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<resource xmlns="http://schemas.microsoft.com/rtc/2012/03/ucwa" rel="root" href="https://lync.'domain'.local/Autodiscover/AutodiscoverService.svc/root?originalDomain='domain'.com.au">
<link rel="user" href="https://lync.'domain'.com.au/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain='domain'.com.au"/>
<link rel="xframe" href="https://lync.'domain'.com.au/Autodiscover/XFrame/XFrame.html"/>
</resource>

Lync 2013 android client fails to login bug when ISP overrides DNS

Hello all,
I've noticed an issue occurring in the latest Android client (as of 3/9/2015) with internet networks where the provider resolves all DNS queries to an IP address (e.g. T-Mobile, Cox Cable, and lots of others).
Essentially, sometimes I have noticed my android client stuck on "Signing in". The diagnostic logs show that the client is attempting to resolve http://lyncdiscover.contoso.com (which is not resolvable
externally), but T-Mobile is sending it into a search engine. The app continues to try to connect despite not realizing that it really did not resolve properly. See below logs.
<html><head><meta http-equiv="refresh" content="0;url=http://lookup.t-mobile.com/index.php?origURL=http://lyncdiscoverinternal.contoso.com/"/></head><body><script type="text/javascript">window.location="http://lookup.t-mobile.com/index.php?origURL="+escape(window.location)+"&r="+escape(document.referrer);</script></body></html>
</ReceivedResponse>
Mar 9, 2015 8:26:50 AM ERROR LYNC: ERROR TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/common/private/TransportUtilityFunctions.cpp/1874:Accept-types (application/vnd.microsoft.rtc.autodiscover+xml;v=1) not found in Content-Type response from server (text/html). Not decoding.
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/requestprocessor/private/CHttpRequestProcessor.cpp/266:Sending event to main thread for request(0x9a306048)
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CTransportRequestRetrialQueue.cpp/822:Req. completed, Stopping timer.
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUrlRedirectAndTrustResolver.cpp/610:UrlRedirectAndTrustResolver complete with url = http://lyncdiscoverinternal.contoso.com/, Hops = 1, status = E_ResponseUnknown (E2-1-5)
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CTransportRequestRetrialQueue.cpp/725:Response received for req. UrlTrustResolver(0x9a306048): E_ResponseUnknown (E2-1-5) (RemoteNetworkPermanentError); Done with req.; Stopping resend timer
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaAutoDiscoveryGetUserUrlOperation.cpp/393:CUcwaAutoDiscoverGetUserUrlOperation::onEvent received. Status = E_ResponseUnknown (E2-1-5), url = http://lyncdiscoverinternal.contoso.com/
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation completed with url = http://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected], userUrl = , status = E_ResponseUnknown (E2-1-5)
Mar 9, 2015 8:26:50 AM DEBUG SigningInActivity: onStop()
Mar 9, 2015 8:26:50 AM DEBUG SigninActivity: onStop()
Mar 9, 2015 8:27:20 AM DEBUG HubActivity: onPause()
Mar 9, 2015 8:27:20 AM DEBUG MyStatusFragment: onPause()
Mar 9, 2015 8:27:20 AM DEBUG ContactsFragment: onPause()
Mar 9, 2015 8:27:20 AM DEBUG HubActivity: onStop()
Mar 9, 2015 8:27:20 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/objectmodel/private/CApplication.cpp/944:CApplication::serialize() called
Mar 9, 2015 8:27:20 AM VERBOSE LYNC: VERBOSE APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/privateandroid/CCredentialStore.cpp/90:storing credentials for service:0
Mar 9, 2015 8:27:20 AM VERBOSE LYNC: VERBOSE APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/privateandroid/CCredentialStore.cpp/90:storing credentials for service:1
Mar 9, 2015 8:27:20 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/objectmodel/private/CBasePersistableEntity.cpp/179:Storing 1 out-of-sync Object Models took 32ms
Mar 9, 2015 8:27:20 AM INFO LYNC: INFO UTILITIES /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/platform/persistentstorage/private/CBasePersistableComponent.cpp/245:Storing 3 out-of-sync components took 1ms
Mar 9, 2015 8:27:20 AM INFO PreferencesManager: commit is called on
Mar 9, 2015 8:27:20 AM DEBUG MyStatusFragment: onStop()
Mar 9, 2015 8:27:20 AM DEBUG ContactsFragment: onStop()
Mar 9, 2015 8:27:27 AM ERROR HttpConnection: org.apache.http.conn.HttpHostConnectException: Connection to https://lyncdiscoverinternal.contoso.com refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:183)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
at com.microsoft.office.lync.platform.http.HttpEngine.execute(HttpEngine.java:502)
at com.microsoft.office.lync.platform.http.HttpConnection$1.run(HttpConnection.java:219)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.net.ConnectException: failed to connect to /198.105.244.104 (port 443) after 180000ms: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:238)
at libcore.io.IoBridge.connectErrno(IoBridge.java:171)
at libcore.io.IoBridge.connect(IoBridge.java:122)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:456)
at java.net.Socket.connect(Socket.java:882)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:144)
... 12 more
Caused by: android.system.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:223)
... 19 more
Since DNS overrides by ISPs are a common occurance, I believe the app should properly handle this situation. I installed an app to override my DNS and use Google's DNS servers, and the client connects fine.

Hi,
Did you login Lync 2013 mobile client internal or external the company?
Did the issue also happen for IOS/Windows Phones or just happen for Android Phones?
Please try to check if the issue only happen for your mobile Lync client or also happen for other Android mobile clients.
If the issue only happen for your Android mobile, please try to uninstall Lync client and install the latest version from Android Market and test the issue again.
If the issue happen for multiple mobile clients, please double check the Reverse Proxy settings, if you use IIS ARR for Reverse Proxy, you can troubleshooting with the help of the link below:
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Eason Huang
TechNet Community Support
Ok, I figured out that I had a partial misconfiguration, but the existing client behavior still leads to long delays on a variety of networks. I had the reverse proxy forwarding into port 80 instead of 8080, which seemingly caused problems
during the second autodiscovery phase after the first timed out. I have since confirmed that it's not just T-Mobile, but any such provider (e.g. Cox Cable, see below) that resolves all DNS entries.
Essentially, the following is happening:
1) Client attempts to resolve lyncdiscoverinternal first.
2) DNS record resolves to ISP's website, because they resolve everything and will return their own page if the entry really doesn't exist.
3) Lync client continues to try to connect to the ISP's address, and sits for at least a minute until it eventually falls to the lyncdiscover record.
From the below log entries, you can see that the login process is delayed a full minute due to the client being stuck on the lyncdiscoverinternal record! Again, this does not occur on ISPs that do not catch all DNS resolution
attempts, regardless of validity.
Mar 9, 2015 8:10:04 PM INFO HttpConnection: originalurl is
https://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected] method Get
Mar 9, 2015 8:10:04 PM INFO HttpConnection: decodedurl is
https://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected]
Mar 9, 2015 8:10:04 PM INFO LYNC: INFO TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/common/private/TransportUtilityFunctions.cpp/689:<SentRequest>
GET
https://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected] 9, 2015 8:10:05 PM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation
completed with url =
http://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected], userUrl = , status = E_ResponseUnknown (E2-1-5)
GET http://lyncdiscoverinternal.contoso.com/
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "<html><head><meta">http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><meta
http-equiv="refresh" content="0;url=http://finder.cox.net/main?InterceptSource=0&ClientLocation=us&ParticipantID=96e687opkbv4scrood8k84drs6gw5duf&FailureMode=1&SearchQuery=&FailedURI=http%3A%2F%2Flyncdiscoverinternal.contoso.com%2F&AddInType=4&Version=2.1.8-1.90base&Referer=&Implementation=0&method=GET"/><script
type="text/javascript">url="http://finder.cox.net/main?InterceptSource=0&ClientLocation=us&ParticipantID=96e687opkbv4scrood8k84drs6gw5duf&FailureMode=1&SearchQuery=&FailedURI=http%3A%2F%2Flyncdiscoverinternal.contoso.com%2F&AddInType=4&Version=2.1.8-1.90base&Referer=&Implementation=0&method=GET";if(top.location!=location){var
w=window,d=document,e=d.documentElement,b=d.body,x=w.innerWidth||e.clientWidth||b.clientWidth,y=w.innerHeight||e.clientHeight||b.clientHeight;url+="&w="+x+"&h="+y;}window.location.replace(url);</script></head><body></body></html>
</ReceivedResponse>
Mar 9, 2015 8:10:21 PM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaDataSynchronizer.cpp/799:Mode 0
timed out
Mar 9, 2015 8:11:08 PM ERROR HttpConnection: org.apache.http.conn.HttpHostConnectException:
Connection to https://lyncdiscoverinternal.contoso.com refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:183)
Mar 9, 2015 8:11:08 PM INFO LYNC: INFO TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/common/private/TransportUtilityFunctions.cpp/1032:<ReceivedResponse>
GET http://lyncdiscover.contoso.com/

Lync 2013 Mobile unable to login from wifi

Dear All,
Many thanks in advance.
My Lync 2013 mobile client is unable to login via internal network.
I have tried to provide external web directory and lyncdiscover by giving way through internal leg of reverseproxy(TMG).
I think I'm missing something from the basic. Will appreciate your reply. :)

You are not missing something basic, this is a real issue with using Lync mobile while on internal corpnet. A known feature (issue) with Lync mobile is that has to connect to the external web services. So when internal it will hairpin out your FW and connect
to the web services:
http://technet.microsoft.com/en-us/library/hh690030.aspx
Some more info:
http://blog.schertz.name/2013/07/understanding-lync-2013-mobility/
A lot of Firewalls do not allow this sort of "hairpinning".
Thom Foreman, MCSE, MCSA, MCTS

Voice problems with Lync 2013 Mobile

Hi
I have a situation where Lync 2013 on both iPhone & Android has started giving problems with making and receiving voice calls. There are no problems with Windows, Mac or Phone Edition clients that I'm aware of. I have not tested anything over the VPN,
but this should not be a factor.
For receiving calls - If the user is connected to the LAN via Wi-Fi AND the call is from an internal user, all works fine. If the call is from an external user OR the user is connected via 3G, then the call just shows "Connecting" indefinitely.
This includes transferred calls.
For making calls - If the user is connected to the LAN via Wi-FI and calls either an internal or external users, all works fine. If the user is connected via 3G and calls either an internal or external user, the phone rings, but when it's answered it shows
call ended.
I have ran RUCT on a computer outside the network, with the following findings:
DNS:
Record
Type
Hostname
IP Address
Port
Weight
Priority
_sip._tls.domain.com
SRV
sip.domain.com
Edge External IP
443
100
0
sip.domain.com
A
sip.domain.com
Edge External IP
sipexternal.domain.com
A
sipexternal.domain.com
Edge External IP
meet.domain.com
A
meet.domain.com
<null>
_ntp._udp.domain.com
SRV
pool.ntp.org
NTP Server IP
123
100
0
_sipfederationtls._tcp.domain.com
SRV
sip.domain.com
Edge External IP
5061
100
0
lyncdiscover.domain.com
A
sip.domain.com
Edge External IP
lyncdiscover.domain.com
CNAME
sip.domain.com
I have ran Test Port on each entry where there is a port with successful results. Ping works on all entries.
If I query Certificate Information on sip.domain.com with port 5061 or 444, it succeeds and returns the certificate with subject sip.domain.com. If I query 443, it fails with error "An error occurred while retrieving the certificate. Unable to read
data from the transport connection: An existing connection was forcibly closed by the remote host."
On Microsoft Remote Connectivity Analyzer, all tests pass except for the certificate test:
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server sip.domain.com on port 443
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Running netstat on Lync Edge gives me the following with regards to port 443:
TCP <Internal IP>:443 Lync2:0 LISTENING
TCP <External IP>:443 Lync2:0 LISTENING
Firewall allows connections on port 443 and I've tried disabling the firewall as well. Trying to open https://sip.domain.com in the browser on the Lync Edge fails also, telnet succeeds, but no data is returned.
I've restarted the AV service and also rebooted the Lync Edge server, no change. In the topology builder, I can see that AV is configured to listen on port 443.
Any ideas would be most welcome.
Regards
Lionel
MCP Windows Server MCTS .NET

I have ran a large amount of additional tests. On my latest round of testing, I have obtained the following results:
Call received via PSTN gateway on user DID, answered by desktop client inside LAN - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN - works.
Call received via PSTN gateway on user DID, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call made through PSTN gateway from desktop client inside LAN - works.
Call made through PSTN gateway from desktop client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client inside LAN - does not work.
Call made through PSTN gateway from mobile client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client outside LAN (3G) - does not work.
Call from desktop client inside LAN to desktop or mobile client (regardless of location) - works.
Call from desktop or mobile client (regardless of location) to desktop client inside LAN - works.
Call from desktop or mobile client (regardless of location) to desktop or mobile client (regardless of location) - works.
There is no difference in behaviour between normal calls and conference calls. Reproducing the problem seems to require the following:
1. PSTN gateway needs to be involved
2. One party needs to be on mobile client
3. The mobile client needs to be inside the LAN or on a 3G connection, but not behind NAT on a DSL connection
The only conclusion I can make is that somehow NAT makes the problem go away, but it does not affect desktop clients (on the LAN or Wi-Fi at least, I do not have a way to test them on 3G).
The PSTN gateway (Cisco UCM) could also be the problem, but it works fine in all other cases. It has 4 trunks and makes all kinds of routing decisions, but once a call is routed to/from Lync, it should not make a difference on what type of device it is answered.
I'm really baffled by this one. Perhaps the 3G thing is a service provider issue and the issue on the LAN has something to do with the internal DNS combined with the behaviour of the mobile client. Just not sure exactly what.
MCP Windows Server MCTS .NET

Lync 2013 Android Client - Intermittently unable to join conference

Hi
I've just finished installing Lync 2013 on our network (single Front End, Single Edge, Reverse Proxy Server and Office Web Apps Server).
Everything works fine currently, with one exception:
When a user tries to join a meeting from the Lync 2013 client on Android (Lollipop), the call generally sits there "connecting..." before it fails to connect with a message of "Can't connect the call".
Sometimes when rejoin is pressed it will connect, but most of the time it fails.
Testing on a Windows Phone client (and Full/Basic Lync 2013 desktop client and Windows 8.1 App) it works every time
Is it possible this is a Lollipop compatibility issue or does Android require something that the other devices and clients don't?
Thanks for any suggestions
Andy

Hi Zahoor
Thanks for the response
Although you suggest it's not a compatibility issue, other devices seem to connect fine on the same account and same wifi, so I'm still tending towards a hardware / os compatibility issue.
I have now tested on a (very old) Samsung Galaxy S (i9000) running Cyanogenmod 11 (KitKat). This works absolutely fine every time.
The device I'm currently seeing issues with is a Nexus 5 running Lollipop.
As I said they're both on the same account and same wifi. Wifi is strong (sitting by the router), internet is a decent speed (150Mbps) and they are external clients.
When I'm back in the office I'll try some other devices to see if they have any problems.I've had a quick look through the logs and couldn't see anything that stood out, but I'll investigate again after seeing if the other devices work.
Cheers
Andy

Lync 2013 Android Client and simultaneous ring problem

this is sort of a duplicate but since the other one was marked as answered when it was not I figured I'd start this topic up again.
I set up the Android mobile client on my phone and all seemed to work fine (apart from the know bu where it keeps saying "calls aren't setup to ring mobile device..." whether the are or not) but I've run into the super annoying issue where
even if you turn simultaneous ring off for the cell phone number it still rings through when I get a call on my Lync work phone (a bit delayed so it rings just before voice mail picks up). What stinks is that even if I completely sign out of the Lync mobile
app I still get these ring throughs. The only solution was to reinstall the app with a bogus cell number (which is a bad way to go as it might be calling a random number if I'm not careful). the other thread had a moderator give the answer to create a user
level voice policy to not allow simultaneous ringing. Yeah, thanks. I'd actually like to use the feature sometimes and so would all of my users.
So, is this a bug in the Android client? In the Mobile functionality on the server? What? When I run SEFAUtil on my account it doesn't show any simulring or forwarding (my full Lync 2013 client agrees with that) so what the heck is going on. I can't roll
this upgrade from 2010 out to users until this can be resolved.
Steve

I think I found the solution to the annoying ring to the phone even when your turn off your call forwarding/sim ring.
In Lync 2013 desktop client, when you first setup SIM ring, it asks you to enter the phone that you would like to have sim ring. In this case, most likely your cellphone number. Then when you are sick of SIM ring, you decide to turn this feature off, but
you still get SIM ring to your cellphone which is very annoying. If I remember correctly, in Lync 2010, when you switch from SIM ring ON to OFF, the cellphone number will be deleted automatically. In Lync 2013, however, doesn't do so. Therefore, your cellphone
number is still there even though your have call forwarding OFF. This is a bug. The work around to it is to go to Tools > Options > Call Forwarding, select SiM ring; then from the drop down list, instead of choosing your saved cellphone number, choose
WORK number. Then select "Turn Off Call Forwarding". Now, go back to SIM ring option again, you will see the saved cellphone number is now gone. It will only display your work number. Now, try to make a test call to your Lync phone, it shouldn't ring to your
cellphone anymore.
To me, this seems to have fixed it. You can try this and let me know if that fixes yours too.
A@RJC

Lync 2013 Mobility Client - Video Call Issue (Everything Else works).

Similar Messages

Maybe you are looking for