![]() We can achieve that by adding the room name as a parameter to the connect function and create a custom options object using the room name: Peeking again in other code that uses this library teaches us that we need to add the room name to the serviceUrl using a url parameter. Somehow, though the jitsi-meet library says that we are connected, we clearly aren't! Browsing the jitsi documentation is, as we saw earlier, of no help at all. Let's open a second window and check if we really have a connection. We are able to connect to a room and display our own video. The code so far can be found here Step 6: Houston, we have a problem! Success again! We are able to render both the video and audio using the jitsi-meet library. The refs are arrays, so we need the first element in the array to get the real ref. Also there is something strange with refs in v-for loops. Notice the attaching of the track in nextTick: we have to wait until the element is in the dom. JitsiConnection ( null, null, options ) function onConnectionSuccess () , init () const connection = new JitsiMeetJS. $ = $ import options from './options/config' JitsiMeetJS. Import JitsiMeetJS from import $ from 'jquery' window. In order to import the config in our file we have to transform it to a es6 module by replacing The directory structure will look like this now: In order to do that, create a new folder in the src directory called options and copy the config file into this directory. Let's download it and include it in our code. We are going to use the publicly available server located at and after some peeking around in other projects it turns out that on every jitsi server there is a publicly available config.js file that includes these options and many more.įor the public server it located at. Currently works only in Chrome and is disabled by default. enableLipSync - (optional) boolean property which enables the lipsync feature.bosh - DEPRECATED, use serviceUrl to specify either BOSH or Websocket URL.For example 'wss:///xmpp-websocket' for Websocket or '///http-bind' for BOSH. The documentation states (although not in the getting started, at the bottom) we have to provide the following options: What to do? Clearly we need hosts settings. When we reload the 'run serve' again we are one step further and get the following error:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |