Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Hi to all I'm using Asterisk 1.4 and I'd like to use LDAP instead of sip.conf... Now you suggest to use asterisk realtime (res_config_ldap) or astirectory?? Can I use one of them with version 1.4? thx On 8/30/07, Gavin Henry [EMAIL PROTECTED] wrote: No probs. On 29/08/2007, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Thank you once again. Will have to talk it over with my prof before upgrading to Asterisk 1.4. The productive system is currently running on 1.2.6. Thanks Abhishek On 8/28/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Sorry for having miss pelt your name twice... Thank you once again for your prompt reply. Is this the correct version of the driver for Asterisk 1.2.x : res_config_ldap-v0.7.tar.gz from the link http://bugs.digium.com/view.php?id=5768 If you use an old version of res_config_ldap with Asterisk version 1.2, I'm pretty sure you'll be asked to upgrade to Asterisk 1.4 if you seek any help via the lists or bug tracker. If you can use the latest release of Asterisk, you should. Thank you for your time and patience, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist:
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Hi, There isn't an astirectory driver for Asterisk version 1.4. So I guess you'll have to use the asterisk realtime (res_config_ldap) driver. cheers Abhishek On 9/5/07, Alessandro Russo [EMAIL PROTECTED] wrote: Hi to all I'm using Asterisk 1.4 and I'd like to use LDAP instead of sip.conf... Now you suggest to use asterisk realtime (res_config_ldap) or astirectory?? Can I use one of them with version 1.4? thx On 8/30/07, Gavin Henry [EMAIL PROTECTED] wrote: No probs. On 29/08/2007, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Thank you once again. Will have to talk it over with my prof before upgrading to Asterisk 1.4. The productive system is currently running on 1.2.6. Thanks Abhishek On 8/28/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Sorry for having miss pelt your name twice... Thank you once again for your prompt reply. Is this the correct version of the driver for Asterisk 1.2.x : res_config_ldap-v0.7.tar.gz from the link http://bugs.digium.com/view.php?id=5768 If you use an old version of res_config_ldap with Asterisk version 1.2, I'm pretty sure you'll be asked to upgrade to Asterisk 1.4 if you seek any help via the lists or bug tracker. If you can use the latest release of Asterisk, you should. Thank you for your time and patience, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear Mr Gavin, Thank you once again. Will have to talk it over with my prof before upgrading to Asterisk 1.4. The productive system is currently running on 1.2.6. Thanks Abhishek On 8/28/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Sorry for having miss pelt your name twice... Thank you once again for your prompt reply. Is this the correct version of the driver for Asterisk 1.2.x : res_config_ldap-v0.7.tar.gz from the link http://bugs.digium.com/view.php?id=5768 If you use an old version of res_config_ldap with Asterisk version 1.2, I'm pretty sure you'll be asked to upgrade to Asterisk 1.4 if you seek any help via the lists or bug tracker. If you can use the latest release of Asterisk, you should. Thank you for your time and patience, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
No probs. On 29/08/2007, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Thank you once again. Will have to talk it over with my prof before upgrading to Asterisk 1.4. The productive system is currently running on 1.2.6. Thanks Abhishek On 8/28/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Sorry for having miss pelt your name twice... Thank you once again for your prompt reply. Is this the correct version of the driver for Asterisk 1.2.x : res_config_ldap-v0.7.tar.gz from the link http://bugs.digium.com/view.php?id=5768 If you use an old version of res_config_ldap with Asterisk version 1.2, I'm pretty sure you'll be asked to upgrade to Asterisk 1.4 if you seek any help via the lists or bug tracker. If you can use the latest release of Asterisk, you should. Thank you for your time and patience, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin.
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Gavin, Sorry for having miss pelt your name twice... Thank you once again for your prompt reply. Is this the correct version of the driver for Asterisk 1.2.x : res_config_ldap-v0.7.tar.gz from the link http://bugs.digium.com/view.php?id=5768 If you use an old version of res_config_ldap with Asterisk version 1.2, I'm pretty sure you'll be asked to upgrade to Asterisk 1.4 if you seek any help via the lists or bug tracker. If you can use the latest release of Asterisk, you should. Thank you for your time and patience, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit:
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.suretecsystems.com/services/openldap/ -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear Mr Galvin, As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. Thanks in advance, Abhishek * * * * On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.suretecsystems.com/services/openldap/ -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.suretecsystems.com/services/openldap/ -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit:
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear Mr Gavin, Sorry for having miss pelt your name twice... Thank you once again for your prompt reply. Is this the correct version of the driver for Asterisk 1.2.x : res_config_ldap-v0.7.tar.gzhttp://bugs.digium.com/file_download.php?file_id=9565type=bug from the link http://bugs.digium.com/view.php?id=5768 Thank you for your time and patience, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: On 27/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin! ;-) As of today I am using the res_config_ldap of Astirectory in my test Asterisk system to connect to a test LDAP database of my University. Things seem to be working fine so far. Now I'm faced with the task of installing this in the productive system. Before doing so, I'd sure like to consider trying the RealTime database driver that you people have developed. Why so? because I trust your judgment. Thanks, but you should still test it yourself. I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. This would mean removing Astirectory module, installing the new driver and loading the new schema into LDAP. In my view, the latter part shouldn't be a concern because the old attributes and object classes (Astirectory) should in no way interfere with the new ones. Besides the old object classes could be deleted from LDAP. Also the former part shouldn't be of much concern either. Nope, you are correct. My only concern as of now is in the installation of the RealTime database driver because the 'readme' file does not say anything about the installation. It only says about the configuration after installation. From the link: http://svn.digium.com/svn/asterisk/team/group/res_config_ldap/ Would it be sufficiant if I were to copy the makefile and res_config_ldap.c to the res/ directory of my running Asterisk and do make; make install? or do I have to do LIBS=-lldap export LIBS ./configure before that? My asterisk version is 1.2.6. This Digium version is for 1.4.x, not 1.2 Thanks in advance, Abhishek On 8/27/07, Gavin Henry [EMAIL PROTECTED] wrote: I see it is res_config_ldap. You'd be much better using the latest version in the bug tracker. On 27/08/07, Gavin Henry [EMAIL PROTECTED] wrote: On 26/08/07, Abhishek M S [EMAIL PROTECTED] wrote: Dear Mr Galvin, Gavin ;-) Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. It's for any LDAP Compliant Directory Server. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. Not really. in the RealTime driver you can specify which LDAP attributes map to which Asterisk Config settings. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. OK, maybe I need to go and read more about Astirectory. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.suretecsystems.com/services/openldap/ -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit:
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear Mr Galvin, Thank you for the links. Had gone through the bug tracker before though. I was specifically referring to the schema for the driver 'Astirectory' and not the one related to the real time LDAP driver for Open LDAP. In the 'Astirectory' documentation there's a file defining the schema for LDAP which is incomplete. By incomplete I mean the Syntax and few other fields are not defined let alone the schema being a static file. I do understand that for Open LDAP a static file schema should be defined. The only reason why I preferred Astirectory over the LDAP real time driver was the fact that there is no mapping required for SIP users and peers. Regards Abhishek On 8/24/07, Gavin Henry [EMAIL PROTECTED] wrote: Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear All, Am happy to say that I've successfully been able to register a SIP user from a soft phone terminal via LDAP. The biggest hurdle that I had to overcome was the LDAP-Asterisk schema. The schema example given in the astirectory installation document is incomplete. Here's are a few pointers in this regard: The attributes have to be defined in the following way. Also tab spaces should be avoided. dn: cn=schema changetype: modify add: attributetypes attributeTypes: ( 1.3.6.1.4.1.23935.5.4.1 NAME 'astUsername' DESC '' SUP name EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15) NAME should be the same as objectIdentifier DESC should be the description of the attribute EQUALITY is the rule to use when doing a search/compare for an attribute value. SUBSTR is the rule to use when doing a substring search (*foo*) SYNTAX is the syntax (i.e., type) of the attribute. We should probably stick to syntaxes: 1.3.6.1.4.1.1466.115.121.1.15 - directoryString (UTF-8 string) 1.3.6.1.4.1.1466.115.121.1.26 - IA5String (ASCII String) 1.3.6.1.4.1.1466.115.121.1.27 - integer (Integer value) The object class has to be always defined as AUXILLARY and never ABSTRACT. dn: cn=schema changetype: modify add: objectclasses objectClasses: ( 1.3.6.1.4.1.23935.5.5.1 NAME 'astSipGeneric' DESC '' SUP top AUXILIARY MUST ( astContext ) MAY ( astSecret $ astPermit $ astDeny $ astMd5Secret $ astDtmfmode $ astCanreinvite $ astNat $ astCallgroup $ astPickupgroup $ astAllow $ astDisallow $ astInsecure $ astTrustrpid $ astProgressinband $ astPromiscredir $ astRegseconds $ astname $ astLanguage ) ) Best Regards Abhishek On 8/16/07, Anthony Francis [EMAIL PROTECTED] wrote: You will need to extend your schema to include all of the attributes that can be used in sip.conf plus the extra ones that allow realtime to store connection information. Please refer to the realtime info at voipinfo.org to get a feel for what your schema should look like. Anthony Abhishek M S wrote: Dear all, May I first introduce myself. I'm a student of HAW Hamburg University currently working for my professor on a VOIP project. We have a Debian Linux system (server) on which Asterisk 1.2.6 has been successfully installed and running. Also the asterisk SIP server has been connected to the PSTN so users could make calls externally. We use Xlite softphone to make calls between users in the network. Currently there are very few users and I have been able to register them in the in *sip.conf *file and declare extensions in the *extensions.conf *file. Now there is a requirement to assign extensions to all students in the university(over thousand) whose credentials and information is stored in the Novel based LDAP database. Moving along I've managed to successfully install astirectory which is a real time database driver that allows to fetch configuration data from LDAP directories. Have also installed the LDAPget module that can lookup data in the LDAP directory. I'm looking for SIP attributes on LDAP or an LDAP schema that would facilitate astirectory or LDAPget to retrieve the username, telephone number and password from the LDAP database to register the soft phone user. I'd be extremely grateful for any help or suggestion in this connection. Thanks in advance, Abhishek ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Please see the official tracker in the Digium buglist: http://bugs.digium.com/view.php?id=5768 Here are the schemas we did for OpenLDAP: http://bugs.digium.com/file_download.php?file_id=14842type=bug http://bugs.digium.com/file_download.php?file_id=14841type=bug Also, for Novell eDirectory, see: http://forge.voicerd.org/frs/?group_id=7release_id=17 Gavin. -- http://www.suretecsystems.com/services/openldap/ ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear all, May I first introduce myself. I'm a student of HAW Hamburg University currently working for my professor on a VOIP project. We have a Debian Linux system (server) on which Asterisk 1.2.6 has been successfully installed and running. Also the asterisk SIP server has been connected to the PSTN so users could make calls externally. We use Xlite softphone to make calls between users in the network. Currently there are very few users and I have been able to register them in the in *sip.conf *file and declare extensions in the *extensions.conf *file. Now there is a requirement to assign extensions to all students in the university(over thousand) whose credentials and information is stored in the Novel based LDAP database. Moving along I've managed to successfully install astirectory which is a real time database driver that allows to fetch configuration data from LDAP directories. Have also installed the LDAPget module that can lookup data in the LDAP directory. I'm looking for SIP attributes on LDAP or an LDAP schema that would facilitate astirectory or LDAPget to retrieve the username, telephone number and password from the LDAP database to register the soft phone user. I'd be extremely grateful for any help or suggestion in this connection. Thanks in advance, Abhishek ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
You will need to extend your schema to include all of the attributes that can be used in sip.conf plus the extra ones that allow realtime to store connection information. Please refer to the realtime info at voipinfo.org to get a feel for what your schema should look like. Anthony Abhishek M S wrote: Dear all, May I first introduce myself. I'm a student of HAW Hamburg University currently working for my professor on a VOIP project. We have a Debian Linux system (server) on which Asterisk 1.2.6 has been successfully installed and running. Also the asterisk SIP server has been connected to the PSTN so users could make calls externally. We use Xlite softphone to make calls between users in the network. Currently there are very few users and I have been able to register them in the in *sip.conf *file and declare extensions in the *extensions.conf *file. Now there is a requirement to assign extensions to all students in the university(over thousand) whose credentials and information is stored in the Novel based LDAP database. Moving along I've managed to successfully install astirectory which is a real time database driver that allows to fetch configuration data from LDAP directories. Have also installed the LDAPget module that can lookup data in the LDAP directory. I'm looking for SIP attributes on LDAP or an LDAP schema that would facilitate astirectory or LDAPget to retrieve the username, telephone number and password from the LDAP database to register the soft phone user. I'd be extremely grateful for any help or suggestion in this connection. Thanks in advance, Abhishek ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Authenticating SIP user in LDAP database instead of SIP.conf file
Dear Mr.Anthony, Thank you so much for your responce.. Did go through the link as I'd done in the past. Would really appreciate if you could give me more specific links that could show a schema examples listing SIP attributes for LDAP. Appreciate your time and patience thanx Abhishek On 8/16/07, Anthony Francis [EMAIL PROTECTED] wrote: You will need to extend your schema to include all of the attributes that can be used in sip.conf plus the extra ones that allow realtime to store connection information. Please refer to the realtime info at voipinfo.org to get a feel for what your schema should look like. Anthony Abhishek M S wrote: Dear all, May I first introduce myself. I'm a student of HAW Hamburg University currently working for my professor on a VOIP project. We have a Debian Linux system (server) on which Asterisk 1.2.6 has been successfully installed and running. Also the asterisk SIP server has been connected to the PSTN so users could make calls externally. We use Xlite softphone to make calls between users in the network. Currently there are very few users and I have been able to register them in the in *sip.conf *file and declare extensions in the *extensions.conf *file. Now there is a requirement to assign extensions to all students in the university(over thousand) whose credentials and information is stored in the Novel based LDAP database. Moving along I've managed to successfully install astirectory which is a real time database driver that allows to fetch configuration data from LDAP directories. Have also installed the LDAPget module that can lookup data in the LDAP directory. I'm looking for SIP attributes on LDAP or an LDAP schema that would facilitate astirectory or LDAPget to retrieve the username, telephone number and password from the LDAP database to register the soft phone user. I'd be extremely grateful for any help or suggestion in this connection. Thanks in advance, Abhishek ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
