Vodia PBX

We don't support the CS410 any more. There are a couple of reasons for that. The first and most important is that we were never able to get the multitasking working properly with the Linux (which is also a couple of years old). We had to call yield() all the time all over the code to keep the PBX from freezing. This is like Windows 3.1, and it does not help to have a competitive product in the market. The other problem was that the overall production volume of the CS410 was relatively low. Quality assurance in the hardware world is all about volume or military-grade prices. A PBX should be very reliable, and consequently it is a excellent idea to go for mainstream, high-volume server products if you don't want to risk a downtime of your employees until new hardware can be purchased. Here comes the next problem: If the device breaks, how long does it take to get a new one? If you have a standard off the shelve server breaks, you have a new one the next day or you already have a space one in your server rack anyway. By the time when the CS410 was designed, 128 MB was a lot and a 400 MHz processor was mind boggling. Today, every smart phone has a lot more and so does the CS410 hardware look outdated. If your friend does not want to go for a 19" server, I would look for a small home server or consider a snom ONE mini (at least it has 1.4 GHz). For the PSTN termination I would go for a standard PSTN gateway; they are made in high volume and the quality is great.

None of those I would consider "trivial"...

If they want to switch to version 5, they have to purchase a new key. The old key can be used to get a special discount though (snom ONE blue or yellow).

Seems the only solution right now is to use some external conversion services. At least now it is possible to use custom headers, for example to add a Reply-To header. We have seen a case where an external server did the speed-to-text conversion. We can add other codecs; however they need to be "trivial". Looking at what Windows phone 8 is supporting, I just cannot spot anything less complex than MP3.

There was a bug with the updating of the button, which will be fixed in 5.0.7. Workaround for now it to use the star code.

If you automatically plug and play the device with snom ONE, you can look into the generated folder. There you can see what files where generated; and those files contain the password for the web access.

On this forum, we support snom ONE, not 3CX...

Solution: Use snom ONE

Well the log says that the internal webclient is trying to fetch a file from "". In the context of ActiveSync my guess would be that either there is no server address (or in the wrong format) or the DNS is not set up the way the PBX expects it.

If they don't want to upgrade to 5.0, they can as well upgrade to 4.5.1 where the PBX provisions the recording button on the phone with a XML menu, where they can turn recording on and off. That should solve their problem.

You probably have an older key that needs to be changed. Send us a private message and we'll update the key. Sorry for the inconvenience.

There is a global setting app_user_agent which you may change.

Actually there is already version 5 out. Unfortunately it is not trivial to merge manual changes in.

Well the differentiation between pbxnsip and snom ONE is another legacy that we have or had. We took this out in 4.5.1.1108: http://snomone.com/downloads/snomONE/debian32/pbxctrl-debian32-4.5.1.1108, we will publish the whole set ASAP.

We were not able to test this yet. However we did use version 4.0.2 and it worked okay so far.

Well, a PBX is a PBX and an extension is an extension. So far we did not have too much demand for such functionality and we would have probably to add something to the SIP headers not only on the trunk side, but also on the extension side to make the magic happen.

There was a critical bug in 4.5.1090 in the LDAP area; you should at least upgrade to 4.5.1. No those templates are on system level. For such a general problem like LDAP, I would not make changes in extension or even domain level. Also deleting and creating accounts will not have any impact.

This could make sense if you want to use the SBC-functionality of snom ONE. The biggest catch that I can think of right now is this setup will be bound to one DID only. It will be difficult to assign multiple DID to a single registration.

Hmm. 4.3 is not really the latest, but as far as I remember that feature was added many years ago. IMHO this should also work in 4.3.

AFAIK the regular trouble ticket system is available as usual. P.S. what is PoC?

This is not the last version... we know that the current design can win any beauty contest.

Div: excellent catch. The line below has it right... We'll fix the div tag in the next release. On Chrome I am using Version 25.0.1364.152 too. Maybe this problem is related to some network problems? NAT or firewall involved?

Right, this is for disabling entries. Not sure why that feature was put in. Anyway, it seems that in the dial plan test area the flag is being ignored (should be fixed in the next version); but in the real dial plan processing it should be honored.

Well for this you really have to wait until the snom forum is back up again.

There are several ways; I believe the most interesting should be ActiveSync. But you can also do one-time imports e.g. with CSV. The phones generally use a stripped-down version of LDAP. The data is kept on the PBX.