FAQ

• Browsers don't receive the webrtc calls, why?
  • The http port for the external service might not be reachable from Restcomm. Double check that there’s no firewall/security group preventing access
  • Make sure that the Incoming Number in Restcomm Admin UI is properly configured and linked with the correct external service URL and that method is GET (restcomm-test.py handles that automatically through provisioning, but if you have it already provisioned the tool won’t be able to modify it, at least not yet)
• Calls fail for no apparent reason when using chrome, why?
  • Check if a Chrome lock file has been left behind by a previously ill-terminated session. In the chrome logs you should see ‘The profile appears to be in use by process X on host Z’ and the lock file is usually at $HOME/.config/google-chrome/SingletonLock - remove it
• Some calls are failed, why?
  • When making lengthy load tests we have seen that some times the browsers after a while start getting slower to process requests and the tabs aren't re-spawned on time to handle the directed to them.
• Need to configure Firefox to allow javascript to close a window/tab?
  • Set about:config preference dom.allow_scripts_to_close_windows to true. Notice this is insecure and should only be used for testing purposes!