Updated LDAP server for Innovaphone

Updated LDAP server for Innovaphone devices

Last year we did publish our small ldap server as opensource on git hub.
In the past months we did many enhancements, which added text search capability, more number fields and better support for varios DECT platforms.

If you already use it, we strongly suggest that you upgrade to the new 2.2 release.

If you are providing a hosted environment for your clients, then we have a closed source version of the same software, which can handle tenants for your different clients. Just contact info@aarboard.ch for a quote.

Small LDAP server for Innovaphone PBX

The innovaphone PBX series are small hardware (or virtual systems) which are very powerful and customizable to almost all user requirements.

They also use Internet standard where ever possible.

For number reverse look up and address books, the preferred method is ldap.

In small installations you usually don't have your LDAP server configured to maintain all your contacts and phone numbers, so you are in fact missing a simple address book for your solution.
Of course there exist large ldap servers, like Estos Metadirectory and others, but for many use cases they are just oversized and too expensive.

This gap is now filled with the open source project "inno-thinyldap" which can be found on github.

It has two main functions:
- Forward and reverse look up of numbers against a built in mysql database
- Reverse look up of phone numbers against the tel.search.ch directory

The local mysql address book can be maintained by uploading/download xlsx file containing your contacts and phone numbers.

Give it a try and tell me what you think about it.

PS: If you need the same thing, but usable for hosting/multiple clients in the same installation, get in touch with a.schild@aarboard.ch

Adding more redundancy to postfix with ldap store

When using postfix with a ldap backend for storing user data is a common setup.

There exist a lot of guides on how to do this, for example:

http://www.howtoforge.com/postfix-virtual-hosting-with-ldap-backend-and-with-dovecot-as-imap-pop3-server-on-ubuntu-karmic-koala-9.10

or

http://linuxgazette.net/124/pfeiffer.html

These are good starting points for getting your MTA up and running.
When your business grows and becomes more "mission critical" it's time to look at what you can do to provide moreprotection against system failures.

As you might have seen, in the config file you have to add these ldap host definitions:

domains_server_host =

To protect you against ldap server failures, you can simply specify multiple ldap url's
in the standard ldap syntax.

This gives then:

domains_server_host =  ldap:// ldap://



You can even add more servers to the list if required.
If you use smtp authentication for mail submission, then you probably also have saslauthd configured. To benefit from the same redundancy just modify the ldap_servers line in the saslauthd.conf file too

ldap_servers: ldap:// ldap://


After reloading postfix and saslauthd the new configuration is active