Export (0) Print
Expand All

4.4.1 Packet-Pair Commands for UDP Connections

The sequence of commands that is required to negotiate a packet-pair depends on whether the client and server have negotiated a UDP or a TCP connection for the transmission of streaming media packets.

When UDP is used, the following sequence applies.

587fd2c2-8dfe-43a1-88eb-988b7bf40158

Figure 4: Sequence for UDP connections

  1. The client sends a LinkViewerToMacConnect message with the playIncarnation field set to "0xF0F0F0F0". This value corresponds to the named value of MMS_USE_PACKET_PAIR.

  2. The server sends a LinkMacToViewerReportConnectedEX message with the playIncarnation field set to "0xF0F0F0F0".

  3. The client sends a LinkViewerToMacFunnelInfo message with the playIncarnation field set to "0xF0F0F901". This value corresponds to the named value of MMS_PACKET_PAIR_UDP_HIGH_ENTROPY.

  4. The server sends a LinkMacToViewerReportFunnelInfo message with the playIncarnation field set to "0xF0F0F901".

  5. The client sends a LinkViewerToMacConnectFunnel message.

  6. The server sends a LinkMacToViewerReportConnectedFunnel message.

  7. The client sends a LinkViewerToMacOpenFile message.

  8. The server sends a LinkMacToViewerReportOpenFile message.

  9. The client sends a LinkViewerToMacReadBlock message.

  10. The server sends the first of three Data packets (the first two forming the packet-pair) with the fields of the first packet set as follows:

    • LocationId is set to "0xF0F0F000".

    • playIncarnation is set to "0xFF".

    • AFFlags is set to "0X10".

    • payload is 1,472 bytes of random data.

  11. The server sends the second Data packet that is identical to the first except that the LocationId field is set to "0xF0F0F001".

  12. The server sends the third Data packet, which contains an ASF file header, along with the LinkMacToViewerReportReadBlock message to complete the conversation.

 
Show:
© 2014 Microsoft