Changes

* OS & Firefox version at both ends of the call* Date and Time of the call* Any Console ErrorsThere are some options/Warnings:** If you're using the pop-up window (receiving a call), then open the Browser Console (under Developer in the Application menu)preferences that will help with debugging issues with Loop. ''As this is We are working on exposing more of the console for failures via the whole browser, there may be unrelated errors & warnings in hereUI, but if in doubt as these are likely to what is relatedcontinue to be useful, include as much as possible''.** If you're using the website (initiating a call after clicking on the link), then open the Web Console (under Developer in the Application menu).* about:webrtc information** Visit about:webrtc in a new tab, at the bottom press "Connection Log"** Copy & paste the information to a new file & attach to bugespecially for developers.

* Visit about:webrtc<code>debug.websocket</code> (true/false)** At This enables debug for the bottomconnection activity between client and server when connecting a direct call, press "Start Debug Mode"or an original call-url based call.** After a few secondsThis shows information as to what stage the connections have got to, select "Stop Debug Mode"and reasons as to why calls may have been rejected.* <code>debug.sdk</code> (true/false)* A file is saved into your temp directory* Turns on debugging of the [https://tokbox.com/opentok/libraries/client/js/ OpenTok sdk]** On Mac it This is most useful for debugging if issues are occurring within the sdk, e.g. video/audio setup issues.* <code>debug.dispatcher</tmpcode> (true/WebRTCfalse)** This logs "actions" that are generated in the UI.log** These are to aid developer diagnostics of the flow of information around the flux-based system.** Currently only the direct calling outgoing window uses flux.* <code>debug.loglevel</code>* Copy *  === How to turn on debugging === ==== Firefox Desktop ==== Go into <code>about:config</code> and search for the saved preference, prefixed by <code>loop.</code>. Then set the value to appropriately. For example, for <code>debug file and keep it safe.websocket</code>, in case it set the preference <code>loop.debug.websocket</code> to true. Debug output is needed to be analyzed shown on the Browser Console (it not the web console), accessible from the Tools -> Web Developer menu. ==== Link Clicker UI ==== This is quite bigthe standalone UI, so if sending/uploading itshown when clicking a link. To turn on debugging: * Open the Web Console (accessible from the Tools -> Web Developer Menu)* In the line at the bottom, (with the '>' symbol) enter:  localStorage.setItem("debug.websocket", true); * (or use the values appropriate to the pref you may want to zip set.* Debug output will then appear on the file firstwebconsole.* The preference value will stay set, until you clear the site's local storage or manually enter:  localStorage.removeItem("debug.websocket");