Vodia PBX

We are actually coming up with a few changes in this area. You can select what other users you want to see (favorites) and the domain admin can also set up groups that control what users are shown to the user.

Registration is a pretty basic feature. I would be surprised if the firmware would have such a fundamental change. Do you see a REGISTER message showing up on the PBX?

Please keep in mind that "call waiting" is a feature... You can actually disable call waiting for that extension as a workaround, maybe even as a solution.

Well all we need is a VM where gcc can cross compile to that architecture. There are some downloads at https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads now sure which one would be the one.

Thanks. We have a few things on the to do list regarding easy of use. The scope of the mobile version of the app is different from the desktop because of the screen size. Attendants typically use the PC version, while occasional users prefer the mobile version where things like transfer occur a lot less ofter.

Looks like this is a https://en.wikipedia.org/wiki/AArch64 64 bit ARM. Would the code for Raspberry Pi run there? BTW if you want to have a router with a PBX on it, you can also use the Vodia IO.

Nono this was released shortly after the post.

There were version where that was a problem, however this should be resolved in the newer versions. What version is this?

Looks like both sides of the call are jumping on T38 as soon as the FAX tone is being detected, resulting in a conflict. In the mailbox setting on the extension there is a setting at the bottom for T.38, try to set this to "after 3 CED tones". Then the provider will win the race and hopefully both sides can agree on T.38.

Keep in mind 67.1 is our beta build.

The many options on what to show in the BLF in the previous version overwhelmed users. Generally speaking, a blinking BLF means that you can pick up the call. DND may be an exception, there is a generally accepted "hack" interpreting the dialog XML that if the ID is "dnd" the phone is free to render something that indicates DND. However IMHO it should jus show a solid red light.

You can book multiple conference calls at the same time in a conference room. The conference ID will make sure that they cannot hear each other. That was supposed to be a feature since day one... And of course this should not crash the PBX. We'll check if it works as expected on our end.

Well the whole area is already redesigned for the next release... Which is also working on Safari. However it is not released yet.

Does that account have an email address? And does email sending work in general on that system? Also does the license in the status web page show under "Additional license information" the word "Fax2Email"? If that is all the case I would turn logging up and see what the PBX has to say when the FAX hits the mailbox.

You will need at least version 67.1 for that — a new build is available from last Friday. Only CentOS64 and Debian64 at this point.

If you are using Vodia IOP; you would have to enable SSH from the web interface. Then after that set the admin password again, which will be also the password for root (make sure you are in 67.0.3 or later). On Vodia IO things will get a little bit more tricky because there is no easy fix system access. On all other OS, yes use whatever mechanism you used to install the PBX also to access the file system.

In the provisioning history you can see what was sent to the phone. It makes sense to use a XML checker to see if the format accidentally is not well formed (easy to make typos). Does that file look like what you would expect?

Sorry we always validate the certificate on SIP TLS connections that are initiated by the PBX.

Just put it into the tftp directory. Probably the directory does not exist in the working directory of the PBX, so just create it. You can then fetch it with tftp://192.168.1.2/x42.12.0.7275T20200914120531.z. BTW you can also use http://192.168.1.2/tftp/x42.12.0.7275T20200914120531.z., Fanvil does support HTTP as well.

Depending where you are coming from you might have to change the setup on the bandwidth portal. They had an old API that was replaced with a newer one, which we are using now. We are now at 67.0.4.

You can use CO-lines with the trunk and set them to inbound and outbound only. That will limit the number of calls. That being said we have every intention to get rid of the CO lines because this is concept of the last century. It might make sense to add a setting to the trunk that just lists how many inbound and outbound calls are allowed. On domain level, we already have a limitation on how many calls can be on a trunk, however this now does not differentiate between inbound and outbound.

In the next version we will use spaces. This is what pretty much the whole world is using today to make phone numbers readable. Except for USA, the area code also seems to be without parenthesis (and actually it often shown even if you are in the area). We'll have this "marinate" in the 67.1 build for some time and then we will eventually make this version 68.

Its on https://doc.vodia.com/docs/login#admin-password-reset — happens all the time!

Most installations don't leave tenants to change the DID at all. IMHO that is not too bad because those DID changes are rare (which means that they don't cost that much time) and tenants usually don't have the expertise to deal with the topic. However I agree the DID management can be improved. We have added a property to the DID that links it to a trunk, which makes a lot of sense, and yes it might make sense to further link it to a domain as well.

We have addressed that problem already in the code, however it is not available in a release yet. A short-term workaround is to remove the calls window altogether through the customization.