Vodia PBX

No that will be another license.

Just ask sales to give you a staging license.

Is this a hosted or CPE license?!

No that would be an additional device to ring. Typically that should not be a problem if all hot desking users use devices which are not called directly and which have dummy extension numbers.

Phone type - no this should be actually automatic (otherwise edit it in the domains phone list where there is a bulk action). Attach voicemails as emails - yet that is a "class" simple setting for an extension that should be no problem with CSV.

We'll add another way in the next version where you can factory reset the device with a USB memory stick.

If you want to try the Vodia soft phone for Windows, please contact support. Maybe that's easier.

Did you (maybe accidentally) enable to auto logout at midnight?

There was a typo in the link in some versions - should be fixed in the latest. In the meantime just manually enter the link please.

If the AuthID is the same like the extension number then you can use the SIP password.

For the range it currently works only with the year. We'll add the feature that is can work any year in the next version.

Looking at the ticket wondering what you are trying to achieve - if you want to see what the PBX sends to the phone you can do this easily in the page where you enter the MAC for the phone - there is lists the files that were sent to the phone. You can click the view button then it shows a pop-up with the content.

There is a setting in the pbx.xml - password_history. It is (currently) not exposed on the front end. It defines how many passwords are stored (max), if you set it to 0 it will not remember any passwords. If you edit the pbx.xml file you will have to restart the service.

Yes if they already exist the information will be overwritten. Powerful feature if you can edit CSV!

I guess "make selected accounts secure" is what you want? Sending out emails with the password will be history soon as this is becoming a no-go for security. The passwords for the devices (associated with the MAC address) are not affected by this. What you always do is use the CSV import to bulk-import values, including new passwords. You can follow the rules at https://doc.vodia.com/csv for this.

Well we can take it out - should we use PAI instead?

There is a setting in the pbx.xml that enabled that (rest_show_passwords, default is false). There are some customers that demand that all passwords are sent to the front end...

Yes - T.38 is almost as complicated as SIP... That is why it makes sense to generate a PCAP trace for this and take a look,

Maybe there was another area where the message could be generated - we'll add that just to make sure. Will be in the next 63.0 - probably 63.0.5.

What version is this? This should be fixed in 63 already.

Listing all the possible numbers is not completely unreasonable - it makes sure that the PBX presents only numbers that are known. Many SIP trunk providers do that, so that they don't have to worry about SPAM calls from customers. The flag in the screenshot above actually controls weather the PBX will rewrite the From-Header to the first account identity or the one that was presented. If you want to keep the from header the other option would be to do a trunk-to-trunk routing where there are no extensions involved. This would be similar to connecting branch offices, see https://doc.vodia.com/trunk_branches.

It is a little bit tricky area because of the way the browser caches the logo image. F5 is usually not enough. In many browsers you need to enter the "inspect" mode and disable the cache.

There is a setting that tells the PBX to keep the From-header untouched (in the domain settings dom_settings.htm). Setting it to "no" might solve your problem. The other possibility would be to assign all possible DID/ANI to the extension I believe the PBX will then try to keep the right one when passing the call on.

Just open a new one - does not cost anything

The warning sign tells you that the HTTP password is not secure. Just set a good password...