Chrome problems with phone.html . "NotAllowedError"

Discussion in 'Web Call Server 5' started by mbedial, Feb 14, 2020 at 8:58 AM.

  1. mbedial

    mbedial Member


    We are having problems using the flashphoner-api-0.5.21/phone/phone.html example. When the call is starting, and before the microphone permission is asked, we are getting:

    name: "NotAllowedError"
    message: "Permission denied"

    This problem occurs only with Chrome. What should we do?

    Thanks in advance
  2. Max

    Max Administrator Staff Member

    Did you test page over https? WebRTC does not work over plain HTTP. Make sure you test over https.
    Please provide a screenshot and full code sample, browser console output.
    Here you can find samples' docs:
  3. mbedial

    mbedial Member

    Hello !

    When we test the page over https with our self-certificate , we obtain the following ERROR once we try to do the call.

    Here i attached our code , we have made some modifications and of course values like URL server, domain , passwords... has been changed by XXX because is private information.

    There are some comments in the code explaining what we have added to the original code.
  4. Max

    Max Administrator Staff Member

    Good day.
    We checked your code sample on our test servers.
    When choosing country code from dropdown menu, the call is established correctly from Chrome 80, for example we call to number 10007 on our OpenSIPS PBX:
    So WebSDK part of code sample seems working.
    However, there are some issues with country code definition:
    1. The country prefix passed with query parameters such as https://wcs:8888/client2/examples/test/phone/phone.html?number=10008&password=password&prefix=1 seems to be ignored:
        input.addEventListener('change', function(e) {
        prefijo = iti.getSelectedCountryData().dialCode
    2. Synchronous XHR issue occurs
    3. jQuery cannot get clients ip address to check clients country code
    Those issues concern intlTelInput JS plugin integration and should be probably addressed to its developer

Share This Page