3.2.5.3.3 Sending MCS Connect Initial PDU with GCC Conference Create Request
The structure and fields of the MCS Connect Initial PDU with GCC Conference Create Request are specified in section 2.2.1.3. A basic high-level overview of the nested structure for the MCS Connect Initial PDU is illustrated in section 1.3.1.1, in the figure specifying MCS Connect Initial PDU.
The tpktHeader field is initialized as specified in [T123] section 8, while the x224Data field (which contains an X.224 Class 0 Data TPDU) is initialized as specified in [X224] section 13.7.
The MCS Connect Initial PDU (embedded within the mcsCi field) is specified in [T125] section 7, part 2. The client SHOULD initialize the fields of the MCS Connect Initial PDU as follows.
|
Connect initial field |
Value |
|---|---|
|
calledDomainSelector |
0x01. |
|
callingDomainSelector |
0x01. |
|
upwardFlag |
TRUE. |
|
targetParameters |
See the following table. |
|
minimumParameters |
See the following table. |
|
maximumParameters |
See the following table. |
|
userData |
GCC Conference Create Request. |
The targetParameters, minimumParameters, and maximumParameters domain parameter structures SHOULD be initialized as follows.
|
Domain parameter |
targetParameters |
minimumParameters |
maximumParameters |
|---|---|---|---|
|
maxChannelIds |
34 |
1 |
65535 |
|
maxUserIds |
2 |
1 |
65535 |
|
maxTokenIds |
0 |
1 |
65535 |
|
numPriorities |
1 |
1 |
1 |
|
minThroughput |
0 |
0 |
0 |
|
maxHeight |
1 |
1 |
1 |
|
maxMCSPDUsize |
65535 |
1056 |
65535 |
|
protocolVersion |
2 |
2 |
2 |
The userData field of the MCS Connect Initial PDU contains the GCC Conference Create Request (embedded within the gccCCrq field). The GCC Conference Create Request is specified in [T124] section 8.7 and appended as user data to the MCS Connect Initial PDU using the format specified in [T124] sections 9.5 and 9.6. The client SHOULD initialize the fields of the GCC Conference Create Request as follows.
|
Conference create request field |
Value |
|---|---|
|
conferenceName |
"1" |
|
convenerPassword |
Optional field, not used |
|
password |
Optional field, not used |
|
lockedConference |
FALSE |
|
listedConference |
FALSE |
|
conductibleConference |
FALSE |
|
terminationMethod |
automatic (0) |
|
conductorPrivileges |
Optional field, not used |
|
conductedPrivileges |
Optional field, not used |
|
nonConductedPrivileges |
Optional field, not used |
|
conferenceDescription |
Optional field, not used |
|
callerIdentifier |
Optional field, not used |
|
userData |
Basic client settings data blocks |
The userData field of the GCC Conference Create Request MUST be initialized with basic client settings data blocks (sections 2.2.1.3.2 through 2.2.1.3.5). The client-to-server H.221 nonstandard key which MUST be embedded at the start of the userData field ([T124] section 8.7 for a description of the structure of user data) MUST be the ANSI character string "Duca".
If Enhanced RDP Security (section 5.4) is in effect, the External Security Protocol (section 5.4.5) MUST be used to encrypt the entire PDU and generate a verification digest before the PDU is transmitted over the wire.