Vodia PBX

I assume that the problem was fixed in 5.0.10a. Please use the following link to update: http://snomone.com/downloads/snomONE/version-5.0.10a.xml

Hmm. That looks fine, however the gateway is then supposed to send another REGISTER with the authentication info. Is there something on the gateway that needs to be turned on?! I am not the biggest Mediatrix expert...

The button features generally require that you use TLS transport layer. This is because UDP messages can easily get lost and also because UDP messages have a lot of problems with fragmentation. Maybe that's the problem?

You could just look into the IVR CDR (cdri) or have the PBX send a SOAP request when the pattern matches.

Regular expressions don't care much about numeric values... However it is possible: 99000[1-9]|9900[1-9][0-9]|990[1-3][0-9][0-9]|990400 I hope I did not make any mistake, hope you got the idea

Well the post says "SoHo" (which is not the mini), and there you can access the JTAG without opening the box. We can also recover the mini for you. You'll have to purchase a ticket and send the device to the office near Boston.

G.722 can give you better quality only if both sides are using G.722. If one side uses G.722 and the other G.711, then the resulting quality will be worse than G.711. Transcoding can make the call never make sound better. Transcoding between the trivial codecs such as G.711, G.726, G.722 is not very CPU intense. Even if you have to transcode 50 calls between those codecs, the CPU will be still able to handle this. Only when you are getting into GSM, G.729A or even things like speex, iLBC or OPUS transcoding then the CPU might get under heavy load. The PBX tries to avoid transcoding. IMHO today it is still a very reasonable choice to just leave everything on G.711; especially if bandwidth is not an issue and most (important) calls terminate in the PSTN anyway.

At the end of the day, both SoHo and mini are Linux computers and we gave customers full access. On the snom ONE plus the decision was to lock out people from the shell; that caused even more problems as customers could not even perform trivial administrative tasks. The mini has a reset-button; however that just reset the passwords and the network setup (DHCP), but it does not install a default SSH program. You can still get a JTAG cable and recover the box. This will give you the console, which runs without SSH.

The specs look okay with me. Should be definitively good for 50 calls.

Double or triple check that the password is the same on the Mediatrix and the PBX... Apart from that, also make sure that you either have a "localhost" domain on the PBX or the domain name matches exactly the domain name in the Mediatrix. Do you see the REGISTER message in the log of the PBX? Does it match your expectations?

Inbound can be done relatively easy. The general rules where to send the call apply here. Outbound is a little bit bigger problem. We introduced the parameter for the CO-lines for this purpose. For example, the PBX can send something like line=3 in the request-URI. However I am not sure how the NBE wants the information that tells it what line to use. BTW the inbound CO line seizing can also be done this way.

There is a setting in the trunk that tells the PBX how the provider wants the number presented. It is called "Rewrite global numbers", and you can set it to NANPA 11 digits.

What about 8.4.35? snom 821 has that one also available.

I still don't get the point what you are trying to achieve. Do you want to move your snom ONE mini installation to a Windows-based computer? If yes, then the easiest way to do this is to (1) install a new snom ONE on Windows, (2) make a backup of the snom ONE mini and then (3) restore the backup on the Windows computer. In the LInux world, the easiest is to use tar; however on your Windows computer you must then install a tool that understands the file format.

You cannot run Microsoft Windows on the snom ONE mini.

You cannot upgrade a computer that is running Linux to Windows. Or maybe I don't understand the question?

In defense it has to be said that snom was caught in surprise by the market demand for such an appliance and the devices were sold in no time. The Linux was really not the point. The mini avoids the problems with the AC converter by having it outside and also offering PoE. That was IMHO a smart move. The power supplies are made in the millions, and the quality level is where it needs to be. The low-power components are a lot less critical when it comes to reliability.

The PBX chooses the right OS by itself. The XML file contains all necessary links.

Please open a trouble ticket on the support site (link can be found on the website).

Well 5.0.7 version does not have that problem. Are you using UDP? Maybe packets get lost? If you can reproduce it, a PCAP trace would be great.

If you use CO lines then the PBX will always try to bind a call to a CO line for that trunk. If there are no more CO lines, then it will fail. Can you increase the log level? I guess there must be some more messages that tell us more why it sends "404 Not Found"

We had some older versions with a bug in that area. What version are you running?

Ah... that would explain why the updates did not work. I have no idea how difficult it is to update to squeeze. One thing is clear, don't do that if your SoHo is mission critical!

You can delete the entries in the autocallback directory; however this will require a restart of the system. The next version should not be too far away (if you want to have a build, send me a PM)

When you receive calls from other numbers that are not blacklisted, but in the address book, do you see the name that was entered in the address book? If yes, then the address book matching works in general and the problem is limited to the blacklisting feature.