Hello,

o Jeremy A [08/31/08 13:03]:
> Hi,
> 
> I have encountered a webconference participant status '5' which is out 
> of the bounds of the documented 0-4
   enum ParticipantStatus {
     Disconnected = 0,
     Connecting,
     Ringing,
     Connected,
     Disconnecting,
     Finished
   };

a participant is in 'Finished' state when the call is over or when the 
call failed (e.g. was declined, or reply received, and dialog state 
AmSipDialog::Disconnected). 'Finished' is the last state of the 
participant. In this state it is held for 10 (PARTICIPANT_EXPIRED_DELAY) 
seconds, and then removed from the list.

> 
> In particular I have encountered two entries for the same participant 
> number, one has status '5' (??wtf??) and one has status '3' (connected)
but it is two separate calls i suppose? i.e. the call with status 5 and 
the one with 3 do not have any relation, apart from the fact that they 
are to the same number?

> 
> Given the history of calls in this instance, it seems the status '5' 
> entry has been kicked but not deleted, while status '3' is a currently 
> connected call to the same number.
> 
> Can someone confirm my assessment?
> 
> Further to this, the lack of a 'clear room' or 'delete room' function is 
> a problem. In my code I continually re-use a specific room and it would 
> be very helpful if I am guaranteed that there are no participants or 
> remnants of participants when I re-use it. (I 'kick' all participants at 
> end of conference, but they don't all seem to go in a reasonable time)
yes, this is still lacking unfortunately (SEMS-35).

> 
> Overall, the sems web conference has been very predictable and useful 
> asides from this problem - and the other problem that the dial-out 
nice. out of curiosity, which version do you use?

> function assumes attendees are in the same call domain, which is not 
> helpful in a generic conference.
this can be fixed easily in the WebconferenceFactory::dialout function. 
I have added a tracker item so this does not get lost - hopefully I will 
have some time to implement missing features. If not, I am always open 
for patches.

Stefan

> 
> Thanks
> 
> Jeremy
> 
> _______________________________________________
> Sems mailing list
> [email protected]
> http://lists.iptel.org/mailman/listinfo/sems

-- 
Stefan Sayer
VoIP Services

[EMAIL PROTECTED]
www.iptego.com

iptego GmbH
Am Borsigturm 40
13507 Berlin
Germany

Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to