Release Notes

Identifier Description
CSCun70776 The TelePresence Server event log was recording many messages of the form "RTCP : Info
: call 1615, RTP session 2: message failed validity checks (invalid
payload)".
This issue is now resolved by reducing the severity of invalid messages.
CSCuj26833 On 7010 and MSE 8710 TelePresence Server platforms, the application's CDR log was not
properly recording remote teardown of H.323 calls.
This issue is now resolved.
CSCul55216 In some rare circumstances, a TelePresence Server could restart after receiving an unexpected
internal packet.
This issue is now resolved.
CSCum07100 When a CTS endpoint tried to join a TelePresence Server conference that had only audio ports
available, the CTS would join the conference without hearing any audio.
This issue is now resolved.
CSCun86369 The TelePresence Server would retransmit video received from Lync in the incorrect aspect
ratio, but only when significant horizontal motion was recorded by Lync.
This issue is now resolved.
CSCue88488 The TelePresence Server was too aggressively flow controlling the video from TC series
endpoints while there was a constant packet loss on the line.
This issue is now resolved.
CSCul94805 The TelePresence Server could unexpectedly restart during combinations of call defer and
automatic reconnection of dropped calls.
This issue is now resolved.
Open issues
The following issues apply to this version of Cisco TelePresence Server.
Identifier Description
CSCup59735 Cisco TelePresence Server on Virtual Machine requires 2.4 GHz or higher processors. If
the processor speed is too low, there is no warning to indicate that the processor is not
supported and that video calls cannot be made.
CSCup49756 On an 8 vCPU Cisco TelePresence Server on Virtual Machine the recommended
maximum 360p call participant capacity is 32. If a 33rd endpoint joins, call quality issues
may occur.
Cisco TelePresence Server Software Release Notes (4.0(2.8)) Page 26 of 36
Open issues