Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Introduction
Cisco TelePresence Video Communication Server X7.2 Software Release Notes
Page 7 of 46
If you subsequently downgrade from X7.2 to X7.1 all local administrator accounts will have their
passwords reset to TANDBERG.
passwords reset to TANDBERG.
TMS Provisioning Extension mode
You must upgrade your VCS or VCS cluster (while still in TMS Agent legacy mode) to X7.1 or X7.2,
before installing TMS Provisioning Extension (TMSPE) and switching TMS and VCS into Provisioning
Extension mode.
before installing TMS Provisioning Extension (TMSPE) and switching TMS and VCS into Provisioning
Extension mode.
You are recommended to switch to TMS Provisioning Extension (TMSPE) mode, if you are using
Cisco TMS with Provisioning or FindMe, when the upgrade to X7.2 is complete and proven to be
operating correctly.
Cisco TMS with Provisioning or FindMe, when the upgrade to X7.2 is complete and proven to be
operating correctly.
To switch to Provisioning Extension mode (from TMS Agent legacy mode), you must upgrade TMS to
TMS 13.2 or later. See Cisco TMS Provisioning Extension Installation Guide.
TMS 13.2 or later. See Cisco TMS Provisioning Extension Installation Guide.
Upgrading a non-clustered VCS to X7.n from X5.1, X5.1.1 or X5.2
If you are currently running VCS X5.1, X5.1.1 or X5.2, you must first upgrade to X6.1, then upgrade
from X6.1 to X7.n.
from X6.1 to X7.n.
Upgrading a non-clustered VCS to X7.n from X5.0 or earlier
If you are currently running VCS X5.0 or earlier, you must first upgrade to X5.2, then upgrade from
X5.2 to X6.1, and then upgrade from X6.1 to X7.n.
X5.2 to X6.1, and then upgrade from X6.1 to X7.n.
Device authentication
You should review your whole network and consider whether authentication should be enabled for all
endpoints and enable authentication where possible.
endpoints and enable authentication where possible.
Upgrades from release X5.2 or earlier to X7.n
Cisco VCS upgrades where authentication is not enabled
If device authentication is not enabled when the Cisco VCS is upgraded from X5.2 or earlier to X7.n,
the upgrade process will configure all zones and subzones (except the Default Zone) on the Cisco
VCS with authentication set to ‘Treat as authenticated’. This ensures that:
the upgrade process will configure all zones and subzones (except the Default Zone) on the Cisco
VCS with authentication set to ‘Treat as authenticated’. This ensures that:
CPL continues to work as expected
Caller ID can be set to the FindMe ID for calls originating from endpoints specified in a FindMe
The provisioning request is challenged by the provisioning server (if in TMS Agent Legacy mode)
If you are upgrading from X6.n to X7.n your existing authentication configuration will not be changed.
Note that if TMS Agent (rather than the Cisco VCS) challenges for authentication of provisioning data,
the initial presence publication by Movi (if running Movi version 4.1 or earlier) will fail; to publish Movi
presence, users must manually set their presence status after logging in.
the initial presence publication by Movi (if running Movi version 4.1 or earlier) will fail; to publish Movi
presence, users must manually set their presence status after logging in.
Cisco VCS upgrades where authentication is already enabled
If device authentication is enabled when the Cisco VCS is upgraded from X5.2 or earlier to X7.n, the
upgrade process will configure the Cisco VCS with authentication set to ‘Check credentials’. This
means that:
upgrade process will configure the Cisco VCS with authentication set to ‘Check credentials’. This
means that:
CPL continues to work as expected
Caller ID can be set to the FindMe ID for calls originating from endpoints specified in a FindMe
The provisioning request is challenged by the Cisco VCS (if in TMS Agent Legacy mode)