In general each field can have an "override" attribute (i.e. xml attribute ) that dictates whether the user is allowed to change it or not. This can be generated by sipxconfig. The openfire plugin now simply overrides all fields with those that are generated by sipxconfig but there is no reason why this must be true. If "override" is set to true then I can compare creation time for the field / fields in question and take the latest one when populating the openfire database. Clearly, sipxconfig must decide carefully about what fields it wants to allow overrides to..
Martin : I assume you mean "an alias to the user". Why does this make sense. I thought these were for phone call routing ( like aliases can be used for DIDs). Why would it make sense to use the IM ID as a user alias? Are there any other uses for this? Ranga On Thu, Sep 3, 2009 at 9:27 AM, Martin Steinmann <[email protected]>wrote: > How about keeping the IM ID admin controlled, but allow the user to > change the display name? > > Should the IM ID also be an alias or not? > > --martin > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Fowler, Peter > (CAR:9D10) > Sent: Thursday, September 03, 2009 9:23 AM > To: Krzeminski, Damian (BL60:9D30); [email protected] > Subject: Re: [sipX-dev] Contact Information questions > > > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Krzeminski, Damian (BL60:9D30) > > Sent: Thursday, September 03, 2009 9:20 AM > > To: [email protected] > > Subject: Re: [sipX-dev] Contact Information questions > > > > Robert Joly wrote: > > >> Alfred Campbell wrote: > > >>> Christopher Parfitt wrote: > > >>>>> Will the User from User Portal be able to edit his/her Contact > > >>>>> Information and will that information be sync'd up with: > > >>>>> > > >>>>> * Superadmin Contact Information > > >>>>> * Softclient XMPP Contact Information > > >>>>> * IM / openfire Contact Information > > >>>>> > > >>>>> Chris > > >>>>> > > >>>> Yes. User will be able to edit his/her Contact Information. > > >>>> > > >>> Is this something coming in a future commit? > > >>> > > >> There is Laurentiu's patch and Kevin is reviewing it: > > >> http://track.sipfoundry.org/browse/XX-5552 > > > > > > > > > Changing a user's IM/openfire Contact information will > > result in the > > > former user being deleted from openfire and the new one > > created. This > > > operation in effect changes the users configured on the > > openfire server. > > > Up to now, these kinds of operations could only be performed by the > > > administrator. Are we comfortable putting this power in the user's > > > hands? > > > > > > > > > > Good point. > > I have to admit that when people say Contact Info I think of > > address, external phone number etc. I do not think that > > anybody is against letting end user to modify those. > > > > But Robert is right: one of the data items the is 'IM ID' and > > changing that would transfer the capability to create change > > IM accounts from administrator to user. So may be - just to > > be on the safe side - let's keep this one in admin hands till > > we actually have OpenFire integrated properly and can assess > > what types of issues may arise if we let users to control it. > > > > Kevin? Laurentiu? what do you think? > > 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/ > > > > Another option is to show the primary IM Ids as read only in the user > portal but allow > The user to change the alternate IM Id (eg. add a gtalk IM ID). > Currently I have coded Personal Assistant to accept registrations from > either Id. > _______________________________________________ > 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/ > _______________________________________________ > 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/ > -- M. Ranganathan
_______________________________________________ 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/
