Multi-party HD video. Enhanced video capabilities with p resolution and up to 6 people shown at once. Offline messaging. Share files via chat. Always up to date. Always have the latest Office apps, features, and services. Swipe to view more plans. Ready for Microsoft ? Contact sales. Lync resources Lync help topics Find user guides, training, and other support for Lync Learn more. Other versions of Office Learn about other versions of Office and how you can upgrade to the new Microsoft Office Download Office Download and install Office using an existing product key.
Download now. The sign out process is finished. If the client is in UI suppression mode, it is ready to be shut down. One of the running processes has called the BeginShutDown method, and the client is still shutting down. When the shut-down process is finished, the hosting Lync background process stops. Figure 1 shows the state transitions and sign in-related operations that move the client from state to state. GetClient method, check the current state of the client before calling any of the methods in figure 1.
The client can be in any of the states shown in the figure. The Lync sign in process is pretty reliable and only fails when the user has provided an incorrect sign-in URI, user name, or password. The less likely, but still possible cause is a network outage that occurs when a computer network interface card is disabled, a mouse chews through an Ethernet cable under the desk, a hub needs to be reset, or a router fails.
Incorrect credentials can be re typed and re submitted but network issues cannot be solved by using the Lync API. Instead, your application can inform the user that sign in is delayed and then let the user decide if she wants to continue to try to sign in.
The Lync client shows two distinct reactions to incorrect user credentials at sign-in time. It is simple to predict which behavior Lync will show and let you code for either behavior. If the client is in UI suppression mode and the user tries to sign in with incorrect credentials, sign-in is interrupted and the LyncClient.
CredentialRequested event is raised. Use this event to ask the user to re-type their credentials and then submit the updated credentials to complete the sign in. You can see an example of this credential submission process below.
If the client UI is not suppressed, no event is raised for incorrect credentials. Instead, the client remains in the SigningIn state until the user completes signing in by using the Lync client.
Once the sign in is completed, your application is notified that the state is now SignedIn. In this failure case, after sign in, the contact list fills with people who do not belong to the current user and new conversations are started with the wrong local user name. How can this happen? If your application calls the LyncClient. BeginSignIn and passes empty strings in the first three arguments, then Lync uses previously cached credentials to sign the current user in.
You can clear the credential cache by calling the SignInConfiguration. ForgetMe method and pass the sign in URI of the user whose credentials were used by the client. To be sure that the right user is always signed in, verify that the three string arguments are not empty before calling BeginSignIn. If you pass correctly formed strings in the first three arguments of the method, Lync uses them to sign the user in. If the arguments are not empty, but are incorrectly formed, an ArgumentException is thrown by BeginSignIn.
These delays are the result of network bandwidth or server utilization issues. Instead, use the LyncClient. SignInDelayed event to tell the user about the status of the sign in operation and how long it is taking. The only way that you can cancel the sign in operation is to call the BeginSignOut method.
SignInDelayed event is raised every 30 seconds starting when network outage is detected. The status code that is returned in the event data 0x80EE00BD tells you that the sign in operation has timed out. Instead, shut down your application or ask the user if she wants to wait until connectivity is restored.
Figure 2 shows the logic flow of the sign in process. The details of how to handle each state change event are explained in the following How to procedures. The procedure in this section handles three of the most likely client states that your application sees after getting the Microsoft. LyncClient object from the static LyncClient. GetClient method. Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical.
Not enough information. Not enough pictures. Any additional feedback?
0コメント