My comments below....
Regards, jimt.
At 12:13 PM 8/21/98 +0800, you wrote:
Hi.. I have some questions about master/slave determination in H.245. Perhpas these questions are stupid... but could you please kindly give me some help?
With H.245, we need to do master/slave determination to resolveconflicts between two endpoints which can be the MC in a conference.
(1) If there is no MC is active and all entities are of different types, the priority to win the master/slave determination is MCU > Gatkeeper > Gateway > terminal. THis means. e.g., with Gatekeeper and terminal, Gatekeeper always wins the determination? then why bothering to set "statusDeterminationNumber" to be a random no. in that certain range?
or only when those entities are all in the same type, then such setting just makes sense? i.e., "terminalType" overrules "statusDeterminationNumber" ??
Seems like a reasonable optimization.....it has been discussed before but never documented.
(2) An MC that is already acting as an MC shall always remian the active MC. However, assume that there are only terminals participating in a conference, what if a terminal that won the determination already decides to leave the conference at some time during the call? Should we need to perform such master/slave determination again?, or the terminal can assign the other to be an active MC?, or the terminal by no means can not leave the conference in the middle of the call?
If more than two terminals are in the conference then there must be an MC envolved. If the MC leaves the conference (note that this is not the same as the colocated Terminal leaving...) then the conference must end. The H.245 connections all go to the MC....
Please advise... thanks a lot..
Best regards,
Wanjiun Liao
***************************************************** *** +1-503-264-8816(voice) Intel - Hillsboro, OR. *** *** mailto:jim.toga@intel.com mailto:james.toga@ties.itu.int *** *** PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41 *** *****************************************************