I think I've got this coming together now. > Is it about the user LDAP password or user PIN password?
The password is my current problem. I think I'm done with the PIN problem for now. I can use the default PIN setting for now and later set up an attribute which the user can fill out for the PIN. It's the password and the User ID that are causing me problems. > As far as I remember the user LDAP password is not generated/storedby > sipxecs, this would be a security break. When you manually create an account on sipx, the server creates a password for the user. If you don't pick a User ID, the system can also pick the next one from the pool. The User ID isn't as much of an issue as the password one is for me. > User LDAP passwords are kept only in LDAP and you can use it to > authenticate against your configured LDAP server with one of your LDAP > imported users. What has happened so far is that I can either use the "SIP password attribute" of [] which ends up creating a new user with a blank password or, I can pick the userPassword variable which is getting the password from LDAP and putting it into the new sipx account. I need to figure out what type of password is being pulled in however. It doesn't look like the long MD5 string that the mysql database contains, it's not clear text so it must be getting encrypted to something else by the tool I'm using to create the account on LDAP, phpldapadmin. The User ID is that I'd like to have sipx generate the next User ID based on the Extension Pool defined. I can use it either in the User ID section or in the Alias section. I've yet to see how this can be done. Once this is figured out, I've got to find some docs on configuring x-lite 4.0 with the openfire server on sipx. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
