Vodia PBX

The SoHo is not set up well. You have to keep in mind that the SoHo was supposed to be a training kit/giveaway. A proper Linux setup wasn't the goal. If you want to fix this, it can be done but you really must be firm in Linux to get this done. In the mini the apt-get should work. There the Linux was set up in a different way.

One thing that we will add in the next version is a duration how long the callbacks will be active. For example, it does not make much sense to call back after days of inactivity. That will at least reduce the problem with callbacks getting out of control.

The best way is to set up a free edition for 5.0.10 and try out to be 100 % sure...

The problem could be that you don't have the country code set for the domain and therefore the number matching does not work as expected. Internally the PBX tries to convert all numbers into a global format starting with +<countrycode><number>, so that the matching becomes easy and fast.

No you would really have to list them one by one. There is no pattern possible for this setting.

My recommendation is to always set the country code in the domain settings. That way, the PBX can re-format the numbers into always the same format. For example, 2121234567 and 12121234567 and +12121234567 are the same if the PBX knows that this number must be read in the US number context (country code 1). That makes it easier to match numbers, for example for hunt group alias names. In 5.0.10 we have introduced a drop-down for the settings that you are looking at. ERE are powerful, but not very easy to understand. In 5.0.10 the PBX would internally generate the pattern !([0-9]{10})$!\\1!500! to match the last 10 digits of the number. Then you can just assign the DID as the alias to the account number. For example, "400 2121111190" would mean that the account has the number 400 (which would be the primary number) and 2121111190.

I remember that we had this problem before. I don't think you can fix this with a setting.

It looks like we nailed that one finally. Send me a PM if you want a build or wait for the next release.

The snom ONE mini has an activation code (Mxx-xxx-xxx-xxx). If you loose your license during an upgrade, you can use that code to re-activate your system. If you have trouble doing that or have lost the activation code, you can contact support and we'll dig the information out for you.

You can use the following link to "upgrade" your system: version4.5.1.xml, this should actually work with the mini as well as with other operating systems.

You can define the time when the email is being generated and sent. This is because e.g. some call centers are still busy at midnight and there are better times to generate the statistics. Are you using that feature?

Yes there is no license. You need to get a V5 license from snomone.com.

No, the m9 is different than the other snom devices that's why there is a special setting for the m9. Are you already on 5.0.10? The 720 should be upgraded to 7.3.19 first; the 7.2 version is not suitable for snom ONE and the automatic provisioning.

It sounds like a nice idea at first glance to have a box that has everything inside (snom ONE plus). However they way the snom ONE plus works internally is indeed a challenging setup. However it surprises me that you also have problems with Patton. This setup should be (relatively) simple.

The MacOS version is also available as upgrade. The installer will follow later, please use the 5.0.2 or 5.0.8 installer in the meantime and then upgrade from there.

Having one recording license for the whole system was a mistake. It indeed makes it prohibitively expensive for small installations and too cheap for installations with more than hundred extensions. We have the topic on the to-do list.

Well the latest beta firmware had a lot of cool features but lacked the stability. Hopefully the next general firmware release will combine the stability of the good old versions with the latest features.

Can you call the cell phone from an extension, using the *00<ext> star code? Then that's a good sign that the cell phone call works in principle. Then when that is working, try to call the extension from the outside and see if the cell phone twinning works. If that does not work, then we know the problem is not related to the hunt groups. One "classical" problem is that the service provider rejects the call because the From-header shows a number that is not coming from the PBX. Changing the SIP headers in the trunk and fix the caller-ID to a number on the PBX will then fix that problem.

Probably another case where you have to have to set the SIP headers. Try "Remote-Party-ID" on your trunk for the SIP Caller-ID Presentation.

That most probably depends on the SIP Header setup. Try to use "No Indication" in the trunk for the Sangoma card. This is absolutely okay as the analog line has the caller-ID tied to the cable anyway.

It is important that the preference numbers in the dial plan are distinct, because the processing continues with the next higher preference after the one that triggered the failover. If you have set the country code to "1" then you should be using the pattern "978*".

Well, well... The installation is obviously not so easy. That is another reason to take a look at the web-based console. No installation necessary.

That is caused by the trunk header settings. You can put something like {ext-ani} into the from field and that should solve your problem at hand... However it would have negative side effects for calls were you do want to see the original caller-ID (regular twinning). What is necessary is that the PBX erases the current From-header before sending the call out and set it to the From-header that would be used when calling from the extension. We will fix that in the next build.

Well I don't think that this is supposed to be a lie, but it is indeed not clear. Also when you look at the bundles you can see that automatic recording is not included. Anyway we'll clarify that on the extension web page soon.

In version 4, snom 710 was not available yet; that's why it is not included in the V4 builds. In V5, snom 710 is included.