Optional Configurations for Cisco Expressway

NAT Configuration

NAT translations are also supported in the Cisco Expressway environment. To reconfigure the Expressway IP for NAT environments, use the cluster name 'EXPRESSWAY' in the following statement in the NAT Configuration.

Edit the NAT Configuration and add a NAT-MAP CLUSTER statement, fir detailed see NAT Configuration Syntax.

Example:

SUBSYS NAT
NAT-MAP CLUSTER(1, name=EXPRESSWAY, source=10.10.10.10, dest=10.20.20.20, mask=255.255.255.255)

Network Bandwidth

The Cisco Expressway monitoring feature tries to efficiently gather historical and active information from Expressway devices using Web queries. This is to minimize the network bandwidth required for monitoring an Expressway device. The monitoring feature is not able to improve on the efficiency of historical and active B2BUA components because of the Web Programming Interface currently implemented by Cisco. While the method of collecting data is efficient for active and historical calls, the same efficiency cannot be claimed for the B2BUA components.

If required, the data collection intervals and record aging in the Cisco Expressway feature can be adjusted through the dev-global.xml file which is located in the following folder path:

 <Prognosis_Home>/Server/Configuration/IPTM/IptDevice

In this configuration file, the aging and interval counts (in seconds) for call and system queries can be adjusted.

Call queries involve looking at the currently active calls and ALL historical calls (including B2BUA components) on the Cisco Expressway server. Incorrect settings can cause the historical call gathering process to be costly to run from a network traffic and computation perspective, so the following interval and aging variables in the dev-global.xml file can be adjusted, only if required:

  • ExpresswayCallsAgingInSec

  • ExpresswayCallsInterval

System queries involve ALL other web queries (Zones, Warnings, SystemInfo, Links, etc) and do not contain excessive information from a network perspective, so should not normally need to be adjusted. These are configured from the following variables the in dev-global.xml file:

  • ExpresswaySystemAgingInSec

  • ExpresswaySystemInterval

When configuring the aging and interval seconds, it is recommended that the aging value be at least double the interval value in seconds.

Do not make the aging value less than the interval value as this will cause a loss of data and empty Displays.

The other configuration options in the dev-global.xml file that start with 'Expressway' and end in 'Url' (ExpresswaySystemUnitUrl, ExpresswayResourceUsageUrl, ExpresswayZoneUrl, ExpresswayLinksUrl, ExpresswayAlarmsUrl, ExpresswayAlternateUrl, ExpresswayB2BUAUrl, ExpresswayCallsUrl, ExpresswayHistoryCallsUrl). These should not be changed without advice from IR Technical Support.

Provide feedback on this article