Export (0) Print
Expand All

3.3.5.3.4 Sending MCS Connect Response PDU with GCC Conference Create Response

The structure and fields of the MCS Connect Response PDU with GCC Conference Create Response are described in section 2.2.1.4. A basic high-level overview of the nested structure for the MCS Connect Response PDU is illustrated in section 1.3.1.1, in the figure specifying MCS Connect Response PDU.

The tpktHeader field is initialized as described 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 Response PDU (embedded within the mcsCrsp field) is described in [T125] section 7, part 2. The fact that the MCS Connect Response PDU will contain a GCC Conference Create Response as user data implies that processing of the MCS Connect Initial PDU with GCC Conference Create Request (see section 3.3.5.3.3) was successful, and hence the server MUST set the result field of the MCS Connect Response PDU to rt-successful (0). The calledConnectId field SHOULD be set to zero, while the domainParameters field MUST be initialized with the parameters which were derived from processing of the MCS Connect Initial PDU (see section 3.3.5.3.3 for a description of the negotiation rules).

The userData field of the MCS Connect Response PDU contains the GCC Conference Create Response (embedded within the gccCCrsp field). The GCC Conference Create Response is described in [T124] section 8.7 and appended as user data to the MCS Connect Response PDU using the format described in [T124] sections 9.5 and 9.6. The server SHOULD initialize the fields of the GCC Conference Create Response as follows.

Conference Create Response field

Value

tag

1 (length of 1 byte)

result

success (0)

userData

Basic Server Settings Data Blocks

The nodeID field of the GCC Conference Create Response MUST be initialized with a value in the range 1001 to 65536, inclusive, as required by the T.124 ASN.1 definitions of the UserID and DynamicChannelID types ([T124] section 8.7, parts 1 and 2).

The userData field of the GCC Conference Create Response MUST be initialized with basic server settings data blocks (see sections 2.2.1.4.2 through to 2.2.1.4.4). The server-to-client H.221 nonstandard key which MUST be embedded at the start of the userData field (see [T124] section 8.7 for a description of the structure of user data) is the ANSI character string "McDn".

If Enhanced RDP Security (see section 5.4) is in effect, the External Security Protocol (see 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.

 
Show:
© 2014 Microsoft