Jump to content

Support

Administrators
  • Posts

    1,000
  • Joined

  • Last visited

Posts posted by Support

  1. Hi,

     

    1. We suppose you're using https for the user portal

    2. Is the mic / speaker access been allowed to the user portal (via the pop up options that it gives) ?

    3. Are you able to hear the other party and calls are being completed fine?

    4. Please switch to incognito window on Chrome to try this too.

    You can always generate ringbacks from the trunk settings if the Trunk isn't providing it, from under our trunk settings.

  2. 2 hours ago, Vernon said:

    Just to provide an example i'm able to loop a phone into a provisioning cycle where i can force the PBX to regenerate the same config file 10,000 times and there's nothing in place that stops this

    You may have whitelisted that IP where the phone resides, and hence PBX might be letting it through.

    If it sees a request from an IP which is not associated with the system it will try to block it.

    Does this page below help?

     

    2.png

  3. We saw the video, thanks for that.

    We tried the same scenario on 65.0.6 (unfortunately we upgraded before we saw this thread and can't go back as it's an overwritten test build) and it worked just fine. We can send a video too, to demonstrate it from our end.

    Did you edit any of the customized template which deals with front end? Maybe welcome.htm file on the PBX? or your browser might be facing issues? Please clear the cache and try again from the incognito window (we see that you were on incognito in ).

  4. ACME Directory URL & DNS provider: 

    The PBX now supports generating X.509 certificates using the ACME protocol through HTTP and DNS challenges. When using the HTTP challenge, the system must be on a public IP address and it must use port 80. When using the DNS challenge, the DNS must have access to the DNS provider (currently DNSMadeEasy is supported).

    When adding a domain, the PBX will attempt to create the DNS entry for the new domain and issue a certificate for the domain. A few days before the certificate expires, the PBX will then attempt to reissue the certificate. When a domain gets deleted, the PBX will attempt to delete the DNS entry.

    It is now also possible to define a DNS name for the system. The PBX will also attempt to generate a certificate for this DNS address, so that the management access to the system can be done through a properly encrypted HTTPS connection.

    If you've had the PBX with domains having FQDN attached on them, and if you turn on this feature, these domains will acquire the certificate as well. No need to delete the domains and import them again.

×
×
  • Create New...