This set of files adds a working Directory for your Cisco IP phone. It has been tested on my Cisco 7970 phone, but does not use any additional features, so it should work on any of the other Cisco IP phones that support XML services, such as the Cisco 7960.

It adds the following Features:

* Directory button now works!* Works with Contacts from the Pluto phone directory* Paginates them based on # of entries in phone book* Shows the phone type.

Nice and simple.

== Installing this Patch ==

* Unpack the files to the pluto-admin directory. (/var/www/pluto-admin/)* edit the file /tftpboot/SEPDefault7970.cnf.xml (it just needs to be the default xml for your cisco phone, adjust as needed.)** Find the <directoryURL></directoryURL> tags, and place '''http://192.168.80.1/pluto-admin/directory.php''' between them.* Reboot the phone by pressing the settings button, and pressing the following button sequence '''**#**'''

Once the phone boots, try the directory by pressing the Directory button!

looked at the code, seems reasonable. What i see messing is some kind of a search functionality. Let's see if i find the time to implement it. I'll test the code these days.The 7970 has some nice additional features. It plays/sends RTP streams, it should be easy to implement intercom, burglar voice bashing, announcements and so on..

I deliberately didn't implement the Search functionality. But if someone wishes to implement it, cool. I wanted to avoid the stupidity of having the search feature be the primary way to use the system, especially from the telephone. This is not an enterprise services directory, and should not be searched as such.

I deliberately didn't implement the Search functionality. But if someone wishes to implement it, cool. I wanted to avoid the stupidity of having the search feature be the primary way to use the system, especially from the telephone. This is not an enterprise services directory, and should not be searched as such.

you are absolutely right for a few entries. But my personal addressbook alone has at about 120 contacts. If i dig into this i will do some option switches or put the search function in the services menu...

Aha, well, my LDAP is just a front to a Postgres DB (via DB-link). Maybe another argument for porting LMCE from MySQL to Postgres. Or perhaps a better argument for setting up a MySQL datamart for Postgres data (perhaps via DB-link). I'm not dropping Postgres, because too many other existing apps depend on it.

I already have an LDAP server running with a directory of contacts in it. Can I use this patch to connect to that existing directory?

not this patch but the modifications are minor: simply exchange the mysql select with some kind of ldap_search and iterate through the result entries.

Or perhaps change the MySQL select to a Postgres select. Or the ldap_search call you mention, as a start down the road towards a hybrid Postgres/MySQL glued together with the existing DB-link between LDAP and Postgres.

Any of the possible combinations among the three seem an equal balance of interface function and kluge . I wish there were an app that generically synced different schemas in each of MySQL and Postgres, allowing queries on one to reach the other, without building the glue for each different schema.