George, Multi-value attributes from LDAP _do_ work for aliases, but are not very practical in a Windows / Active Directory environment. Windows user profile typically have predefined attributes such as sAMAccountName, ipPhone, businessPhone and the like that could all go into "aliases".
On a sidenote, it would be sensible to allow mapping of a single-value LDAP field to Caller ID / DID, or even designate DID as a special type of alias that would also be the default caller ID. That would simplify user administration a great deal... Regards, Anders 2011/5/10 George Niculae <geo...@ezuce.com> > On Tue, May 10, 2011 at 8:33 PM, Anders Mydland <and...@mydland.info> > wrote: > > 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.... > > Change alias -> sAMAccountName mapping to alias -> > LDAP_attribute_that_allow_multiple_values and you'll end up with an > user with multiple aliases in sipXconfig. > > Regards, > George > _______________________________________________ > 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/
