The Maximum Transmission Unit (MTU) size defaults to 1500 post upgrade to X14.2 (from a lower version) while customizing the 'Maximum Transmission Unit (MTU)'. You must set it back to the intended value after a successful upgrade. To ensure MTU is set correctly, navigate to System > Network Interfaces > IP and then the appropriate LAN Number to check the current value.

Note	Restart the system for MTU size modification to take effect.

The REST API for Expressway is available to simplify remote configuration. For example, by third party systems such as Cisco Prime Collaboration Provisioning. We add REST API access to configuration, commands, and status information as new features are added, and also selectively retrofit the REST API to some features that were added in earlier versions of Expressway.

The API is self-documented using RAML, and you can access the RAML definitions at https://<ipaddress>/api/raml.

X14.0.9 release

Jabber Over MRA intermittently plays Ringing Tone instead of Busy, when called Extension is Busy

A new CLI command is added that specifies the maximum delay of a SIP REFER message . It contains DtLineBusyTone during initial call dialog (ensure SIP messages proceeds in a sequence) that the server can handle (in milliseconds).

Expressway processes and sends SIP messages (REFER contain DtLineBusyTone parameter and 183 Session Progress), which causes Jabber Over MRA to intermittently play Ringing Tone instead of Busy Tone (bug ID CSCwc27302 refers).

Recommend adjust delay between 100-200 milliseconds.

The CLI command is: xConfiguration SIP Advanced BusytoneReferDelay: <0..2000>

X14.0.7 release

Expressway processes SIP messages in a different order than they are received

A new CLI command is added that specifies the maximum delay of a SIP BIB invite message (ensure SIP message proceeds in order) that the server can handle (in milliseconds).

Recommend adjusting delay between 500-1000 milliseconds.

The CLI command is: xConfiguration SIP Advanced BibInviteDelay: <1..5000>

ssh removal from backup and restore

We are removing the client ssh public key and server ssh key pair from the backup and restore.

As ssh keys will not part of backup, after restoring the system ssh may not work without password. So, to login, add both client and server keys manually.

X14.0.2 release

CE Zone Status Change from "Active" to "Address Resolvable"

Prior to X14.0.2, CE zone showed a status of Active where the Zone Profile had Monitor Peer status / Neighbor Monitor set to No - since the Expressway is not monitoring the peer status for the CE zones, the more accurate status of Address Resolvable is indicated.

Auto-created UC zones and associated Unified Communications zone profile are not customizable and Neighbor Monitor set to No is by design.

Auto-created CE (tcp/tls/OAuth) Zone destined for the UC node will show status as Address Resolvable as per a fix for CSCup29823.

Traffic Server Enforces Certificate Verification

Important

Before upgrading from pre-X14.0.2 release to X14.0.8, make sure the following certificate requirement is met.

Due to improvements in the traffic server service in Expressway, beginning in X14.0.2, the following must be in place for MRA.

Requirement - Upload the Complete Certificate Authority (CA) chain of trust including any Certificate Authority provided intermediate certificates to the Tomcat-trust and CallManager-trust list of Cisco Unified Communications Manager (UCM), even if the UCM is in non-secure mode. And restart the following services on CUCM side:

• TFTP

• Tomcat Service

• CallManager Service

• HA Proxy Service (if using TLS on Tomcat)

Reason - The traffic server service in Expressway sends its certificate whenever a server (UCM) requests it. These requests are for services running on ports other than 8443 (for example, ports 6971, 6972, and so on). This enforces certificate verification even if UCM is in non-secure mode.

For more information, see Mobile and Remote Access Through Expressway Deployment Guide.