This article will help you to collect logs from Web SDK and Web RTC.
How to get Web SDK logs
First, you have to enable logging. To do so, specify the showDebugInfo parameter while initiating an SDK instance:
Logs in Developer Console
While using a Web SDK app in a browser, open the developer console and click the Levels dropdown to check Verbose.
In Chrome, press F12 or
Ctrl+Shift+J(Windows, Linux, Chrome OS).
In Firefox, select "Web Console" from the Web Developer submenu in the Firefox menu (or Tools menu if you display the menu bar or are on Mac) or press
Ctrl+Shift+I(Windows) or press
In Safari, enable the Develop menu in Advanced preferences: Safari > Preferences > Advanced > Show Develop menu, then choose Develop > Show Error Console.
Now, reproduce your issue, right-click on the console panel, and choose "Save as…" to save the output to a file.
Do not forget to send the result file to our Support team if needed.
Logs in Browser
To see logs in the browser main window, use either Chrome or Firefox browser. Depending on which one of them you use, open "chrome://webrtc-internals/" or "about:webrtc" URL respectively.
Next, open the Web application being debugged in a new tab and reproduce the problem.
Finally, go back to the logs tab and save them as Web Page, Complete.
For those who want to organize logs in a special way (e.g., collect them in a database for further analysis), we've got a demo called log-collector, that is available freely on Github.
The demo allows you to collect logs about calls state and send them to your backend server. What backend server to choose is up to you, the demo works fine with all of them since it sends POST requests and uses no black magic.
How to get WebRTC logs
WebRTC logs help developers and Voximplant technical support in case of issues with audio or video connections. Right now only Chrome and Firefox web browsers can create such logs, and this article provides a step-by-step guide on how to download them.
Chrome web browser
- The browser tracks and logs all WebRTC connections, so close all tabs and restart the browser.
- Open a new tab and point it to the "chrome://webrtc-internals/" URL.
- Open the Web application being debugged and reproduce the problem.
- Go back to the "chrome://webrtc-internals/" tab, there will be at least two tabs:
- GetUserMedia Requests and https://your/appllication/url. You will see logs along with stats graphs.
- Choose the tab with the name of your application and save the page content as Web Page, Complete.
Stats graphs are not available in the saved file! We recommend either analyzing graphs while being on the chrome://webrtc-internals/ tab, or making screenshots for further usage.
Firefox web browser
- Close all tabs, open a new one and point it to the "about:webrtc" URL.
- Open the Web application being debugged in the new tab and reproduce the problem.
- Go back to the "about:webrtc" tab and save the page content as Web Page, Complete.
How to debug remote clients
Learn how to collect logs about the state of calls and send them to your backend server using the Voximplant logs collector.
Here is how you can make the module serve your needs:
- Clone this repo.
- Go to the Applications section of the Voximplant control panel and click your application.
- Switch to the Scenarios tab and create a new scenario. Paste the code from the
Scenarios.VoxEngine.js filehere, then save your scenario.
- Go to the repo folder, open
logger.js, and paste your backend server hostname in line 43. Save the file.
index.htmlin any browser.
- Fill in the username and password fields, e.g.:
- Start an outbound call or answer the inbound one.
- When you need to send your logs, push the Report button.