Vodia PBX

The PBX tries to bind to the sockets like 80, 443 which are protected sockets. In Linux, that might take a while if the socket was in use before and there are connections in wait state. This is an open issue; unfortunately not an easy one. Workaround is to wait for at least 60 seconds before restarting the service on Linux.

I would not recommend XP any more, this OS is not even maintained any more I believe. I am not sure if Windows 7 64 or 32 bit have different price tags; if they have I would definitively choose 64 bit. The question with the number of TCP connections surprisingly never came up. Maybe this applies only to Microsoft products like IIS.

Seems like the issue was not even related to the m9. There was generally the problem that the last extension that wrote the MAC "won". This is something that we need to address in 5.0.11.

You can use it; however the provisioning works only when you open the extension up for PnP. Unfortunately we did not find out how to store the web client credentials in the device, so the PnP experience is not really there.

I think the change to use the MAC address in all configurations might have caused the issue.

Hmm.. What is the Provisioning Server? And the HTTP Client User and Password? Also, can you drop the attached file into the html folder and see if that solves the problem? snom_m9_settings.xml

Can you check the generated folder in the working directory of the PBX if those 4 extensions were actually provisioned into the m9? In theory, they should show up in the snom_m9_settings.xml file.

I think for Android you can check out Sipdroid. I would not bet on presence of BLF on soft phones. But you can cobine this with the web-based attendant console information that you now get with version 5 when you log in as user.

Absolutely. If you are a Windows person, you might also check out Hyper-V.

Regarding redundancy there are several ways to go. The best performing way is to run the PBX host in a virtual machine and run it exclusively on a hypervisor. Then use a tool that have the VM automatically failover to another machine when the primary server fails. That can work within seconds and calls can stay up. However the disadvantage is that this requires an expensive license on the virtualization side. If the failover does not require such a fast failover, you can strip this setup down and have a server on standby. For example, you can take a snapshot of the VM from time to time and restore the snapshot on the secondary server in case you have to. This will have the advantage that you keep the configuration exactly the same, including IP address and even MAC. If you don't want virtual machines, you can do the same with physical machines. Then rsync is your friend. When the primary server goes down, you have to start the PBX process on the secondary server. However our experience is that changing the IP address of the secondary server creates a lot of problems and that it is easier to use DNS to point to the active server. Consequently, your DNS server must be very stable, too. And you must provision the phones with DNS, not the IP address of the PBX. Some DNS hosting companies offer the service to poll the primary server and then automatically change the DNS settings to point to the secondary server. But even if you just make regular backups and have a secondary server available, this relatively cheap setup can be effective. If people who are watching the system know what steps need to be done to restore the service on the secondary servers, the failover can be done within lets say an hour. This is much better than waiting several days for a new server and in many environments already okay.

Navigate in the web interface into the domain, then click on "Customize". From there you can select "PnP" and there the snom_3xx_fs.xml.

You can not just edit the template for snom_3xx_fs.xml. You can make these changes on system, domain and even on extension level. This makes it possible e.g. to try out firmware versions on one or two phones before rolling it out to all phones. This was not possible before.

Check out http://snomone.com/support

Well the country codes makes it possible for the PBX to read the numbers the way people do. We should add something to the domain overview to make this important setting more visible.

80 MB sounds a little high for a snom ONE mini but still reasonable. Maybe you can open a trouble ticket with login information and we take a look.

Hmm. It seems there is a API function that needed to be compiled in a different way. Interesting that it worked before?! Anyway, please try the following link: http://snomone.com/downloads/snomONE/win64/pbxctrl-v5.0.10e-64.exe Obviously this is a beta image that requires a manual upgrade (rename to pbxctrl.exe in the working directory).

UTF-8

We hear good things about the new firmware; however it has not been released yet and we did not have the chance to take a look at it.

Send us a private message with the MAC; then we'll dig out the activation code for you.

I hear good things about the new firmware, but we were not able to try it out yet.

Does this problem relate to the PSTN termination or to the dial plan on the PBX? If it is for the dial plan on the PBX: If you have a country code set, the PBX presents the number in a normalized format to the dial plan, in case this is a domestic number it is always in 10-digit format (no matter if the user dialed 10 or 11 digits). As for the PSTN termination, the trunk has a settings that tells the PBX how the trunk provider would like to have it. Many POTS providers prefer to have the number in 11-digit format, so that they can know that this is a domestic call.

Try !99000[1-9]|9900[1-9][0-9]|990[1-3][0-9][0-9]|990400!123 123 is your destination.

No please no 32 bit. Maybe you have to install the C++ runtime libraries. It is strange, those kind of problems are so far only known from Windows XP.

No trace enclosed... But anyway make sure that the Patton is enabled for T.38 and starts the T.38 Re-INVITE after receiving the CNG tone.

Well, the Wiki should contain the settings that you need to set in the Yealink web interface to get them going. Don't forget to open the extension for PnP for 10 minutes.