Actually, when reading http://wiki.sipfoundry.org/display/sipXecs/LDAP+Integration again, it says as follows:
"alias: Multiple attributes (possibly multi-value attributes) can be mapped to this field" The field is rendered as a single-value dropdown in the import wizard, so I'm guessing / hoping this could be a simple bug.... --Anders 2011/5/10 Tony Graziano <tgrazi...@myitdepartment.net> > sounds like there needs to be an improvement request, or an extension > (custom field) to the LDAP server to populate the alias entries and map that > instead... > > > On Tue, May 10, 2011 at 1:03 PM, Anders Mydland <and...@mydland.info>wrote: > >> See inline comments >> >> 2011/5/10 Tony Graziano <tgrazi...@myitdepartment.net> >> >>> >>> >>> On Tue, May 10, 2011 at 12:26 PM, Anders Mydland <and...@mydland.info>wrote: >>> >>>> >>>> >>>> 2011/5/10 Laurentiu Ceausescu <lauren...@ezuce.com> >>>> >>>>> On Tue, May 10, 2011 at 5:29 PM, Anders Mydland >>>>> <and...@mydland.info>wrote: >>>>> >>>>>> I just found what I perceive as (another) weakness in the LDAP >>>>>> functionality. >>>>>> >>>>>> Running an import will overwrite any extra aliases that are configured >>>>>> (and probably other settings too). >>>>>> Using the default LDAP mappings for Active Directory (alias -> >>>>>> sAMAccountName), this has severe implications when adding new LDAP users >>>>>> to >>>>>> the system... >>>>> >>>>> With a typical use case for aliases being DID numbers, it would not be >>>>>> unreasonable to think that LDAP aliases and manually configured aliases >>>>>> should peacefully co-exist. >>>>>> Or am I just missing something? >>>>>> >>>>> >>>>> You can setup a DID number for an user - (User / Contact information >>>>> tab). >>>>> This setting will not be overwritten by a new LDAP import. >>>>> >>>> >>>> >>>> True, but this will not direct the incoming call (and even if it were, >>>> you're still limited to one). >>>> >>> >> >>> What do you mean here? Do you mean the user cannot have more than one >>> DID? The user alias field can accept more than one entry, you simply >>> separate them with a space between entries. >>> >> >> >> Laurentiu replied and was refererring to the user contact information >> field called "DID". Putting a number here does not put any calls to this >> number through to the user. >> >> The user alias field will indeed accept multiple space-separated aliases, >> but an LDAP import will overwrite any changes / additions. >> Thus, you're stuck with whatever single value you map from LDAP to your >> alias field. >> >> >> >>> If it should, it's not working.. >>>> >>>> DID rules in the dial plan do of course work for contiguous blocks. >>>> >>>> I still believe one should be able to get additional aliases / numbers >>>> from LDAP, as described below. >>>> >>>> >>>>> >>>>>> Also, it's being stated on the configuration page that the user id >>>>>> should be the users extension. >>>>>> With LDAP enabled, I believe it would be better to use the users' LDAP >>>>>> user name as the default user ID, and enable multiple aliases during >>>>>> import >>>>>> (e.g. ipPhone / businesPhone from the directory). >>>>>> >>>>>> >>>>>> Any comments? >>>>>> >>>>>> >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Anders Mydland >>>>>> >>>>>> _______________________________________________ >>>>>> sipx-users mailing list >>>>>> sipx-users@list.sipfoundry.org >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> sipx-users mailing list >>>>> sipx-users@list.sipfoundry.org >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>> >>>> >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> sipx-users@list.sipfoundry.org >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> >>> >>> >>> -- >>> ====================== >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> sip: tgrazi...@voice.myitdepartment.net >>> Fax: 434.326.5325 >>> >>> Email: tgrazi...@myitdepartment.net >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> sip: helpd...@voice.myitdepartment.net >>> >>> Helpdesk Contract Customers: >>> http://support.myitdepartment.net >>> >>> <http://support.myitdepartment.net>Blog: >>> http://blog.myitdepartment.net >>> >>> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>> >>> >>> _______________________________________________ >>> sipx-users mailing list >>> sipx-users@list.sipfoundry.org >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> _______________________________________________ >> sipx-users mailing list >> sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: tgrazi...@voice.myitdepartment.net > Fax: 434.326.5325 > > Email: tgrazi...@myitdepartment.net > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: helpd...@voice.myitdepartment.net > > Helpdesk Contract Customers: > http://support.myitdepartment.net > > <http://support.myitdepartment.net>Blog: > http://blog.myitdepartment.net > > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
