The symptom is being erratic. I thought I'd got it sussed just now and was about to send this message:
> OK, I think I've worked out where the problem lies, and it's in the length of > the IM Username field. Basically if the username field is longer than 10 > characters then the problem occurs, the user can't be edited. You can save a > username that's longer than 10 characters if IM but you can't edit it again > to fix it if IM is Enabled. If it's disabled you can put in a shorter > username and get around the problems. > > Some users are now locked in an un-editable state because their IM is Enabled > and their username is longer than 10 characters. However that's not quite right I can't consistently reproduce this. For one user, if I click Apply it's happy and says 'changes applied successfully', but if I think click OK it gives the app error message. I can only think that the database is in some inconsistent state due to bugs in sipXconfig.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
