Vodia PBX

If you need a certificate try to move to 60.2, there you can just use letsencrypt to generate one for you free of charge.

We introduced a setting in 60.2 where you can easily set the MAC address prefix, but that was not available in 60.0 yet.

Depending on how old the installation is, the executable might still be called snomONE. If that is the case you will have to rename it to pbxctrl to make this work.

The 60.0 version has already the new Yealink MAC addresses listed. If it does not please update to 60.2 which will be available today.

This might take two or three weeks.

The domain name (if you have set the DNS record) should be enough. Though we don't have the Aastra phones in 60.1 yet.

Well, we are not operating the snom redirection service. IMHO it would have been easier to keep everything backward compatible plus we don't see a reason why it cannot be backward compatible. Anyway we have to deal with the situation.

Hard to say, looks like a problem in the SRAPS end. When registering a phone, the API returns "Ok" and shows the (unknown) provisioning profile. As far as we know there is no way to assign profiles through the API in snom SRAPS like Yealink does (http://wiki.snom.com/Category:HowTo:XMLRPC_Redirection#redirect.getPhoneRedirection).

Actually at least snom, Grandstream and Yealink have a recording function on their buttons. Right now we have it for ad-hoc. They way this works is a INFO message with a special header; we need to try if the PBX can actually send it to tell the phone that recording is on.

The system detects that it is one of the extensions calling into the system and plays that message. So you want that the call goes into the mailbox or should the call be treated just like from any other number?

You can see that directory in the status web page of the pbx (reg_status.htm), it is called "Working Directory". If you are looking for pbxwebai, that folder is not there by default; but you can just create it in the working directory.

IMHO the best way would be to control the BLF for the recording mode. It might not work with every phone, but that would IMHO the most intuitive way to signal the user.

Check out https://vodia.com/doc/click2dial this should be pretty straightforward.

No Vodia PBX is not based on Asterisk. IMHO the Asterisk integration must be linked to a Asterisk distribution, e.g. FreePBX or SwitchVox as the pure Asterisk does not come with much around it. But Vodia has a complete REST API, which means that anything you can do from the web interface can be scripted e.g. with curl.

There is some info here. The way this works is essentially that the call is classified "anonymous" so that the standard handling of anonymous calls can take place which we had for years.

Did you try user mode?

How about snom M-Series? They had fairly large installations with DECT.

Exactly. You can control it on per-group basis.

The pattern does not make any sense to me... If you want to get the last 3 digits after the prefix try !555198([0-9]{3}$)!\1!t!0 Dial plans answer the question on which trunk an outbound call should end up and what number to dial. There is no way to do additional things like enabling trunks.

Everything goes through the API, you can always take a look what the browser sends to the PBX after you press the import button and then do the same from your script. It is all REST.

Well 60.1 is a pretty good version, however not a "released" version (daily builds). dom_adrbook.htm should be still there... You can use the CSV import button to import in bulk.

No we do release notes only for the "full" releases. We try to make them more stable than the in-between builds.

This is obviously not good... There were some situations where the PBX would not recover from HTTP client problems but in 60.0 they should be solved?

Why not just keep the software up to date? There are a lot of new models, features, ...

We have now made 60.0.3 for CentOS, Debian and Windows the rest will follow today.