Vodia PBX

Right now that's not possible. However snom is coming out with some changes in this area. Assuming that there will be a support for color buttons, we'll take a look into this.

There was a problem when the URL was not as expected. The PBX expects the URL to be in the form http://ip/snom320.htm, not http://ip/prov/snom320.htm. Or skip it all and use http://ip-adr/prov/snom760-000413123456.htm instead. We have a fix in the next version.

No only the service. A hard boot would not make any difference.

Okay, then the phone should subscribe for MWI. You should actually see that in the registration tab for the extension. Why the phone does not render MWI remains a mystery though. Maybe we can trace it down to the NOTIFY being sent to the phone. Anything in the extension, for example, in the mailbox settings, sending out the new voicemail as email and delete it afterwards? Then that behavior would be perfectly okay.

Did you PnP the 870?

Hmm. Yea that did not work. Actually what if the user accepts the call? Then the callback should be done and the system removes it from the to-do list. In any case a restart will reset the callback list. That is why the list is not present in the file system.

Can you check if there is anything in the directory "autocallbacks"? Take a look at the entries if there is something that makes sense. Quick & dirty solution is to delete the entries (or move the whole directory away) there and restart the system.

Well the Bad Gateway does come from the service provider (ENSR3.0.66.41-IS1). Probably you have to tweak the SIP trunk header settings to make it work. If the provider has a description where he wants the authentication info and where the caller-ID info, it should speed up the process.

Try holding the # key while the phone is booting up. Then you should be able to factory-reset it and then you can set the URL again,

Hmm. The fallback is to use http://1.2.3.4/prov/snom760-000413123456.htm and provide the users username@domain and web password in the QoS/Security tab under HTTP client.

Well, the way the address book was designed (so far) is that the number serves as index in the table. With the cell phone addition, we need to think about this.

I guess in the old times they called that calibration. In order to make sure that the volume on the 821 is okay, call the mailbox. If the volume is okay, then the 821 is okay. Otherwise, adjust the volume with the Volume keys on the handset. Then, if the calls from outside are still too low, then you must adjust the gateway volume as well. Sorry but I am not a Sangoma expert, but there must be some volume settings somewhere that I would just increase. Maybe the calibration is overkill, maybe (without being a PSTN expert) all you need it to increase the gain manually and you are all set.

What is in the settings server? Can you put something like http://ip-adr? And you also need to open the extension for PnP from the PBX domain web interface. It will show that you have 10 minutes for provisioning the device.

If you put a URL like http://ip-adr/prov into the phone, IMHO it should take it. You also have to put the username (user@domain) and password (web password) in there, so that the PBX can send the right settings.

Can you check if you are really running 5.0.9? The usr_recording page should *really* be in. Regarding provisioning, the key question is if any modifications were made to the provisioning templates. Maybe they are in the way.

You can register multiple devices on one ext as a workaround... not unusual in home environments unless you have library, billiards room, social room, guest suites and lobby, kitchen, bedrooms, fitness center, pool, sauna, walk-able closets: then you can probably afford a bigger license

For those who like to stay with the latest and greatest version, we have released the version 5.0.9 It addresses a few problems that we found with 5.0.8. Also it added more features to the web-based console, so that now calls can be terminated, started and transferred. Also it should be possible to see who is waiting in the ACD. As usual, the release notes can be found on http://wiki.snomone.com/index.php?title=Release_5.0. MacOS will follow tomorrow, but Centos32/64, Debian32/64, Windows32/64, ARM are available now.

Yea the last V4 build don't support free anymore (was stopped somewhere in 2012). If you want free, V5 is the way to go.

Does your activation code start with 5 (5XX-XXX-XXX-XXX)? You can get a code from snomone.com, also for free. The version 4 codes don't work with version 5.

Oh for new installations you need to use version 5. Also keep in mind that the libraries might be a problem as the version 4 build uses some relatively old stuff. You can test with ./pbxctrl -version if the executable is able to run on the system.

Well when registration fails, the system has already re-sent the REGISTER messages many times (500 ms, 1 s, 2 s, 4 s, 8 s, 8 s, 8 s). Giving it a "break" for 60 seconds does not sound unreasonable to me. You also have to keep in mind that too many registrations may be DoS for the registrar. The key question here is why the registration fails so often. If other trunks stay up all the time that is a hint that the internet connectivity is stable (which is usually the problem); the only think that I can think of is that the registrar expects the registration on a different IP address for fail-over or load balancing purposes, which causes problems. Also you have to keep in mind that the DNS server might also play a critical role in this game. In order to rule that out I would out an IP address in the outbound proxy to see if that could be the issue.

If you are running a version 4 free on a snom ONE mini, you can also upgrade with a discount to version 5. The MAC address of the device serves as coupon code in that case--the license will be bound fixed to that MAC.

The PBX re-registers depending on what it is being told by the registrar. However you can override that (did you already?) with the "Keepalive Time". Then you can be 100 % sure this is not a problem with a too short registration interval.

Oh it seems you actually have a very old model that was still using the name "snomONE-ctrl". You need to edit the /etc/init.d/snomone daemon start-up file and change the "snomONE-ctrl" into "pbxctrl".

Call recording is usually quite expensive with other solutions. The snom ONE price is comparatively low...