2.2.1.8 Client MCS Channel Join Request PDU
The MCS Channel Join Request PDU is an RDP Connection Sequence PDU sent from client to server during the Channel Connection phase of the RDP Connection Sequence (see section 1.3.1.1 for an overview of the RDP Connection Sequence phases). It is sent after receiving the MCS Attach User Confirm PDU (section 2.2.1.7). The client uses the MCS Channel Join Request PDU to join the user channel obtained from the Attach User Confirm PDU, the I/O channel (section 2.2.1.4.4), the message channel (section 2.2.1.4.5), and all of the static virtual channels obtained from the Server Network Data structure (section 2.2.1.4.4).
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
tpktHeader |
|||||||||||||||||||||||||||||||
|
x224Data |
mcsCJrq |
||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
tpktHeader (4 bytes): A TPKT Header, as specified in [T123] section 8.
x224Data (3 bytes): An X.224 Class 0 Data TPDU, as specified in [X224] section 13.7.
mcsCJrq (5 bytes): PER-encoded MCS Domain PDU which encapsulates an MCS Channel Join Request structure as specified in [T125] section 11.21 (the ASN.1 structure definitions are given in [T125] section 7, parts 6 and 10).