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 updates to those products.

§ 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 Client 2013/Skype for Business

§ Microsoft Skype for Business 2016

§ Microsoft Skype for Business Server 2015

§ Windows 10 v1511 operating system

§ Windows Server 2016 operating system

§ Windows Server operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates 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.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: IPv6 is not supported.

<2> Section 2.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: RTP session SHOULD be terminated between 30 and 40 seconds.

<3> Section 2.2.1:  Office Communicator 2007, Office Communicator 2007 R2: Silence suppression cannot be disabled.

<4> Section 2.2.1:  Office Communications Server 2007, Office Communicator 2007: DTMF payloads are required to use the same payload type for the send and receive directions.

<5> Section 2.2.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Sending G711 µ-Law with 10 msec P-time is not supported.

<6> Section 2.2.1:  Sending /receiving GSM 6.10 is supported for Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only.

<7> Section 2.2.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Sending G711 A-Law with 10 msec P-time is not supported.

<8> Section 2.2.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

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

<10> Section 2.2.1:  Silk and OPUS codecs are not supported for Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010, Lync Server 2013, Lync Client 2013/Skype for Business, Skype for Business Server 2015 and Skype for Business 2016. 

<11> Section 2.2.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported.

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

<13> Section 2.2.1:  This behavior is not supported in Lync Server 2013, Lync Client 2013/Skype for Business.

<14> Section 2.2.1:  This behavior is only supported in Lync Server 2013, Lync Client 2013/Skype for Business.

<15> Section 2.2.1:  This behavior is only supported in Lync Server 2013, Lync Client 2013/Skype for Business.

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

<17> Section 2.2.1:  This behavior is only supported in Lync Server 2013, Lync Client 2013/Skype for Business. All other releases use SSRCs of the contributing source as CSRC list as described in [RFC3550].

<18> Section 2.2.1.2:  This behavior is supported for Microsoft Edge only.

<19> Section 2.2.1.2:  This behavior is supported for Microsoft Edge only.

<20> Section 2.2.10.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

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

<22> Section 2.2.11.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<23> Section 2.2.11.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<24> Section 2.2.11.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<25> Section 2.2.11.3:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<26> Section 2.2.11.4:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<27> Section 2.2.11.5:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<28> Section 2.2.11.6:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<29> Section 2.2.11.7:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<30> Section 2.2.11.8:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<31> Section 2.2.11.9:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<32> Section 2.2.11.10:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<33> Section 2.2.11.11:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported.

<34> Section 2.2.11.12:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported.

<35> Section 2.2.12:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync 2010, Lync Server 2010: This behavior is not supported.

<36> Section 3.1:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync 2010, Lync Server 2010: this behavior is not supported. SSRC of the contributing source is used instead.

<37> Section 3.1.3:  Office Communications Server 2007, Office Communicator 2007: If the SSRC throttling mechanism is used, all related variables are required to be initialized to invalid values at the start of a session. The very first RTP packet on a stream is required to trigger the throttling mode as if it were an SSRC change.

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

<39> Section 3.1.5:  Office Communications Server 2007, Office Communicator 2007: If the inter-arrival jitter estimation is computed, the jitter per algorithm is required to be calculated on receipt of every RTP packet from the network, which means no special handling for DTMF.

<40> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<41> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<42> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<43> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<44> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<45> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

<46> Section 3.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync 2010, Lync Server 2010: DSH message is not supported.

<47> Section 3.2.2:  Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: RTCP Bye timer:This timer is set to 2 seconds. It is started when an RTCP BYE is received. There MUST be one timer per participant.

<48> Section 3.2.2:  Office Communications Server 2007, Office Communicator 2007: Packet loss notification timer: This timer is required to be greater than or equal to 500 milliseconds, with a recommended setting of 500 milliseconds. It is started when an RTCP packet is sent containing a packet loss notification extension.

Show: