Dear Mr. Harasaki,
HH>> >Either MCU or a terminal can initiate the call. HH>> HH>> In the root-initiated point-to-multipoint case, it's still MCU who HH>> should initiated the call since the addditional VC is setup by the HH>> calling party, the party who initiated the first VC (Do I understand HH>> H.310 procedure right?) HH> HH>Only initial VC (the call) can be initiated by either MCU or a terminal. HH>An additional VC can be initiated by either MCU or a terminal if the VC HH>is point-to-point. A point-to-multipoint additional VC shall be HH>initiated by MCU. HH> HH>I am not quite sure that point-to-point additional VC can be initiated HH>by a terminal after H.245 negotiation, though.
Please note that Section 7.1.1/H.310 specifies as follows:
Phase A3 (Additional VC Setup)
In this phase, and based on the communication mode determined above, the calling terminal, that is, the one that initiated the first VC SETUP message, shall firstly indicate the characteristics of the additional VC(s) to the remote end using the H.245 NewATMVCIndication message, and then shall setup the additional VC(s) with the appropriate parameters, such as bitrate and AAL type, for the transfer of the audiovisual and other data between the two H.310 terminals.
NOTE - This allows the remote end to receive the H.245 NewATMVCIndication message before responding to the VC setup message.
Best regards,
Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo@gctech.co.jp 151 Japan ********************************************************************