Cisco Cisco Expressway Release Notes
New features in X8.5
Unified Communications Cisco Expressway Series Software Release Notes (X8.5)
Page 3 of 23
Figure 1: Multiple deployments to partition Unified Communications services accessed from outside the
network
network
Serviceability improvements
Secure connection checker
This new utility enables you to test whether or not a secure connection can be made from the Expressway. It
checks the validity of certificates presented by the transacting parties, looking for errors that would prevent
the secure connection.
checks the validity of certificates presented by the transacting parties, looking for errors that would prevent
the secure connection.
You simply enter an FQDN, hostname, or IP address to test the secure connection without otherwise
affecting your configuration.
affecting your configuration.
The feature can be used in the following circumstances:
n
you are discovering Unified Communications servers / nodes while configuring Mobile and Remote
Access, and wish to test whether TLS or HTTPS will be possible with the configured nodes
Access, and wish to test whether TLS or HTTPS will be possible with the configured nodes
n
you are configuring a Unified Communications traversal zone, or Secure Traversal zone, between the
Expressway-C and the Expressway-E
Expressway-C and the Expressway-E
Syslog publish filter
You can now filter the logs that Expressway sends to each remote syslog host by severity level.
For example, your syslog host is typically receiving syslog messages from multiple systems, so you may
want to limit Expressway to sending only "Error" messages (and anything more severe) to this host. If you
want to leave the host untouched while troubleshooting a Expressway problem, you could configure a
second, temporary, host to receive "Debug" level (most verbose = messages of all severities). Then you
could safely remove the configuration after resolving the issue, without risking your primary syslog host.
want to limit Expressway to sending only "Error" messages (and anything more severe) to this host. If you
want to leave the host untouched while troubleshooting a Expressway problem, you could configure a
second, temporary, host to receive "Debug" level (most verbose = messages of all severities). Then you
could safely remove the configuration after resolving the issue, without risking your primary syslog host.