Stefan Sayer writes: > > when a user joins a conference, authentication application that > > asks/checks the pin code and then forwards the call to the conference, > > can set a timer that fires when the conference expires. onTimer handler > > of that timer can then kick out the user by sending a bye to it. there > > is thus no need for any external process to kick out the user. > how do you determine the call time? would it be statically > > configured?
stefan, currently, when user creates a conference in management system (not in sems), user tells when the conference starts and ends. when someone calls into my sems conference authentication application and gives a pin code, my the application application makes xmlrpc query to the management system, which check the pin code and returns back to sems conference authentication application the remaining conference time in seconds, which the application then uses to set up the expire timer. > > similar effect (and even better) could be achieved for web conference, > > if it would be possible to give a time argument to roomCreate function, > > which would tell how many seconds the conference room exists. web > > conference could then set a timer to expire at that time and kick > > everyone automatically out and delete the room. > ok, this sounds reasonable. > > > > > by the way, i didn't find a roomDelete function in > > Readme.webconference. > what should that function do? are you looking for a "kickAll" function? > that might make sense. undo whatever roomCreate did, e.g., roomInfo etc calls would stop working on the conference room because it would not exist anymore. as side effect, it would kick everyone out. > i was refering to the garbage collector, which works now. see > etc/webconference.conf configuration : ok, i read the description, but the model that web conference currently implements does not match mine. i want to to this: - user creates a conference in advance that starts at some given time and stops at some other given time or - user creates a conference that starts immediately and stays until it is explicitly removed that latter might be possible to implement using existing web conference application, but in order to easily implement the former, i would need roomCreate with a duration argument and automatic roomDelete with kick-all-out when duration expires. roomDelete would also be needed as a new explicit function. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
