Vodia PBX

Well if you want to try-and-error those hundred settings you can also do it manually. However is it much easier to just PnP the phone...

We have added a setting for that problem with the hunt group and ACD group pickup in 60.1. This is IMHO cleaner as you can now select which group should exhibit that behavior and which do not.

It is supposed to work... This setting is only a part of it telling the phone to accept phones even if it is on DND (because the PBX is filtering calls, and the phone should respect that e.g. in the case of administrative override "boss/secretary"). You should see a subscription for as-feature-event in the list of registrations for the extension, then that subscription relationship should be there. I do assume you PnP the phone?

The 60.0.3 build will include the required changes. It is actually only a tiny change, the URL has slightly changed. And you will have to make sure that the letsencrypt root certificate is trusted, which is the case if you use the default certificates.

Did you try the extension BLF mode? That does monitor, pickup and speed dial...

Can you call the mailbox (*97) or another extension, if yes that that points at a problem with dialplan and/or the trunk. Can other extensions make outbound calls? Then that would hint at problems specifically with the device.

This seems to be essentially about the URL and the certificate that the PBX needs to trust. We have already changed it in 60.1 (test build) but it seems that the "old" way is still available. There was only a short time window when we had the chance the make the changes. We'll include it in the latest 60.0 version.

You should really upgrade to 60.0. The 8851 phone support was added in that version, getting really the best out of it including support for BLF automatic LAN provisioning and so much more. The phones are great and it would be a waste to use only a basic feature set.

If this is on snom phones, it is probably because the URL is not correct. We have already made a change in the ringtones.xml which should solve the problem.

You don't need to restart the PBX if you change the permissions; might might have to log out and log in again though to create a new session with the updated info.

The PBX has this, though the supported API is at this point only voicecloud.

Yes. One of the next things on the to-do list.

Seems we also needed to upgrade the compiler... Please try again with the latest image.

There was a minor bug when loading the flag. Saving worked, but loading did not... Next build will have that fixed.

Wir mussten das FreeBSD updaten weil unsere Tools sonst nicht mehr funktionieren: [user@freebsd64 ~]$ freebsd-version 11.1-RELEASE-p6

We have already changed that. Now only the last name is required, this is in line what LDAP would expect. Last resort would be to call it "40" for extension 40.

That means that the (end) user cannot change that button from the user web front end.

Maybe the pattern was just missing in the pnp_snom file. You can try to edit the pnp_snom.xml file in the templates web page, like this (notice the snomD31?): <file name="snom_300.xml" encoding="xml"> <pattern mac="8">snom30?-############.htm</pattern> <pattern mac="9">snomD30?-############.htm</pattern> <pattern mac="9">snomD31?-############.htm</pattern> <prefix>true</prefix> <vendor>snom</vendor> <anonymous>true</anonymous> <protocol>tftp,http,https</protocol> </file> We will include this in the next build, so please after updating just revert the file then.

Well the phone should accept the call automatically. In the test environment here they do. If the ringtones.xml got out of sync with the yealink template then this could happen; maybe double check if either file was changed?

There was a typo in the web interface, next build will have that fixed.

It is on the to-do list...

Sounds like a problem with the trunk settings to me. Try filtering in the LOG for the IP address of the SIP trunk provider; there should be some kind of error message on what they don't like.

This was in the old way of doing it before 60.0. The new way is to detect the model using the various HTTP headers. If you can I would suggest to move on to 60.0.

Well did you factory reset the SPA 122?! If you have removed the MAC from the PBX this should be all you need. Or did yo drop anything into the TFTP folder.

Anything in the JavaScript console? Must be some error somewhere