We have a concept called the "directory interface" not to be confused with the "user directory".<br>The directory interface is a pluggable abstract API that looks and feels like LDAP only you can plug in anything you want to implement the functions. <br>
<br>mod_ldap is a module that registers to this interface and connects LDAP to it. So essentially you load mod_ldap then you use the freeswitch directory interface as you would have used the ldap code and it will carry over.<br>
<br>There is a mod_dialplan_directory who uses the directory interface to ask for a dialplan, and installs the results into an extension. In the case of mod_ldap obviously it allows you to get your dialplan from LDAP.<br>
<br>Now also in mod_ldap, there is some code someone recently contributed to tie our XML interface to LDAP,<br>This is more interesting because then when anything in FreeSWITCH tries to lookup a user, dialplan entry or anything else in our XML config, all the important details are passed to LDAP where it can make a query, pull the info out of LDAP and deliver it back to FreeSWITCH as the XML it was looking for. This allows you to make all of the registrations, dialplan etc real time driven by LDAP, you can also bind a perl or lua script to this operation as well as mod_xml_curl who will turn the request into an HTTP post to a web server to fetch the data.<br>
<br><br><br><div class="gmail_quote">On Wed, May 28, 2008 at 8:09 AM, Michael Jerris <<a href="mailto:mike@jerris.com">mike@jerris.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Currently the directory interface is only used for that dialplan, I<br>
would like to enhance that in the future. The directory dialploan<br>
uses a filter of exten=destination number, and then has name/value<br>
pairs, I will see if I can find the schema we used back when we<br>
developed it, short of that, the code is the best reference on that.<br>
Another option is to use mod_xml_curl and have your cgi back end to<br>
ldap of your choice. This will give you more flexibility to use<br>
other caller information in your ldap lookup.<br>
<br>
Mike<br>
<div><div></div><div class="Wj3C7c"><br>
On May 28, 2008, at 1:58 AM, Faraz R. Khan wrote:<br>
<br>
> First of all- Amazing project. Tired of asterisk deadlocking all the<br>
> time we have been deploying asterisk with OpenSER as the registrar.<br>
> Freeswitch is a huge relief!<br>
><br>
> This is an extremely important feature we have been looking for.<br>
> Asterisk realtime ldap integration is very flaky. I found this page:<br>
><br>
> <a href="http://wiki.freeswitch.org/wiki/FreeSwitch_Dialplan_Directory" target="_blank">http://wiki.freeswitch.org/wiki/FreeSwitch_Dialplan_Directory</a><br>
><br>
> But there are no clues as to the schema, the queries generated and<br>
> what<br>
> exactly it can hold in Ldap. I am also curious to know whether sofia's<br>
> sip registrations, gateways etc can be kept in LDAP.<br>
><br>
> We are basically developing an extensive plugin based control panel<br>
> and<br>
> a Asterisk module is already ready. However, we are writing<br>
> asterisk .conf files for managing asterisk. We would be quite<br>
> pleased to<br>
> develop a FreeSwitch Ldap plugin to manage users,sip gateways, groups,<br>
> features, etc.<br>
><br>
> Though the XML configuration file is extremely easy to parse and<br>
> write,<br>
> pure LDAP integration would be amazing. Any pointers on this would be<br>
> appreciated.<br>
><br>
><br>
> --<br>
> Faraz R Khan<br>
> Chief Architect<br>
> Emergen Consulting Pvt Ltd<br>
> +92.21.529.0381 x200<br>
> <a href="http://www.emergen.biz" target="_blank">www.emergen.biz</a><br>
><br>
><br>
> _______________________________________________<br>
> Freeswitch-users mailing list<br>
> <a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400