Hi,

I have users in our organization who are having SIP id and UPN suffixes added. So they are able to login through either their SIP ID assigned or the UPNs through LYNC. Through LYNC Client, they are able to login perfectly. but They are facing issue when they are trying to connect through LYNC mobile app? 

We have multiple SIP domains in organisation. We are facing problem for one domain.

I see all DNS SRV records are in order. Can you suggest any tests to run to check this? 

Thanks,

Vinay Mishra

• Edited by vinay6m Tuesday, February 03, 2015 4:28 PM

Hi, Yes it Redirects to dhriadlyncws.danahermail.com and the certificate it tries to get is na-join.danahermail.com. Even LYNC remote connectivity analyzer says it as failed. I reveiwed the certificate and following are subject Alternative names which seem to be correct.

DNS Name=dhriadlyncws.danahermail.com
DNS Name=na-join.danahermail.com

Did you run a certificate check tool? Look at https://ssltools.websecurity.symantec.com/checker/views/certCheck.jsp the certificate chain may not be properly installed on your server. 

Hi So many thanks to your for replying with valuable tool. I got the following in tool check:

na-join.danahermail.com This server is safe from Poodle vulnerability. This site is safe from the Heartbleed vulnerability. You have 1 error Intermediate certificate missing. Symantec Class 3 Secure Server CA - G4 | Download certificate Recommendations Update your certificate chain.

Your certificate chain is valid, but some older browsers may not recognize it. To support older browsers, download and install the missing intermediate certificate. | Download certificate

So, where do I need to install this certificate? on our ISA/TMG or Edge servers?

Thanks & Regards,

Vinay Mishra

Any server that has the certificate installed.  https://www.digicert.com/util/ does this for you, but I can't remember if it works with all vendors or only digicert.  It's easy enough to find out though. 

Hi,

This solved other minor issues. but for this issue, It cam out to be very minor. Since I was not with end users, they work remote I was not able to verify the configuration of lync client. Scene was, that user SIP domain was different than the domain mentioned in UPN suffix. So, in addition to sign-in address, domain login details in form of domain\username was required to put in lync Mobile app manually. This fixed our issue after a long time of analysis. Strange..

Thanks & Regards,

Vinay Mishra

• Proposed as answer by Anthony CaragolMVP Wednesday, February 11, 2015 7:25 PM

Hi,

This solved other minor issues. but for this issue, It cam out to be very minor. Since I was not with end users, they work remote I was not able to verify the configuration of lync client. Scene was, that user SIP domain was different than the domain mentioned in UPN suffix. So, in addition to sign-in address, domain login details in form of domain\username was required to put in lync Mobile app manually. This fixed our issue after a long time of analysis. Strange..

Thanks & Regards,

Vinay Mishra

• Proposed as answer by Anthony CaragolMVP Wednesday, February 11, 2015 7:25 PM
• Marked as answer by Eric_YangKModerator 2 hours 52 minutes ago

Hi,

This solved other minor issues. but for this issue, It cam out to be very minor. Since I was not with end users, they work remote I was not able to verify the configuration of lync client. Scene was, that user SIP domain was different than the domain mentioned in UPN suffix. So, in addition to sign-in address, domain login details in form of domain\username was required to put in lync Mobile app manually. This fixed our issue after a long time of analysis. Strange..

Thanks & Regards,

Vinay Mishra

• Proposed as answer by Anthony CaragolMVP Wednesday, February 11, 2015 7:25 PM
• Marked as answer by Eric_YangKModerator Tuesday, February 17, 2015 8:55 AM

Yes, Indeed. It was very helpful and came to know many things and resolved minor issues as well..

Thanks & Regards,

Vinay Mishra