Export (0) Print
Expand All

6 Appendix A: Product Behavior

Office

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:

  • Microsoft Office Communications Server 2007

  • Microsoft Office Communications Server 2007 R2

  • Microsoft Office Communicator 2007

  • Microsoft Office Communicator 2007 R2

  • Microsoft Lync Server 2010

  • Microsoft Lync 2010

  • Microsoft Lync Server 2013

  • Microsoft Lync 2013

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 2.2.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. If a server does not receive a video packet, it drops all packets of the sequence of packets representing the entire video frame.

<2> Section 2.2.2: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. The entry point header is only present in the Codec Headers Bytes field and not in the video payload.

<3> Section 2.2.5: Office Communications Server 2007, Office Communicator 2007: Reserved/FECPacketsNumber (5 bits): Reserved field for future use. It is set to zero. The sender does not send more than one FEC metadata packets for each RTVideo frame.

<4> Section 2.2.5: Office Communications Server 2007, Office Communicator 2007: DV (2 bits): FEC version number. The value ranges from zero (0) to 3. The version number is zero (0) in the RTVideo FEC RTP Payload Format (section 2.2.5).

<5> Section 2.2.5: Office Communications Server 2007, Office Communicator 2007: Reserved/FECPacketsNumber (5 bits): Reserved field for future use. It is set to zero. The sender does not send more than one FEC metadata packets for each RTVideo frame

<6> Section 3.1.5.3: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported.

Receivers do not reconstruct a video frame with the aspect ratio of the MAX_CODED_WIDTH and MAX_CODED_HEIGHT specified in the sequence header.

<7> Section 3.1.5.3: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. The sequence header in the Codec Header Bytes field does not contain the DISP_HORIZ_SIZE and DISP_VERT_SIZE fields.

<8> Section 3.1.5.4: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. For all other products, the size of the buffer is the FEC data block size.

<9> Section 3.1.5.4: Office Communications Server 2007, Office Communicator 2007: DV (2 bits): FEC version number. The value ranges from zero (0) to 3. The version number is zero (0) in the RTVideo FEC RTP Payload Format (section 2.2.5). Reserved/FECPacketsNumber (5 bits): Reserved field for future use. It is set to zero. The sender does not send more than one FEC metadata packet for each RTVideo frame.

<10> Section 3.1.5.6: Office Communications Server 2007, Office Communicator 2007:

The value of the DV field is zero ("0") and the value of the Reserved/FECPacketsNumber field is set to zero ("0"). The sender does not send more than one FEC metadata packets for each RTVideo frame.

<11> Section 3.2.4.2: Office Communications Server 2007, Office Communicator 2007: DV (2 bits): FEC version number. The value ranges from zero (0) to 3. The version number is zero (0) in the RTVideo FEC RTP Payload Format (section 2.2.5).

Show:
© 2014 Microsoft