Support

Please make sure this is "unset" for them.

It does show all of them, but they cannot access it. Try to click on them, it won't function.

Unfortunately, it's only available on the store.

From here:

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.

Have you set up a group on the extension level, assigned a button on the phone, re-provisioned the phone and then tried to press the BLF button t pick the calls going to that group?

Hi, Hopefully this setting works ?

Thanks for the update. Will update this thread ASAP.

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?

Please update the app to 4.0.5 to get the German language issue fixed.

Hi, This is the latest Android app download URL is here Please keep checking this space if you have any issues with it. Appreciate your feedback.

Yeah, those german texts are being looked into. Please go ahead and test other modules of the app as of now. German texts will be handled shortly.

We don't have a ringtone setting on Auto-attendant for the obvious reasons. But you can also change the ringtone on the extension level.

So why is the "Ring melody" setting not helping you?

It is a stable release. if you face any issues with it, please let us know and we can provide an update to you regarding it. The document still needs to be written about this version as it was freshly created.

Can you check if you're facing the same issue on the Ubuntu App: http://portal.vodia.com/downloads/app/lin/VodiaPhone1.2.5.AppImage

We're aware about this issue. Let us get back to you on this.

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 ).

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.

Hi, 1. You have to be on 65.0.5 version for trying teams out. 2. Please try the code as 5TR-YTE-AMS-MAY 3. Please check the below video to know the complete installation steps.

Can you post some screenshots of exactly what is not working for you?

When you make a query to open up any random website (hence http request) Maybe with http it is not null. For e.g. http://vodia.com

Alright, so your content length might be really 0. But it is sending it to the desired server? How about when you send a Http packet to it? Is the length still 0?

Out logs may not give you the full idea, whereas the system level wireshark trace might, in your case.

Did you take a look at the admin level logs for web server and webclient set to 9 to look at more errors? Is the URL that you supplied here the one that accepts requests?