Users can download the Lync 2010 mobile client for Nokia Symbian for free from the Nokia store. Users can use the client to connect to Lync Online if they're assigned a Lync Online license. This article describes how to troubleshoot some common issues that you may encounter when you use the Lync 2010 mobile client for Nokia Symbian.
Install the app
Users can download the Lync 2010 mobile client for Nokia Symbian for free from the Nokia store. Users should install the app directly to their device and use their user ID to sign in.
If a user experiences issues when they download or install the Lync 2010 mobile client, have the user change their connection type from 3G to Wi-Fi or from Wi-Fi to 3G. Then, have the user try downloading again. If the user still can't install the client, they should contact their cellular service provider or Nokia Support.
When Lync Online users sign in to the Lync Mobile app, all they have to do is enter their sign-in address and password. The Domain
and User name
fields are for on-premises Lync Server deployments only and aren't required for Lync Online.
To configure Auto-Detect settings and HTTP proxy credentials, click More Details
If automatic discovery for mobile clients hasn't been configured, users have to enter the following internal and external discovery addresses in addition to the fields that are listed in the table:
- Internal discovery address: https://webdir.online.lync.com/Autodiscover/autodiscoverservice.svc/Root
- External discovery address: https://webdir.online.lync.com/Autodiscover/autodiscoverservice.svc/Root
The Lync 2010 mobile client looks for DNS records different from those for which the Lync 2010 desktop client looks. For the Auto-Detect process to discover the correct Lync Online service, a CNAME record that meets the following criteria must be created for the Session Initiation Protocol (SIP) domain that's being used:
Collapse this tableExpand this table
To troubleshoot, use one or more of the following methods, as appropriate for your situation:
- Use the nslookup command and a public DNS server to determine whether the DNS CNAME record is configured correctly.
- If the user has the option to switch between Wi-Fi and 3G, have the user do this to determine whether the issue can be scoped to one kind of connection. If sign-in continues to fail on a 3G data connection even though the CNAME DNS records are configured, there may be an issue with the cellular service provider’s data connection.
- The user receives the following error message:
This error message usually indicates one of the following conditions:
Cannot connect to the server. It might be unavailable. Also please check your network connection, sign-in address and server addresses.
- A DNS lookup issue exists.
- The Auto-Detect CNAME records are configured incorrectly or aren't configured at all.
- The user receives the following error message when the user tries to sign in:
This error message indicates one of the following conditions:
Can’t sign in. Please check your account information and try again.
- The Lync 2010 mobile client can discover the correct Lync Online server but can't find the sign-in address that was entered by the user.
- The password is incorrect.
The contact list that's displayed in the Lync 2010 mobile client is read-only and can't be changed from the mobile device. If a user wants to add or to remove a contact from the list, the user must use the Lync 2010 desktop client or Outlook Web App (OWA) Instant Messaging (IM).
Chats tab and conversation history
tab on the Lync 2010 mobile client keeps track of only the conversations that occurred on the mobile device. It won't display conversations from desktop clients. Chats on mobile devices aren't displayed in the conversation history folder in the user’s Exchange mailbox.
Voice mail is read from Exchange Unified Messaging (UM) only. If it isn't enabled for UM, this tab doesn't work.
Comparison with other mobile clients
For a feature comparison of Lync 2010 mobile clients, go to the following Microsoft TechNet website:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Still need help? Go to the Office 365 Community