Back to all discussions

  •   over 4 years ago

Full Conference Web App not working

Hello,
I am setting up Full Conference Web App, referred link https://docs.dolby.io/communications-apis/docs/full-conference-web-app, and github repo of Frontend and backend. Both app started successfully as per logs in terminal.

Front end logs:
[./node_modules/html-webpack-plugin/lib/loader.js!./public/index.html] 1.22 KiB {0} [built]
[./node_modules/lodash/lodash.js] 531 KiB {0} [built]
[./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {0} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
i ｢wdm｣: Compiled successfully.

Backend logs:
$ yarn start
yarn run v1.19.1
$ node src/app.js
Running https server on port 3500

When I open frontend in browser, I get water surfing background with few options like text box asking "Conference name" and "Your name". But after entering those details, I navigate to next page having same water surfing image, but I dont see any options related to audio, video conferencing, screen sharing option etc. I only get water surfing image. I also checked terminal and did not get any error logs.

Can someone please help with respect to this issue ?

Regards,
Amit

  • 4 comments

  • Manager   •   over 4 years ago

    Amit, thanks for your question.
    This complete application requires that you build both the frontend and backend apps. The backend app creates a localhost token server, it requires ssl certs and some and additional configuration. It's beyond our scope here to address troubleshooting that backend config. Each app has its own setup and config.

    Build a token server:
    I will suggest you swap out the backend token server by deploying this example:
    https://github.com/dolbyio-samples/communications-api-token-server-netlify
    - once deployed you'll have a live site, open that up and click on the link you should see json containing a token. refresh and it changes. Copy the URL from the browser address bar. Save this for the next step:

    Next from your terminal open the project root, cd to the frontend folder:
    Run the command:
    yarn install

    By default, your frontend application will make REST API calls to the same hostname and port where your frontend is available. To change this behavior, set the environment variable AUTH_SERVER : in the command below replace with the url you saved in step one.

    From the terminal: (without the <>)
    export AUTH_SERVER=

    Finally run the command
    yarn run build

    This will create a DIST folder.
    From there you can run the app using a basic server npm serve (for example)

    When you decide to host the app, you may need to config you env variables on the server to reflect the AUTH_SERVER url.

    Line 18 of the VoxeetConference.js is where that value is read in the app:

    const AUTH_SERVER = process.env.AUTH_SERVER || "";

    If you host the app on Netlify or elsewhere setup the env var for AUTH_SERVER as the key and as the value. (without the <>)

  •   •   over 4 years ago

    Hi Dan. So a token server provide a way to initialize your Dolby client side app on the server side, so you don't have to include your keys in the client side (browser page) initialize() call to the Voxeet SDK?

  • Manager   •   over 4 years ago

    Yes, that is the basic concept. Tokens expire and are easier to manage via a server / serverless function.
    Take some time to review the documentation. https://docs.dolby.io/communications-apis/docs/initializing-javascript

  •   •   over 4 years ago

    Excellent, thanks!

Comments are closed.