This is the second SNOM phone I have been using for more than a year. I can not tell I am a fan of it but at home, people like it very much. Again, as my previews review of the SNOM 870, I will not talk about technical specs. I will try to talk about some details you will not find by reading about it on the vendor website. This phone has been discontinued, but you can find it on eBay for about 125 USD with the base or 100 USD only the headset.

The model M9 is a wireless (aka cordless) IP Phone. The phone consists of a base that controls up to two headsets and nine SIP accounts. The signal reach of the base is good, I have tried in a three-level house without issues. This phone has a repeater mode, this means that if you have a really big house, you could put two bases and the headset will jump between them.


Since I have been doing VoIP for a long time now, I think it is a good idea starting to write my experience about using some IP phones. When I talk to people, I always refer myself to this phone as my "trusty SNOM"; in the 4 years I have had it, I can say it has not failed me a single time. With this said, I will talk more about my experience, you can find the tech spec by googling it.

This is the phone I have on my desk for daily use.

First the bad news, this phone has been out of the market for about 3 years. If you want to get one, you will need to get from eBay, Amazon but you will not get it from SNOM directly. 

Because I must work with best IT practices, I decide to install my ticketing and support system. I have known OTRS since 2012. As they claim on their website, OTRS with ITMS satisfies ITIL processes, one of them has to be with Incident Management. OTRS, if installed with the correct add-on, can give support for a DBMS, in other words, it can keep track of your inventory and link dependencies and issues to them. OTRS can be linked to a Nagios system as well.

So, if you invest the enough time, you can have a pretty good ticketing system.

Caching in OTRS allows you to reuse objects that have been used recently. By default, OTRS has a disk cache. However, this could not be enough if you are planning to do a cluster or you just want to speed things up. Fortunately for us, someone coded the Memcached support. So I will talk about how I did this.

In my very specific case, the VPS where I have installed my OTRS is very slow on I/O operations, so putting a Memcached configuration helped a lot!

Disclaimer: I am not the author of this patch. I just did the .patch file more friendly.

Last two weeks I  have been working hard trying to release a new version of the Billing/LCR for FusionPBX software. There are some exciting changes which I will talk about in this post. I encourage everyone to update to this release.

The Tax Logic has changed

Usually, the taxes are taken out from the paid amount. However, this was doing balance calculation very complex, not to mention that there is no a clear way of dealing with this with the different payment processors. The logic now is at follows: when you pay, if there is a tax configured it will be calculated and added to the quantity you want to pay. For example, if you have a 5% tax, and willing to pay 10 USD, you will be forwarded to pay 10.50 USD. This works on all payments plugins now.