Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
New features in X7
Cisco TelePresence Video Communication Server X7.2.4 Software Release Notes
Page 17 of 50
Other enhancements and usability improvements
You can now configure up to 200 SIP domains.
You can now configure up to 10,000 local authentication database credentials.
Full support of RFC 5806: any SIP diversion headers received in a 302 response are now
maintained in the outgoing INVITE message.
maintained in the outgoing INVITE message.
Improved zone status reporting: the zones summary page now shows separate SIP and H.323
connection status information.
connection status information.
Table sorting indicators: tabular displays now indicate by which column each table is sorted.
A filter facility has been added to the Subzones list page.
Chrome web browser is now supported; Internet Explorer 6 is no longer officially supported.
The administrator no longer has to log out and log back in again after reconfiguring DNS server
addresses.
addresses.
There is a new Call signaling routed mode advanced zone profile setting for neighbor zones. It
controls whether the zone always takes the signaling or uses the system-wide Call routed mode
setting.
controls whether the zone always takes the signaling or uses the system-wide Call routed mode
setting.
There is a new H.323 call signaling port advanced zone profile setting for neighbor zones. It
identifies the call signaling port on the neighbor system to use if Automatically respond to H.323
searches is set to On.
identifies the call signaling port on the neighbor system to use if Automatically respond to H.323
searches is set to On.
SSH and SCP clients are no longer available in the VCS operating system.
Reverse Path Filtering (RFC1812) is enabled by default. This ensures that the VCS will only
accept packets on interfaces from source addresses to which there are valid routes in the routing
table for that interface. This change may necessitate the adding of additional static routes on dual-
interface VCSs to ensure the VCS routing table matches the network topology.
accept packets on interfaces from source addresses to which there are valid routes in the routing
table for that interface. This change may necessitate the adding of additional static routes on dual-
interface VCSs to ensure the VCS routing table matches the network topology.