Chapter 4 Managing the Cisco HSI

Logging

Logging

The logging level of one or more service packages is set using the set-logMML command. For more information about this command, see Appendix A, “MML User Interface and Command Reference.”

Rotating Log Files

Log files are rotated at system startup or when either of the following conditions occurs:

The size limit for the corresponding file is reached. The size of the corresponding log file is equal to or greater than the value that the LOGFILEROTATESIZE configuration parameter specifies. The default value for this parameter is 10 Mb (see Chapter 3, “Provisioning the Cisco HSI”).

The age limit for the corresponding file is reached. The corresponding log file is equal to or older than the interval that the LOGFILEROTATEINTERVAL parameter specifies. The default value for this parameter is 1440 minutes (24 hours). See Chapter 3, “Provisioning the Cisco HSI,” for more information about this parameter.

Convention for Naming the Log File

Log rotation occurs when the system ceases to write to the current log file and commences to write to a new log file. The LOGFILENAMEPREFIX parameter defines the name of the active log file (see Chapter 3, “Provisioning the Cisco HSI”). The default is platform.log.

When log rotation is triggered, the existing file (for example, platform.log) is renamed with the format platform_yyyymmddhhmmss.log (see Table 4-4). For example, a platform error file rotated on September 30, 1999 at 12:36:24 is renamed platform_19990930123624.

Table 4-4 Log Filename Format

Format

Definition

 

 

LOGFILENAMEPREFIX

Provisioned filename (default is platform.log)

 

 

yyyy

Year

 

 

mm

Month

 

 

dd

Day

 

 

hh

Hour

 

 

mm

Minute

 

 

ss

Second

 

 

Note The time stamp is the coordinated universal time (CUT) from the machine at the time of rotation.

Log File Location

The LOGDIRECTORY parameter defines the directory for active log files and rotated log files (see Chapter 3, “Provisioning the Cisco HSI”). The default is $GWHOME/var/log/.

 

 

Cisco H.323 Signaling Interface User Guide

 

 

 

 

 

 

OL-4806-01 Rev. A14

 

 

4-9

 

 

 

 

 

Page 81
Image 81
Cisco Systems H.323 Logging, Rotating Log Files, Convention for Naming the Log File, Log File Location, Format Definition

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.