[Home]

Summary:ASTERISK-12654: sip registeration with ldap
Reporter:anujay (anujay)Labels:
Date Opened:2008-08-28 00:40:27Date Closed:2011-06-07 14:02:50
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Resources/res_config_ldap
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:chan_sip.c:8474 register_verify: Peer '779' is trying to register, but not configured as host=dynamic
[Aug 28 11:16:58] NOTICE[14073]: chan_sip.c:14861 handle_request_register: Registration from '"779" <sip:779@192.168.1.24>' failed for '192.168.7.55' - Peer is not supposed to register

I have configured the ldap. The binding is taken place successfully. When i am registering the extension it is saying the above error. Kindly give me some directions to proceed on.
Comments:By: Leif Madsen (lmadsen) 2008-09-02 16:06:20

That error happens when you have a peer configured as 'host=192.168.1.100' (or some other static IP / hostname), but the peer is still attempting to register. Either change to 'host=dynamic' or configure your peer to not register to the server.

If you feel this bug was closed in error, please find a bug marshall in #asterisk-bugs on the Freenode IRC network at irc.freenode.net.
By: anujay (anujay) 2008-09-05 00:52:40

Hi,

I have enabled the host=dynamic still the problem is there, i am using the ldap with asterisk 1.4 version. Is it possible to use ldap with asterisk 1.4 version.
By: Leif Madsen (lmadsen) 2008-09-05 10:07:00

Can you please provide more information about this? Please attach logs with the output of your 'sip show peers', the relevant parts of your sip.conf file, and anything else which could point us at your problem.

I still believe this is a problem with your configuration as that message is coming from chan_sip, not res_config_ldap, and I'm not sure how the message is related to your ldap configuration, but I admit to having zero experience with ldap.
By: Leif Madsen (lmadsen) 2008-09-05 10:18:32

As has been pointed out to me, there is no LDAP module included in the 1.4 tree, thus this falls under a user support issue, and you should utilize the other available user support forums (such as the mailing lists) to debug your issue.