Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Active Directory integration

Discussion in '3CX Phone System - General' started by prozector, Jul 26, 2010.

Thread Status:
Not open for further replies.
  1. prozector

    Joined:
    Jul 26, 2010
    Messages:
    1
    Likes Received:
    0
    Good day!
    3CX v9.0.13373.540

    Doing "Download Active Users" i found that:
    0) Only first 500 records from Active Directory are shown
    1) No way to define Base DN ( OU=UsersContainer,OU=SiteOne,dc=Domain,dc=com ,for example)
    2) cannot define filter ( telephoneNumber=* for example, to fetch only records with phone number defined)
    3) After import all records have "autogenerated" ExtNs, and only Outbound Caller ID is "telephoneNumber". In our installation Extension number MUST BE exactly the same as "telephoneNumber"
    4) After closing "Download Active Users" window all the settings (Domain Controller, Domain, etc) are dropped to default values

    And some "feature requests":
    0) Ring groups controlled with Security Groups in AD
    1) autoassigned PIN defined by editable formula ( md5(Extension Number+Last Name), for example)
     
  2. matictec

    matictec New Member

    Joined:
    Mar 31, 2008
    Messages:
    188
    Likes Received:
    0
    We have the same problem. It is neccessary to define an base DN or to set a filter. When it is already possible, than please told us how.

    And it would be very nice if the ip-phone number for the user object would be used for extension number
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. lklm

    Joined:
    Mar 18, 2009
    Messages:
    5
    Likes Received:
    0
    I have a fix for the autogenerated Extension numbers, and LDAP lookup.

    In AD for all of your users set the LDAP attribute "extensionAttrubute1" to whatever their Extension should be. (using AttributeEditor in AD interface.

    then when you do the import it will import that number as the Extension number, the loginID and the password.
     
  4. mholman

    Joined:
    Aug 22, 2014
    Messages:
    21
    Likes Received:
    0
    We have run in to the same issue. It would be nice to be able to limit the search baseDN, but it does not seem like that is possible. What you can do is change the LDAP search field in the Advanced option to be whatever field you know for that given user and then enter it in the search text. The problem here is it does not recognize partial information, so you need to know the exact name. For example if you left the "LDAP search field" as CN then you wanted to search for Joe Smith, you have to enter in Joe Smith exactly. You cannot just enter Joe and get search results for all Joe's. Kind of a work around, but it helps a bit.

    I would request the option to limit the search baseDN and also request that search results not needing to be an exact match.

    Thanks
     
Thread Status:
Not open for further replies.