Chapter 3 Provisioning the Cisco HSI

Cisco HSI Configuration

Table 3-4 Dynamic System Data Parameters (continued)

Parameter

Description

Default

 

 

 

OVLDLEVEL1PERCENT

Indicates what percentage of calls should be rejected when an

20

 

overload condition occurs. This parameter is used in conjunction with

 

 

the OVLDLEVEL1FILTER parameter. The overload level 1 value is

 

 

the lowest level of overload and must be less than or equal to the

 

 

provisioned values for OVLDLEVEL2PERCENT and

 

 

OVLDLEVEL3PERCENT.

 

 

Note If this value is set to zero, no overload level 1 treatment

 

 

occurs.

 

 

 

 

OVLDLEVEL1FILTER

Indicates what call types should be gapped if an overload level 1

Normal

 

condition occurs. The possible values are:

 

 

• Normal—Emergency or priority calls are not gapped.

 

 

• All—All calls are gapped, regardless of type.

 

 

Note If the overload percentage is set to 100, all calls are gapped

 

 

irrespective of this setting.

 

 

 

 

OVLDLEVEL1THRESHLOWER

Determines the number of active calls below which the application

1800

CALLS

load must fall in order to remove the overload level 1 condition.

 

 

 

 

OVLDLEVEL1THRESHUPPER

Determines how many simultaneous active calls trigger an overload

1900

CALLS

level 1 condition.

 

 

 

 

OVLDLEVEL1THRESHLOWER

Determines the CPU utilization level below which the application

60

CPU

must fall in order to remove the overload level 1 condition.

 

 

 

 

OVLDLEVEL1THRESHUPPER

Determines the level of CPU utilization that triggers an overload

65

CPU

level 1 condition.

 

 

 

 

OVLDLEVEL2PERCENT

Indicates what percentage of calls should be rejected when an

75

 

overload condition occurs. The parameter is used in conjunction with

 

 

the OVLDLEVEL2FILTER parameter. This is the second level of

 

 

overload and must be less than or equal to the provisioned value of

 

 

OVLDLEVEL3PERCENT and greater than or equal to the

 

 

provisioned value of OVLDLEVEL1PERCENT.

 

 

Note If this value is set to zero, no overload level 1 or 2 treatment

 

 

occurs (by definition, the level 1 value must also be zero).

 

 

 

 

OVLDLEVEL2FILTER

Indicates what call types should be gapped if an overload level 2

Normal

 

condition occurs (see OVLDLEVEL1FILTER).

 

 

 

 

OVLDLEVEL2THRESHLOWER

Determines the number of active calls below which the application

2000

CALLS

load must fall in order for the overload level 2 condition to be

 

 

removed.

 

 

 

 

OVLDLEVEL2THRESHUPPER

Determines how many simultaneous active calls trigger an overload

2200

CALLS

level 2 condition.

 

 

 

 

OVLDLEVEL2THRESHLOWER

Determines the level of CPU utilization below which the application

70

CPU

must fall in order for the overload level 2 condition to be removed.

 

 

 

 

OVLDLEVEL2THRESHUPPER

Determines the level of CPU utilization that triggers an overload

80

CPU

level 2 condition.

 

 

 

 

 

 

Cisco H.323 Signaling Interface User Guide

 

 

 

 

 

 

OL-4806-01 Rev. A14

 

 

3-9

 

 

 

 

 

Page 8 Page 10
Page 9
Image 9
Cisco Systems H.323 appendix OVLDLEVEL1PERCENT, OVLDLEVEL3PERCENT, OVLDLEVEL1FILTER, OVLDLEVEL1THRESHLOWER, Calls, Cpu
Page 8 Page 10

H.323 specifications

Cisco Systems H.323 is a set of standards designed for transmitting audio, video, and data over packet-switched networks. It is a critical technology that enables real-time communication and has become integral to the world of VoIP (Voice over Internet Protocol) and video conferencing applications. Originally developed by the ITU-T, H.323 has been widely adopted and implemented by Cisco Systems, allowing organizations to leverage reliable and scalable communication solutions.

One of the standout features of H.323 is its ability to support interoperability among varying equipment and platforms. This means that devices from different manufacturers can communicate seamlessly, which is vital in a diverse technical environment. H.323 does this by defining protocols that handle signaling, media transport, and control, ensuring that various systems can work together effectively.

Key technologies utilized within H.323 include H.225 and H.245 signaling protocols. H.225 is responsible for call setup and management, establishing communication between endpoints. In contrast, H.245 manages the negotiation of media channels, allowing devices to configure themselves based on the capabilities of each other. This adaptability is crucial for dynamic network conditions typical in VoIP applications.

Another defining characteristic of H.323 is its support for multiple types of multimedia communication, including point-to-point and multipoint calls. This flexibility supports everything from simple audio calls to complex videoconferencing setups, where many participants can share video and audio streams concurrently. Cisco enhances this capability through its hardware and software offerings, optimizing performance for conference calls.

H.323 also features robust error resilience mechanisms. This ensures that real-time data, which is typically sensitive to delays and losses, can be transmitted with minimal disruption. Moreover, it facilitates quality of service (QoS) implementation, allowing organizations to prioritize voice and video traffic over less critical data services, thereby improving the overall user experience.

In conclusion, Cisco Systems H.323 stands out as a comprehensive solution for real-time communication over packet-based networks. Its main features, including interoperability, multimedia support, and enhanced error resilience, position it as a relevant technology in both corporate and personal communication settings. As organizations continue to adopt cloud and hybrid communication models, H.323 remains a reliable backbone for ensuring connectivity and collaboration across diverse platforms.
Top Page Image Contents