Cisco Cisco TelePresence MCU 4510 Release Notes
New features in Version 4.2
Cisco TelePresence MCU Version 4.2(1.50) software release notes
Page 8 of 20
Camera control always applies to largest pane, or top left pane when panes are the same size. Note
that if you have no way to control the layout then you cannot select which participants’ camera to
move – you can only control the camera in the top left pane.
that if you have no way to control the layout then you cannot select which participants’ camera to
move – you can only control the camera in the top left pane.
Different ports for ConferenceMe and web
It is now possible to give users access to an MCU web page which allows them to join conferences
using ConferenceMe and invite other participants to the conference, but has no links to MCU pages
unrelated to ConferenceMe. The ConferenceMe installer can also be accessed via the new join page.
using ConferenceMe and invite other participants to the conference, but has no links to MCU pages
unrelated to ConferenceMe. The ConferenceMe installer can also be accessed via the new join page.
To enable this feature go to Network > Services and check the ConferenceMe box in the TCP service
settings and set the port for the ConferenceMe service. If the Allow ConferenceMe to use web service
box is checked on Settings > Streaming, users are still able to connect to the MCU via the web
service as before.
settings and set the port for the ConferenceMe service. If the Allow ConferenceMe to use web service
box is checked on Settings > Streaming, users are still able to connect to the MCU via the web
service as before.
ConferenceMe calls via Port B
It is now possible to make calls using Port A or B on the MCU. Links can be generated to the
ConferenceMe join page on a different physical port to that which is being used to browse the web
interface using Conferences > Conference name and clicking on the ConferenceMe Invite button.
ConferenceMe join page on a different physical port to that which is being used to browse the web
interface using Conferences > Conference name and clicking on the ConferenceMe Invite button.
Per conference enable/disable of ConferenceMe
It is now possible to enable or disable the use of ConferenceMe on conferences on an individual
basis. This is done by setting the unit-wide setting Streaming & ConferenceMe settings in Settings >
Streaming to enable ConferenceMe, then selectively enabling or disabling ConferenceMe by setting
the ConferenceMe parameter in the conference configuration page (go to Conferences and click the
name of the conference to be enabled or disabled for ConferenceMe).
basis. This is done by setting the unit-wide setting Streaming & ConferenceMe settings in Settings >
Streaming to enable ConferenceMe, then selectively enabling or disabling ConferenceMe by setting
the ConferenceMe parameter in the conference configuration page (go to Conferences and click the
name of the conference to be enabled or disabled for ConferenceMe).
Guest or chair access for ConferenceMe
In conferences set up with two different PINs for guest and chair participants, ConferenceMe users
may now enter either the guest or chair PIN in order to join the conference as that type of participant.
If the chair and guest PINs are identical, the ConferenceMe participant will join as a guest.
may now enter either the guest or chair PIN in order to join the conference as that type of participant.
If the chair and guest PINs are identical, the ConferenceMe participant will join as a guest.
Private IP address hiding for ConferenceMe calls
Previously, in calls using the ConferenceMe software endpoint private IP addresses were shown in
SIP logs. Private IP addresses are now hidden and the dummy address IN IP4 127.0.0.1 is shown
instead. Note that this same dummy data is also populated in logs for IPv6. The call is not using IPv4.
SIP logs. Private IP addresses are now hidden and the dummy address IN IP4 127.0.0.1 is shown
instead. Note that this same dummy data is also populated in logs for IPv6. The call is not using IPv4.
Full HD mode
The Cisco TelePresence MCU 4500 series and MSE 8510 now support Full HD mode. Full HD mode
allows the MCU to decode at a maximum resolution of 1080p at 30fps, as well as transmit at 1080p at
30fps. Note that the HD+ mode that was introduced in a previous release allowed transmission of
these resolutions but only supported decoding of received video in 720p at 30fps.
allows the MCU to decode at a maximum resolution of 1080p at 30fps, as well as transmit at 1080p at
30fps. Note that the HD+ mode that was introduced in a previous release allowed transmission of
these resolutions but only supported decoding of received video in 720p at 30fps.
On the Cisco TelePresence MCU 4500 series, using Full HD mode allows half the number of HD
video ports, but the full number of audio-only ports. For example, on the MCU 4520, 20 Full HD video
ports are available and the usual 40 audio-only ports.
video ports, but the full number of audio-only ports. For example, on the MCU 4520, 20 Full HD video
ports are available and the usual 40 audio-only ports.
On the Cisco TelePresence MSE 8510, four media port licenses are required for each Full HD video
port. Each video port has only one audio-only port associated with it. The maximum number of Full HD
ports available on the MSE 8510 is 10. Therefore, 40 media port licenses are required to provide 10
Full HD video ports which in turn provide 10 audio-only ports.
port. Each video port has only one audio-only port associated with it. The maximum number of Full HD
ports available on the MSE 8510 is 10. Therefore, 40 media port licenses are required to provide 10
Full HD video ports which in turn provide 10 audio-only ports.
MSE 8510 clusters can also be put in Full HD mode. This will provide up to 30 Full HD ports on a
three blade cluster.
three blade cluster.