Matthew is a telecommunications industry executive and software developer, but his real passion is building tools to enable people to communicate simply and effectively. He writes software for Microsoft Skype for Business (formerly Lync) as well as Big Data tools for the telecommunications industry.
Creating and Answering Audio Calls In this module, we'll look at the steps required to add participants or contacts to a conversation, and then how to create and answer audio calls. In the previous module, we've looked at how to retrieve participant capabilities, such as the ability to consume audio and video content, and we'll use that now to begin an audio conversation. Coming up, we'll look at how to add participants to our conversation. We'll see how to start the audioService, initiated by the Skype Web SDK. We'll also see how to accept an incoming call invitation that has been sent by our participant. It's important to check the audio and video capabilities of each participant to ensure they can participate in an audio/video call, so we'll see how to check this. And we'll take a look at how to stop the audioService, which stops the audio call. As always, I'll run through a live demonstration of the code we've seen today, which can be downloaded, and then we'll look at a brief summary. Before we can start an audio call, we need to add one or more participants or contacts to the conversation. Earlier in this course, we saw how to search for and create a reference to a contact or person. This reference can be added as a conversationParticipant object to a conversation, as seen here. Another method for adding a participant is to simply add their SIP address or email address. Typically in Lync or Skype for Business environments, users are referenced by this address. And whilst it's mostly an email address that is used, it is technically a SIP address and should be prefixed with sip:, as shown here.
Troubleshooting In this module, we'll take a look at a few troubleshooting tips and useful techniques for ensuring your Skype Web SDK website or application works seamlessly. Firstly, we'll review the prerequisites for the Skype Web SDK. We'll take a look at what hosting environments are supported by the Web SDK and which are not. Domain trusts are critical, so we'll review the cross-domain authorization process. We'll also take a look at the different framework versions. And finally, the Lync Web plug-In and how to enable NPAPI in Google's Chrome to support it. Firstly, let's take a look at some of the prerequisites for the Skype Web SDK. Whilst it may seem obvious, one of the first things you need to do to ensure the Skype Web SDK functions flawlessly is ensure that all you Lync or Skype for Business servers are currently up to date and fully patched with Microsoft hotfixes and all the Lync and Skype for Business updates. Secondly, we'll look at how to bootstrap your servers, and then we'll make sure that your application is fully trusted to use the Skype Web SDK. Always make sure your servers are fully patched with the latest Windows updates, especially your edge servers that may be internet-facing. Microsoft also has a page on the internet where they list all the Lync and Skype for Business updates. This is updated regularly. The link is shown here. Bootstrapping your environment is also critical. UCWA must be installed on every front end, edge, and director server in order for the Skype Web SDK to function. As seen earlier in this course, you simply need to run the Bootstrapper. exe application on each of your applicable servers. It only takes a few minutes, but it is required, and of course, back up your servers before you perform this task.
Closing a Conversation and Signing Out In the final module of this course, we'll be taking a look at how to close a conversation, and finally, how to sign out of the Skype Web SDK. We'll take a quick look at stopping conversations and why you should do this. We'll review best practices when using the SDK. We'll summarize what we've learned in this course. And finally, I'll provide a list of where you can go to learn more about the Skype Web SDK. Firstly, why would we need to stop a conversation? Sure, participants can just close their conversation windows and the conversation is in reality over, but the SDK will keep conversations and connections open on the server, which is inefficient and wasteful of resources and may result in errors in the longer term. As with any client/server application, it is always best practice to close off a connection once it is no longer needed. The final step in any conversation is to stop the conversation, and it's really as simple as invoking the chatService. stop method. This will automatically terminate any audio and video calls.