Summary:ASTERISK-16321: Asterisk LDAP Modify
Reporter:TBDeluxe (tbdeluxe)Labels:
Date Opened:2010-07-06 10:45:13Date Closed:2013-01-15 21:23:58.000-0600
Versions:Frequency of
is related toASTERISK-20886 [patch] LDAP configuration and documentation updates
Environment:Attachments:( 0) myDebugLog
I see a bug when Using LDAP Realtime

When my Phone is logged out and I Restart Asterisk then Login and Logout will be ok.

But when a Phone is Logged in when a restart Asterisk. Then a get follow Message when logout a Phone

[Jul  6 17:40:11] ERROR[4316]: res_config_ldap.c:1300 update_ldap: Couldn't modify dn:cn=532,ou=Phone,dc=kontrast,dc=de because Invalid syntax    -

Problem is the Field AstAccountFullname
Comments:By: Paul Belanger (pabelanger) 2010-07-06 14:45:21

We'll need a debug log.

We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue:


By: TBDeluxe (tbdeluxe) 2010-07-07 01:58:07

OK here is the Debug I saw that Happen when Logout

By: Matt Jordan (mjordan) 2013-01-15 11:27:22.938-0600

Please note that {{res_config_ldap}} is an extended support module. As such, development support for it typically comes from the open source community. Response times may reflect that.

By: Andrew Latham (lathama) 2013-01-15 12:10:54.133-0600

I have another ticket that may be related to this.  Let me check.

By: Andrew Latham (lathama) 2013-01-15 12:14:20.265-0600

LDAP schema updates and documentation problems lead to confusing field names. Attempting to test with multiple LDAP systems.

By: Andrew Latham (lathama) 2013-01-15 21:23:58.102-0600

As documented Asterisk needs to update LDAP account information like the SIP IP address as an example.  Documentation is also being updated to reflect confusion regarding the "fullcontact = AstAccountFullContact" vs "fullcontact = gecos" configuration settings.  See ASTERISK-20886 for details.

By: Nicholas John Koch (aviator) 2016-11-10 11:29:02.196-0600

Hi Folks,
I am new here but I have found a solution to that problem. I have created a patch. The bug mainly ist because of a false detection of an empty value that need to be deleted rather than modified in the LDAP object. Where can I explain it in more detail and upload a patch for this? Found in version 11.24.1
Thanks in advance