User guide

A-33
Cisco H.323 Signaling Interface User Guide
OL-2156-04 Rev. A1
Appendix A MML User Interface and Command Reference
set-overload
Syntax Description
Usage Guidelines Logging at any level implies that upper levels are included. When you are setting logging with the level
DEBUG, a confirmation is required because the amount of data logged affects service. For a list of the
packages that can log messages, see the “Log Message Packages” section on page 4-10.
Examples In the following example, the command sets the logging level of the package gapping to 0xFFE0:
gw mml> set-log:gapping:0xFFE0
M SUCC
logging level for package gapping set to 0xFFE0
Related Commands
set-overload
The set-overload command defines the overload handling criteria and behavior.
set-overload: level1|level2|level3:cpu,lower=number, upper=number
set-overload: level1|level2|level3:calls,lower=number, upper=number
set-overload: level1|level2|level3:gap,normal|all : number
Syntax Description
package One of the packages in the Cisco HSI.
For a list of package names, see the “Log Message Packages” section on
page 4-10.
level Logging levels are set through the use of hexadecimal numbers between
0x0000 and 0xFFFF. The higher the number, the higher the level of debug.
confirm If any client level parsing fails on the data session, a confirm is needed for
the data to be activated.
Command Description
diaglog Starts and stops event logging into a diagnostics log.
radlog Starts and stops RADVision logging into a specified log file.
rtrv-log Displays the logging level of a package or all packages.
level 1 | level 2 | level 3 Overload behavior can be provisioned at three separate levels: 1, 2, and 3
(rising in severity).
lower=number The lower threshold for overload detection and restoration of normal call
handling service.
upper=number The upper threshold for overload detection and restoration of normal call
handling service.