Robert Joly wrote: > Hi, > I'm looking at the way an admin would provision an IM user in the system > via sipXconfig. Currently, two pieces of information need to be > provided, namely the IM ID and the IM Display Name. The topic of this > post is around the need for IM Display Name part. This IM Display Name > effectily define the name that one will appear as in the buddy list of > an IM client. I'm guessing that this name will frequently be similar to > the user's first name and last name which already have dedicated fields > in thr 'add user' page. If that guess is accurate then it would be > annoying for the admin to have to re-type the user's first and last name > in the IM Display Name field. Would it make sense to use the > concatenation of the first and last name as the IM display name to > supply to sipXopenfire? WRT to the IM Display Name field, we could hide > it under advanced settings and it could be used to override the default > for users that do not like it. > > What do you think? > bob
Makes sense. I also think we can be more proactive in figuring out IM ID: for example by finding the non-numeric alias for the user. We have a new per-group property (not in mainline yet) that tells us if the group of users should be mirrored on OpenFire server. I am thinking about using this as an indication if user should be mirrored as well. That would simplify deployment: instead of importing or setting user names admin would just mark user group as "mirror to Instant Messaging server" and all users would have accounts created automatically. We would also need to come up with a strategy for choosing/generating the passwords. Ideas? D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
