Consider the following scenario:
You create a Microsoft Lync 2013 enabled user account (user A) in Active Directory in a Lync Server 2013 environment. User A is configured to have a non-US telephone number that has an extension number.
Another user (user B) signs in to a Lync 2013 client in the environment. Then, user B adds user A to the contact list.
User B tries to call user A by clicking the telephone number hyperlink in the contact card of user A.
In this scenario, user B cannot call user A. Additionally, a conversation window appears.
Note This issue also occurs when the number is a work number, home number, or mobile number.
This issue occurs because the fMatched value is not set to true whenthe ParseE164Number functionreads the comma (,) by parsing the telephone number.
To resolve this issue, install the following cumulative update:
2825630 Description of the Lync 2013 update 15.0.4551.1005: November 7, 2013