Microsoft has released Lync 2013 Mobile Updates for iOS, Android, and Windows Phone

Microsoft released updates for the various Lync 2013 mobile clients. The Apple client update addresses the 7.1 iOS bug, Android is just Android, and the Windows Phone client gets a tweak to the interface. Unfortunately all that seems to be updated is the interface as the push notification system is still a requirement for WP only. This push experience delivers a poor IM experience when multi-tasking but again, it is limited to the WP client.

On the Windows Phone 8.1 (currently preview) it has been noted by myself and other MVPs that the contact list does not fully populate after initial login. I personally use UCS, others do not, and experience the same result. The fix?? Simply log out of the app and back in and everything is happy.

Product

Version

Download

Lync 2013 for Windows Phone

5.4.1087.0

MS App Store

Lync 2013 for iPhone

5.4

iTunes

Lync 2013 for iPad

5.4

iTunes

Lync 2013 for Android

5.3.1100

Google Play

Additional Notes: 
Lync Server 2010 build number is 4.0.7577.230
Lync 2010 Client build number is 4.0.7577.4445
Lync Server 2013 build number is 5.0.8308.577
Lync 2013 Client build number is 15.0.4605.1003

Lync Group Chat build number is 4.0.7577. 4409
Lync Group Chat Server build number 4.0.7577.4409
Lync Group Chat Admin build number 4.0.7577.4409

Lync Attendee build number is 4.0.7577.4356
Lync Attendant build number is 4.0.7577.4098
Lync Phone Editions build number is 4.0.7577.4420

Lync 2010 for Windows Phone build number 4.3.8120.0
Lync 2010 for iPhone build number 4.7
Lync 2010 for iPad build number 4.7
Lync 2010 for Android build number 4.0.6509.3001

Lync 2013 for Windows Phone build number 5.4.1087.0
Lync 2013 for iPad build number 5.4
Lync 2013 for iPhone build number 5.4
Lync 2013 for Android build number 5.3.1100

Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Apple iOS update 7.1 breaks Lync 2013 Voice/Video

It has been discovered that the latest Apple iOS upgrade 7.1 for iPhone, iTouch, and iPad devices breaks current Lync 2013 functionality. Specifically, it has been found that the update creates interoperability issues which causes voice and video to fail when using these devices. Microsoft is aware of the issue as seen in KB2955745 but there is currently no fix or workaround available.

The current solution? Hold off upgrading your Apple devices until a fix is found or you may be without Lync Audio/Video (I say might as Apple iPad Air and iPad Mini do not appear to exhibit the issue).

UPDATE
An update has been released and availabile in the iTunes store and may be foundhere. This update addresses the Apple flaw.

Your Smartphone – the New Lync Portable Phone

With the recent release of the various Lync 2013 mobile clients a new wave of Lync desktop and portable phones have come into play. Yes – desktop and the concept of a portable phone – all available for Lync 2013. How you ask? Quite simply.

With the new Lync 2013 mobile client allowing you to hold VoIP calls natively and its ability to interact with the system, you end up with two calling scenarios.

1)      You are on a call using your laptop/desktop/Aries phones. You realize you need to ‘leave’ your desk and you have the Lync 2013 mobile client installed on your smartphone. From the full Lync client, you park the call, enter the retrieval code into your mobile client (i.e. within the Lync dialer itself) and it retrieves the call. Very nice – you can move any Lync call from your desktop Lync client or Aries phone to your smartphone.

2)      You use the smartphone as your desk phone. Assuming you have wireless (and who doesn’t) sign-in to the Lync 2013 mobile client. All incoming calls will ring on your smartphone as well – just answer it.

The second option is how we replace a desktop phone with your smartphone. You could also use a Bluetooth headset paired with your smartphone making it a complete mobile package. There are a few things to consider however.

1)      The smartphone is VoIP – that means data. If you are using the smartphone on your cellular data network, you are using your data allotment. That may or may not be a problem, but here in the US most mobile phones have unlimited calling/phone minute plans but the data plans are restricted.

2)      If you answer/transfer the call while you are using the corporate Wi-Fi, that call is tied to the IP and network of that Wi-Fi. Leaving the facility or range of Wi-Fi means the call would need to switch to cellular, IP would change, and call would drop. I would bet that something is done to address this by a third-party sometime soon – something like NetMotion offers on the desktop (if not a solution from NetMotion themselves).

3)      Unfortunately the Lync 2013 mobile client lacks the ability to transfer the call back to the call park service – something I suspect will come in time. So, once the call is answered or transferred to the smartphone that is where it lives.

For a desktop or mobile replacement within the office, the issues above are non-existent. Using the new client you have another means to answer your calls and remain portable (not to mention a single phone device). For those looking for a means to use the smartphone as a way to start in the office and then leave we have a workable yet restricted solution. The key would be to make sure your Wi-Fi is OFF prior to transferring the call. This way, when you leave the office you are already on the cellular data network (just make sure you have the cellular data MB available). The last option of course is to simply transfer the call over PSTN to your smartphone. The real cost there will depend on your cellular plan and remember, you are tying up two phone lines (and Lync resources) as the Lync server infrastructure is conferencing the outside call and your smartphone call.

Try it out – play with the new mobile client – make an audio and video call from it – it is simply amazing and it opens up all kinds of possibilities and scenarios.

Lync Mobile iOS Certificate Errors

I ran into an issue (which I didn't with Android and WP7) where I was unable to login to the iPad and iPhone iOS Lync client. It turns out this error was two separate certificate errors. The first was immediately upon signing internal to the domain (because my Apple devices did not trust my internal CA). The second (internal or externally) was an issue with the intermediate certificate not being present on my KEMP Hardware Load Balancer.

Internal Root Certificate

The error I was seeing on my iPad was "Can't connect to the server. It might be unavailable. Also please check your network connection, sign-in address and server addresses". Again, the WP7 and Android devices were not experiencing this issue! (As a side, the Android devices did realize there was an untrusted certificate but I had the option of saying it was okay and move on. Eventually I simply emailed myself the root and intermediate certificates which installed with a simple click).

 

My Internal CA is comprised of a Root, Intermediate, and an Issuing CA yet the Apple devices only seem to care about the root. To add the certificate to the device, the Apple iPhone Configuration Tool is used. It is true that you could send yourself an email with the certificate, but I have found that the device does not fully trust that method. If you do not already have the Configuration Tool (it is not part of iTunes) download it from Apple here. There is a Mac version of the tool as well but I will show the Windows version.

Once the application is installed, launch the tool and navigate on the right to Configuration Profiles.

 

In the upper-right click New to create a Configuration Profile. The Configuration Profile can be used to set and configure all types of settings; however, I am only interested in adding a trusted root certificate to the device. Start by naming the profile. In my example, I have named it BriComp Root Certificate and set my unique identifier to com.bricomp.cert.profile. Complete the General settings by entering your company name and optionally a description.

 

Next, navigate down the list to the certificate icon labeled Credentials and click Configure.

 

After clicking Configure a list of certificates found on your local computer will be displayed. Assuming your computer trsuts your internal LAN certificates your root certificate will be shown here. Scroll to the correct certificate and click OK.

 

The certificate will be shown in the Credential window and all changes are immediate (i.e. there is no 'save' option). For small/single installs connect your device to your computer using the USB cable. The device will be displayed in the Configuration Tool under DEVICES. Select the device and then the Configuration Profile Tab.

 

You will notice there is an option to install the profile directly. Click Install to begin the process. On your device, a Install Profile window is shown where you must click Install followed by Install Now confirming the installation of the Root Certificate. If you have a passcode you will need to enter it and then click Done.

 

For mass installs, you can export the configuration profile using the tool and email it to all that need it.

External Certificate Error

Once I got past my internal certificate issue I was then receiving the error "Can't verify the certificate from the server. Please contact your support team".

 

This error was the same inside and outside my network but again, only on my Apple iOS devices. Puzzled for days I nearly gave up when I thought maybe...just maybe the Hardware Load Balancer needed the intermediate certificate loaded for DigiCert - the issuer of my web services external certificate. This is an easy process and if you followed my past blog on configuring the KEMP HLB for Lync this step may be required as well.

In the KEMP LB web configuration page navigate to Certificates | Intermediate Certs.

 

In this section you have the option of managing the intermediate certificates on your Load Balancer. Click Add New to display the New dialog. Here you need to paste the public certificate DigiCertHighAssuranceCA-3.cer into the text box and provide a name. The certificate can be downloaded from DigiCert's website athttps://www.digicert.com/digicert-root-certificates.htm. Save the file to your local computer and open it with Notepad. The certificate will look like a text file that is created when you are requesting a new certificate for yourself. Copy and paste the entire content unaltered into the KEMP website and name the certificate DigiCertHA3.
 

Click Add to complete the installation of the Intermediate Certificate.  That's it - once the LB trusts the DigiCert Intermediate and your device trusts your internal CA your client will be able to login.

Apple iOS has Finally Joined the Mobile Party

The Apple iOS Lync 2010 Clients for iPhone and iPad (separate apps) are finally available from the App Store. I had difficulty finding the Application using search but I did find it browsing the newly released applications.

The significant difference between the iOS version and the other clients is the Calendar integration natively within the Lync app. It allows you to see upcoming Lync conferences and join them directly from the application. This is different from, let's say the Windows Phone 7, where you are required to click join now from the meeting invite itself.

Happy playing with the new clients!