I don't remember the exact details of the metadata as it's been awhile since I've looked into this. This is what people at work here have done and it works ok. Then figure out what you need to change in the metadata and then 'add' the metadata to your API created calendar entry yourself. The best approach is the generate a 'Skype' meeting manually then dump the added metadata. If you have Skype installed, you can also join any. ![]() If you need to create a 'Skype' meeting Calendar entry, then we run into the problem in that the metadata for these calendar entries is not documented by Microsoft anywhere (that I have found). If you dont have Skype installed, install Skype, then select the conversation link again to start chatting. ![]() Or, another member of the Event team can click Invite More People in the Skype for Business meeting, and then select the Skype for Business on Mac user in question. When you do this, the Skype for Business on Mac client should join the meeting. Once you have created a Skype user conference you will have the meeting URI to point people to. To resolve this issue, refresh your browser. To create a Skype meeting you can use the UCWI API here (or if you are doing everything within a web browser you can use the WebSDK, which is a wrapper around the UCWA API here). So you don't need to create a Office Calendar Entry to create or use a 'Skype For Business User Conference'. ![]() The Office 'Skype Meeting' Calendar Entry has 'extra' metadata pointing to the 'Skype For Business User Conference' (including the URI). They know nothing about the Office Calendar Entry. The 'Skype For Business User Conference' is what the meeting URL points to and what 'Skype' clients know about. First thing you need to realise is that there are two different systems involved.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |