> >> > >> > > >As part of the Personal Assistant I support voice conference > related IM > >commands such as > > - who => who is/was talking > > - list => list participants > > - mute/unmute participant > > - disconnect participant > > - lock/unlock > > > >So having chat room IM commands provides consistency. > > > > > > >The question was whether we want to support this in > sipxconfig or can we just rely on the client providing these > commands. I am concluding that sipxconfig support is >not necessary. > > > >Please elaborate on what was implied by your last statement. > > > > > >Thanks > > > >Regards > > > >Ranga > > > > We would like to focus on the Couterpath / SMC client. The > first thing I am not clear about is how the user would enter > a personal chat room that he/she can moderate. By default is > seems the client creates an ad-hoc chat room. How would the > client default to the one the user owns or moderates?
I've been focusing on pidgin so far so pardon my ignorance. You say that by default the SMC client seems to create ad-hoc char rooms. I've tried to get my SMC3456 to do that much without success, how did you achieve that? So, as you can see from my question above, I cannot answer your SMC-specific question but I can give you my general view on it based on my pidgin experience. The idea is that the sipXecs, when creating a voice conference for a user, will also be given the opportunity to create an associated chat room for which the user will be the moderator. Once this is done a user can enter a chat room by adding it to its 'buddies' (in pidgin this is done via the 'add chat' option). That will make the chat room appear as a buddy and double-clicking it will put you in that room. > > Once we know that I guess we need to figure out whether we > want to pre-provision personal group chat rooms for every > user. I assume all the nice commands only work if this is your room. For consistency sake I would not do that and instead would keep with the audio conference model, i.e. the admin creates the rooms that are required. > > At this stage I am unclear around how this feature of group > chat would present itself to the user, other than offering > the ability to create an ad-hoc room (does the client do this > on its own?). Ad-hoc is not really the way I see this being used. The idea is that a multi-user chat would be owned by a user the same way it owns a conference bridge. This gives a user 'audio' and 'IM' conferencing capabilities. Furthermore, we are working at strengthening the link between a user's audio and IM conferencing capabilities by adding the capability of promoting an IM conference into an 'IM' + 'audio' conference via a single text command. _______________________________________________ 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/
