Cisco Cisco TelePresence MCU 4510 Release Notes
New features in Version 1.1(1.4)
Cisco TelePresence ConferenceMe Release 1.1(1.4) RC Software Release Notes
Page 5 of 11
(225 x 20 per sub-image). The image has a maximum height of 100 pixels. The background must be
set to transparent (using the alpha channel).
set to transparent (using the alpha channel).
Unicode support for conference names
ConferenceMe can now join conferences with conference names created in Unicode characters.
Allow reconnection attempts
Previously it was not possible to enter a new address in the Conference address box of the opening
window of the ConferenceMe application if a call fails. The application now allows you to enter new
addresses and make reconnection attempts when the ConferenceMe application is opened from the
Windows Start menu and the conference address is entered manually.
window of the ConferenceMe application if a call fails. The application now allows you to enter new
addresses and make reconnection attempts when the ConferenceMe application is opened from the
Windows Start menu and the conference address is entered manually.
Calls via a proxy server
It is now possible to make calls from ConferenceMe via a proxy server in a similar fashion to using a
web proxy. This is done by checking the Use Windows proxy settings checkbox in the Configuration
options window of ConferenceMe configuration, then setting the Windows proxy settings found in:
web proxy. This is done by checking the Use Windows proxy settings checkbox in the Configuration
options window of ConferenceMe configuration, then setting the Windows proxy settings found in:
Control Panel > Internet Options > Connections > LAN Settings > check Proxy Server box >
Advanced (Windows XP)
Advanced (Windows XP)
Control Panel > Network and Internet > Internet Options > Connections > LAN settings > check
Proxy Server box > Advanced (Windows Vista/Windows 7))
Proxy Server box > Advanced (Windows Vista/Windows 7))
ConferenceMe follows the Windows proxy exception filter settings.
IPv6 support
ConferenceMe can now connect to an MCU using IPv6. The Invite ConferenceMe participants page
on the MCU now allows users to generate links to the join page by selecting physical port, IP address
and TCP service. Users opening ConferenceMe from the Join conference page will use the IP
address specified to access the web page.
on the MCU now allows users to generate links to the join page by selecting physical port, IP address
and TCP service. Users opening ConferenceMe from the Join conference page will use the IP
address specified to access the web page.
NOTE: ConferenceMe will not allow IPv6 calls under Windows XP (or earlier). If an IPv6 address is
entered, an error message is generated.
entered, an error message is generated.
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 although this dummy address is an IPv4 address, it will be shown in the logs for
both IPv4 and IPv6 calls.
SIP logs. Private IP addresses are now hidden and the dummy address IN IP4 127.0.0.1 is shown
instead. Note that although this dummy address is an IPv4 address, it will be shown in the logs for
both IPv4 and IPv6 calls.