Cisco Cisco Expressway Release Notes
Open and Resolved Issues
Unified Communications Cisco Expressway Series Software Release Notes (X8.5)
Page 8 of 23
Issue type
Link to list of issues
Open issues
Resolved
issues
issues
Table 2: Bug Search Tool queries for X8.2.2
Resolved in X8.2.1
Identifier
Description
CSCup29435
Symptoms: Expressway reports an application error, and the process restarts automatically. An
alarm is raised reporting that an unexpected software error was detected.
alarm is raised reporting that an unexpected software error was detected.
Conditions: Rare, under investigation.
Workaround: None, the app process will automatically be restarted.
CSCup46518
Symptoms: A remote endpoint registered to UCM via Mobile and Remote Access may fail to
register if an Expressway-C in the cluster is out of service (shutdown, or otherwise unreachable).
Conditions: One Expressway-C in the cluster is out of service, and the route created by the
endpoint happens to use that server.
register if an Expressway-C in the cluster is out of service (shutdown, or otherwise unreachable).
Conditions: One Expressway-C in the cluster is out of service, and the route created by the
endpoint happens to use that server.
Workaround: Restart the endpoint, which will cause it to obtain updated information about the
available Expressway-C servers, which will not include the one that is out of service.
available Expressway-C servers, which will not include the one that is out of service.
CSCup01126
Symptoms:Expressway restart due to internal application crash with "An unexpected software
error was detected in app[15225]: SIGSEGV (address not mapped to object)
@0x0000000000000000" alarm message.
error was detected in app[15225]: SIGSEGV (address not mapped to object)
@0x0000000000000000" alarm message.
CSCup29484
Symptoms: For re-INVITE process, Expressway B2BUA reuse Max-Forwards value that it
stored at the call establishment, therefore may see Max-Forward parameter reduced to an
unexpected level.
stored at the call establishment, therefore may see Max-Forward parameter reduced to an
unexpected level.
Conditions: Re-INVITE and call go through Expressway B2BUA application.
Workaround: None.
CSCup75947
Symptoms: On Expressway running 8.2 in a CMR Hybrid environment, B2BUA fails to process
and forward on the ACK sent by an MCU in response to a WebEx 200OK. The results in a SIP
negotiation failure where the connection ultimately times out on the WebEx side and WebEx
sends a BYE.
and forward on the ACK sent by an MCU in response to a WebEx 200OK. The results in a SIP
negotiation failure where the connection ultimately times out on the WebEx side and WebEx
sends a BYE.
Conditions: CMR Hybrid where MCU dials out to WebEx.
Workaround: In CMR Hybrid deployments you should:
n
Reconfigure the Expressway-E to not use static NAT, or
n
Recommended configuration for Expressway-C with Expressway-E deployments is to
configure the media encryption policy setting on the traversal client zone on Expressway-C,
the traversal server zone on Expressway-E, and every zone on Expressway-E, and to only
use static NAT on the Expressway-E. With this configuration the encryption B2BUA will only
be enabled on the Expressway-C.
configure the media encryption policy setting on the traversal client zone on Expressway-C,
the traversal server zone on Expressway-E, and every zone on Expressway-E, and to only
use static NAT on the Expressway-E. With this configuration the encryption B2BUA will only
be enabled on the Expressway-C.
Table 3: Issues resolved in X8.2.1