> > > I am writing some openfire xmpp chat room management functions and > > would like to validate some working assumptions: > > > > 1. Each user can create chat rooms from his user portal. > This will be > > written into the xmpp-account-info.xml file and the plugin will > > instantiate the chat rooms by scanning that file. > > The subdomain for the chat room will be fixed and set to the user > > name. > > That breaks the current model of doing things wehre the admin > is the only one that gets to create these sorts of things. > Let's see what the sipXconfig guys think about this > > > > 2. Each chat room will have an associated conference number. > > This can be an extension assigned to a voice conference. > The owner can > > direct all members to join a conference call using a command in the > > chat window. I don't think we will need xml rpc support for this ( > > please correct this assumption if wrong ). > > Correct. sipXopenfire plugin will be doing the heavy lifting > here and initiate 3pcc calls using the 3rd party call controller. > > > > > 3. The user is the administrator as well as the owner of the chat > > room. He can invite new members and kick existing members ( > same way > > as we do for conference ). Do we want to make this an interceptor > > command (i.e. in line xmpp command) or an xml rpc command that is > > issued from the user portal? > > I would leave the xmpp commands out of this for now (unless > they come for free - I'm looking into that) and stick with > XML-RPC i/f.
They indeed come for free. The openfire multi-user chat offers the following command natively: affiliate, ban, clear, clearall, config, configure, debug, help, invite, join, kick, me, msg, nick, part, ping, register, role, say, topic. _______________________________________________ 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/
