[asterisk-bugs] [Asterisk 0013861]: ERROR[23999]: res_config_ldap.c:1292 update_ldap: Couldn't modify ... Undefined attribute type

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13861 
====================================================================== 
Reported By:                scramatte
Assigned To:                blitzrage
====================================================================== 
Project:                    Asterisk
Issue ID:                   13861
Category:                   Resources/res_config_ldap
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-11-07 11:24 CST
Last Modified:              2009-01-28 16:22 CST
====================================================================== 
Summary:                    ERROR[23999]: res_config_ldap.c:1292 update_ldap:
Couldn't modify   ...  Undefined attribute type
Description: 
my Asterisk return me this error on SIP register :

ERROR[23999]: res_config_ldap.c:1292 update_ldap: Couldn't modify
dn:cn=200,ou=Telephony,dc=example,dc=com because Undefined attribute type

In spite of this message I can call and receive calls.

I haven't got more details ... 
I've run Asterisk  with  -vvvvvvvvvvvvvvvvgc    


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013660 Provide working demo users for ldap/rea...
related to          0014334 Documentation for configuration of res_...
====================================================================== 

---------------------------------------------------------------------- 
 (0098995) jcovert (reporter) - 2009-01-28 16:22
 http://bugs.digium.com/view.php?id=13861#c98995 
---------------------------------------------------------------------- 
Let me try to more clearly state this.

LDAP is tree structured.

Each entry is at a point on the tree defined by its "dn".

For example, dn: x=a, y=b, z=c, dc=mycompany, dc=mytld

Whenever any program searches an ldap database, it specifies the starting
point, or "base" within the tree at which to begin the search.

If the base is "dc=mycompany, dc=mytld", then all of the tree beginning at
that point will be searched for the requested matches.

I wanted to be clear that the example, which has a portion of the tree
named "ou=sippeers", does not create a relationship that restricts the
search to a part of the tree.

When we specify

sippeers => ldap,"dc=mycompany,dc=mytld"

we say to search all of the tree beginning at that point.  The
"ou=sippeers, dc=mycompany, dc=mytld" portion of the tree will be searched,
but so would the portion "ou=foobar, dc=mycompany, dc=mytld".

We could specify

sippeers => ldap,"ou=chicago,dc=mycompany,dc=mytld"

and restrict the search to the chicago organizational unit (which might be
a smart idea if we have a corporation-wide database, and only want to pick
up the entries in chicago into the chicago asterisk PBX).

In addition to the base, which specifies the PORTION of the tree to be
searched, when searching for a sip entry, we'll pick up entries that match
the fields specified in res_ldap.conf.

There are two entries in the [sip] section which control this:

You've entered

name = cn

or

name = uid

or

name = AstAccountName

or

name = WhateverYouWant

The default res_ldap.conf contains an entry

additionalFilter=(objectClass=AstAccountSIP)

The search will look for an entry anywhere below the specified base which
has a field specified by name= (cn, uid, AstAccounName, or WhateverYouWant)
equal to the sip username and also matches "additionalfilter".

/john 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-28 16:22 jcovert        Note Added: 0098995                          
======================================================================