Page 1 Cisco H.323 Signaling Interface User Guide Cisco HSI Release 4.1 November 2007 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100 Text Part Number: OL-4806-01 Rev. A14...
Page 2 MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
Page 3: Table Of Contents
Preface Document Objectives Audience System Administrator System Operator System Technician Document Organization Document Conventions Related Documentation Release Notes Hardware Documentation Software Documentation Related Documentation Obtaining Documentation World Wide Web Documentation CD-ROM Ordering Documentation Documentation Feedback Obtaining Technical Assistance Cisco.com Technical Assistance Center Cisco TAC Web Site Cisco TAC Escalation Center Cisco H.323 Signaling Interface Overview...
Page 4 Contents E-ISUP New Features in Cisco HSI Release 4.1 Operational Environment Hardware Requirements Software Requirements Security Cisco HSI Recovery Cisco HSI System Limitations Installing and Configuring Cisco HSI Software C H A P T E R Introduction Hardware and Software Requirements Installing the Operating System Installing the Cisco HSI Before You Start...
Page 5 H.323 Stack Configuration Nonprovisionable Data MML Provisionable Data H.323 System Parameters Q.931 Parameters RAS Parameters H.245 Parameters Codec Selection Quick Reference for Important Parameters HSI Feature Configuration Asymmetric Codec Treatment Empty Capability Set H.323 Hairpin T.38 Fax Configuring T.38 Fax on the Cisco PSTN Gateway Configuring T.38 Fax on a Cisco IOS H.323 Gateway Configuring T.38 Fax on a Cisco IOS MGCP Gateway HSI INFORMATION Message Support...
Page 6 Contents Overload Level 2 Overload Level 3 Setting Overload Data Retrieving Overload Data Logging Rotating Log Files Convention for Naming the Log File Log File Location Log Messages Log Message Packages Logging Levels Setting Logging Levels RADVision Logging Gapping Setting Gapping Retrieving Call Gapping Data Troubleshooting Cisco HSI Alarms C H A P T E R...
Page 7 Cause Troubleshooting EISUP_PATH_FAILURE Description Severity Level and Trap Type Cause Troubleshooting GATEKEEPER_INTERFACE_FAILURE GENERAL_PROCESS_FAILURE Description Severity Level and Trap Type Cause Troubleshooting IP_LINK_FAILURE Description Severity Level and Trap Type Cause Troubleshooting LOW_DISK_SPACE Description Severity Level and Trap Type Cause Troubleshooting OVERLOAD_LEVEL3 Description Severity Level and Trap Type Cause...
Page 8 Contents Severity Level and Trap Type Cause Troubleshooting ENDPOINT_CALL_CONTROL_INTERFACE_FAILURE Description Severity Level and Trap Type Cause Troubleshooting ENDPOINT_CHANNEL_INTERFACE_FAILURE Description Severity Level and Trap Type Cause Troubleshooting GAPPED_CALL_NORMAL Description Severity Level and Trap Type Cause Troubleshooting GAPPED_CALL_PRIORITY Description Severity Level and Trap Type Cause Troubleshooting OVERLOAD_LEVEL1...
Page 9 Severity Level and Trap Type Cause Troubleshooting Detailed Logging MML User Interface and Command Reference A P P E N D I X Introduction Starting an MML Command Session in the Cisco HSI MML Commands MML Command Syntax MML Command Conventions Case Sensitivity Starting an MML Session Batch Files...
Page 10 Contents radlog restart-softw rtrv-alms rtrv-calls rtrv-ctr rtrv-dest rtrv-gapping rtrv-log rtrv-mml rtrv-ne rtrv-ne-health rtrv-overload rtrv-softw set-dest-state set-gapping set-log set-overload sta-callproc sta-softw sta-trc stp-call stp-callproc stp-softw stp-trc Cisco H.323 Signaling Interface User Guide OL-4806-01 Rev. A14...
Page 11 Skeleton Configuration File A P P E N D I X Example of an HSI Configuration File A P P E N D I X E-ISUP Name-to-Cause Value Lookup A P P E N D I X E-ISUP Cause Value-to-Name Lookup A P P E N D I X H.323 Name-to-Cause Value Lookup A P P E N D I X...
Page 12 Contents Cisco H.323 Signaling Interface User Guide OL-4806-01 Rev. A14...
Page 13: Preface
Preface This preface describes the objectives, audience, organization, and conventions of the Cisco H.323 Signaling Interface User Guide, and explains how to find additional information on related products and services. It contains the following sections: Document Objectives, page 13 • •...
Page 14: System Operator
Document Organization The system administrator should have an in-depth knowledge of UNIX and a basic knowledge of data and telecommunications networking. System Operator The system operator is assumed to have knowledge of the following: • Telecommunications protocols Basic computer software operations •...
Page 15: Document Conventions
Preface • Appendix E, “E-ISUP Cause Value-to-Name Lookup” Appendix F, “H.323 Name-to-Cause Value Lookup” • Appendix G, “H.323 Cause Value-to-Name Lookup” • Document Conventions This manual uses the document conventions listed in this section. Table 1 Document Conventions Convention Boldface Italics Courier Courier bold...
Page 16: Related Documentation
Related Documentation Table 1 Document Conventions (continued) Convention System prompt Exclamation point (!) at the beginning of a line Means reader take note. Notes contain helpful suggestions or references to material not covered in the Note manual. Means the following information will help you solve a problem. The tip information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Page 17: Software Documentation
• ITU Recommendation H.246 Annex C • Obtaining Documentation These sections explain how to obtain documentation from Cisco Systems. World Wide Web You can access the most current Cisco documentation on the World Wide Web at this URL: http://www.cisco.com Translated documentation is available at this URL: http://www.cisco.com/public/countries_languages.shtml...
Page 18: Ordering Documentation
• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387). Documentation Feedback You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the “Leave Feedback”...
Page 19: Technical Assistance Center
Preface • Register for online skill assessment, training, and certification programs If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL: http://www.cisco.com Technical Assistance Center The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution.
Page 20: Cisco Tac Escalation Center
Preface Obtaining Technical Assistance Cisco TAC Escalation Center The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
Page 21 Cisco H.323 Signaling Interface Overview Introduction This chapter provides an overview of the Cisco H.323 Signaling Interface (HSI) system and subsystems and contains the following sections: Cisco HSI Overview, page 1-1 • Cisco HSI System Description, page 1-2 • Operational Environment, page 1-4 •...
Page 22: E-Isup
Cisco HSI System Description Figure 1-1 Cisco HSI System Overview Voice/ signaling Callers PGW 2200 The PGW 2200 consists of the hardware and software that perform the signaling and call control tasks (such as digit analysis, routing, and circuit selection) and seamlessly switch calls from the PSTN through to the IP network.
Page 23: C H A P T E R 1 Cisco H.323 Signaling Interface Overview
Chapter 1 Cisco H.323 Signaling Interface Overview Figure 1-2 Cisco HSI Subsystems SNMP Workstation Third party OAM Subsystem The OAM subsystem provides the following services: • Man-Machine Language (MML) interface that enables you to retrieve operational parameters and modify configuration values through direct input or through batch files •...
Page 24: New Features In Cisco Hsi Release 4.1
Operational Environment RUDP RUDP transports the E-ISUP messages between the PGW 2200 and the Cisco HSI. RUDP is a Cisco proprietary, connection-oriented, packet-based transport protocol. RADVision H.323 The Cisco HSI 4.1 release uses the RADVision 4.1 H.323 stack. The HSI uses the H.225 (Q.931 and registration, admission, and status [RAS] protocol) and H.245 protocols to implement the H.323 gateway signaling function.
Page 25: Software Requirements
Chapter 1 Cisco H.323 Signaling Interface Overview Software Requirements The software requirements for the Cisco HSI are documented in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide. Security The application does not directly provide security features. All security must be implemented at the UNIX level.
Page 26 Chapter 1 Cisco H.323 Signaling Interface Overview Cisco HSI System Limitations Cisco H.323 Signaling Interface User Guide OL-4806-01 Rev. A14...
Page 27: Introduction
Installing and Configuring Cisco HSI Software Introduction This chapter contains instructions for installing and configuring the Cisco H.323 Signaling Interface (HSI). This chapter contains the following sections: Hardware and Software Requirements, page 2-1 • Installing the Operating System, page 2-1 •...
Page 28: Installing The Cisco Hsi
Installing the Cisco HSI Installing the Cisco HSI This section provides step-by-step instructions for installing the Cisco HSI. Before You Start Complete the preinstallation tasks listed in to ensure that each task is completed. Detailed instructions for completing some tasks follow the checklist.
Page 29: Cisco Hsi Installation Information
Chapter 2 Installing and Configuring Cisco HSI Software Step 5 Enter the following command: # vi .cshrc Enter the vi insert mode by entering the following command: Step 6 i (enter insert mode) Enter the following text on the first line: Step 7 source /opt/GoldWing/currentPM/local/setup.gw.csh Save the file and quit vi by entering the following commands:...
Page 30 Installing the Cisco HSI Table 2-2 Cisco HSI Installation Information (continued) Required Information Hardware platform Installation location 1. VSC = virtual switch controller 2. DNS = domain name system 3. PGW = PSTN Gateway The Cisco HSI application is distributed as a tar file (with filename GoldWing-xxxx.tar in which xxxx is the version ID, for example, GoldWing-4.1.tar) or as a CD-ROM.
Page 31: Installing Cisco Hsi
Chapter 2 Installing and Configuring Cisco HSI Software Installing Cisco HSI This section provides step-by-step instructions for installing a single Cisco HSI for use with a simplex PGW 2200 configuration (a configuration with one Cisco PGW 2200 host). To install a dual Cisco HSI for use with a redundant PGW 2200 configuration (a configuration with two Cisco PGW 2200 hosts), complete the steps in this section and then proceed to the PGW 2200 Configuration”...
Page 32 The following text displays: Processing package instance <OTTgw000> from </export/BUILDS/4.1/APPLICATIONS/OTTgw000.pkg> GoldWing H323 Adjunct Processor V0.1.6 (sparc) 4.1 Copyright (c) 2001 Cisco Systems, Ltd. All Rights Reserved This product is protected by copyright and distributed under licenses restricting copying, distribution and decompilation.
Page 33 Chapter 2 Installing and Configuring Cisco HSI Software Step 14 Type the gatekeeper ID (see The gatekeeper ID must match the entry configured in the gatekeeper. Note The following text displays: Enter E-ISUP Host Port Type the E-ISUP host port (see Step 15 The E-ISUP host port is typically 8003, but it must match the peer port setting of the IPLNK Note...
Page 34 Installing the Cisco HSI Step 20 Type the installation location (see The installation location field is a text field typically used by network designers for Note identification purposes. Entering a value in this field does not affect functionality. The following is an example of the screen that displays: ## Executing checkinstall script.
Page 35 Chapter 2 Installing and Configuring Cisco HSI Software [ verifying class <script> ] ## Executing postinstall script. Installed package instance is: OTTgw000 Installation of <OTTgw000> was successful. Installed package instance environment variables are: ----------------------------------------------------- PKGINST=OTTgw000 VERSION=4.1 BASEDIR=/opt/GoldWing/4.1 GWHOME=/opt/GoldWing MGCUSR=mgcusr MGCGRP=mgcgrp ----------------------------------------------------- Setting link /opt/GoldWing/currentPM.
Page 36: Installing Multiple Cisco Hsis In A Redundant Pgw 2200 Configuration
Installing the Cisco HSI Installing Multiple Cisco HSIs in a Redundant PGW 2200 Configuration This section describes how to install and configure two Cisco HSI for use with a redundant Cisco PGW 2200 configuration (See Figure 2-1 Dual Cisco HSI with a Redundant PGW 2200 Configuration Cisco PGW 194.182.147.226 194.182.147.242...
Page 37: Dual Hsi Example Configuration Script
Chapter 2 Installing and Configuring Cisco HSI Software Dual HSI Example Configuration Script The following example script configures the network topology depicted in Example HSI-A (Blue network) prov-add:name="SYS_CONFIG_STATIC",HOST_PORT_NUMBER1="9001" prov-add:name="SYS_CONFIG_STATIC",HOST_PORT_NUMBER2="0" prov-add:name="SYS_CONFIG_STATIC",VSCA_IPADDR1="194.182.147.242" prov-add:name="SYS_CONFIG_STATIC",VSCA_IPADDR2="194.182.147.242" prov-add:name="SYS_CONFIG_STATIC",VSCA_PORT_NUMBER1="8003" prov-add:name="SYS_CONFIG_STATIC",VSCA_PORT_NUMBER2="8003" prov-add:name="SYS_CONFIG_STATIC",VSCB_IPADDR1="194.182.147.243" prov-add:name="SYS_CONFIG_STATIC",VSCB_IPADDR2="194.182.147.243" prov-add:name="SYS_CONFIG_STATIC",VSCB_PORT_NUMBER1="8003" prov-add:name="SYS_CONFIG_STATIC",VSCB_PORT_NUMBER2="8003" HSI-B (Red network) prov-add:name="SYS_CONFIG_STATIC",HOST_PORT_NUMBER1="9002"...
Page 38: Stopping The Cisco Hsi
Stopping the Cisco HSI Stopping the Cisco HSI To stop the Cisco HSI, log in as root user and enter the following command: # /etc/init.d/CiscoGW stop The command to stop the Cisco HSI returns information such as the following: Note /etc/init.d/CiscoGW stop Signalling PMmain to shut down Signalling GWmain[739] to shut down...
Page 39: Removing The Cisco Hsi
Chapter 2 Installing and Configuring Cisco HSI Software • The system should be restarted to enable the re-initialization of the SNMP processes. The craftsperson needs to change the user to root and issue the following UNIX command: shutdown -i 6 -g 0 -y To revert to a previous version of the software, manually modify the currentPM and currentGW Note links in the/opt/GoldWing parent directory to point to the previous version.
Page 40 Removing the Cisco HSI Step 6 Type y and press Enter. The following text displays: ## Removing installed package instance <OTTgw000> This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] Type y and press Enter.
Page 41: Chapter 3 Provisioning The Cisco Hsi
Provisioning the Cisco HSI Introduction This chapter describes the data that must be provisioned for the Cisco H.323 Signaling Interface (HSI). The data is divided into two areas: system configuration and H.323 stack data. This chapter contains the following sections: Cisco HSI Configuration, page 3-1 •...
Page 42: Mml Configuration Commands
Cisco HSI Configuration HSI starts up, it attempts to read the active configuration, checks that the configuration has been verified, and ensures that the checksum matches. If the active configuration is not verified or if the checksum is faulty, the configuration reverts to using the $GWHOME/currentGW/etc/GWmain.conf file. All configuration data that can be set in the system is defined in the Skeleton Configuration file (see Appendix B, “Skeleton Configuration types (strings or numbers), and defines whether the data is dynamic, static, or constant.
Page 43: Introduction To Mml Command Operation For Hsi
Chapter 3 Provisioning the Cisco HSI Introduction to MML Command Operation for HSI After the HSI software is installed, you can configure additional items. The following MML command examples show how to enable DTMF capability on the HSI. (For a description of the sys_config_static entry and the dtmf parameters, please see the section Initiating an MML Session to Enable DTMF on the HSI The following MML command example shows how to start an MML session and enable DTMF support...
Page 44: Reverting To The Base Configuration
Cisco HSI Configuration Step 2 To display the entire configuration, issue the following command: rtrv-config To display a subset of the configuration, one can issue a command such as the following: rtrv-config:sys_config_static To exit the MML command interpreter, issue the following command: Step 3 quit Reverting to the Base Configuration...
Page 45 Chapter 3 Provisioning the Cisco HSI Table 3-3 Static System Data Parameters Parameter Type HOST_PORT_NUMBER1 [0-65535] HOST_PORT_NUMBER2 [0-65535] VSCA_IPADDR1 STRING VSCA_IPADDR2 STRING VSCB_IPADDR1 STRING VSCB_IPADDR2 STRING VSCA_PORT_NUMBER1 [0-65535] VSCA_PORT_NUMBER2 [0-65535] VSCB_PORT_NUMBER1 [0-65535] VSCB_PORT_NUMBER2 [0-65535] ClipClirSupported STRING RaiSupported STRING DtmfSupportedDirection STRING DtmfSupportedType STRING H225PavoSupported...
Page 46 Cisco HSI Configuration Table 3-3 Static System Data Parameters (continued) Parameter Type PavoRedirPresInd [0-3] CliInDisplaySupported STRING T38MaxVal STRING T38Options STRING AsymmetricHandlingSupported STRING UseConfID STRING Cisco H.323 Signaling Interface User Guide Description The value of the Pavo redirecting number presentation indicator. (If this parameter is not provisioned, the default is Q.931 zero—no indication.) If this parameter is present and set to anything other than “”, the Calling Number is also sent in the DISPLAY IE.
Page 47: Changing Static System Data
Chapter 3 Provisioning the Cisco HSI Table 3-3 Static System Data Parameters (continued) Parameter Type DualCLISupported STRING InjectPi8 STRING 1. PGW = Public Switched Telephone Network (PSTN) Gateway Changing Static System Data To change static system data, you must first determine if it is acceptable to stop currently active calls in 20 seconds.
Page 48: Dynamic System Data
Cisco HSI Configuration Dynamic System Data To modify the dynamic system data parameters in variable for the prov-add, prov-dlt, and prov-ed commands. You need not halt and restart call processing for the changes to take effect. In the following example, the prov-add command adds the dynamic system data parameter OVLDLEVEL1PERCENT to a dynamic configuration file.
Page 49 Chapter 3 Provisioning the Cisco HSI Table 3-4 Dynamic System Data Parameters (continued) Parameter OVLDLEVEL1PERCENT OVLDLEVEL1FILTER OVLDLEVEL1THRESHLOWER CALLS OVLDLEVEL1THRESHUPPER CALLS OVLDLEVEL1THRESHLOWER OVLDLEVEL1THRESHUPPER OVLDLEVEL2PERCENT OVLDLEVEL2FILTER OVLDLEVEL2THRESHLOWER CALLS OVLDLEVEL2THRESHUPPER CALLS OVLDLEVEL2THRESHLOWER OVLDLEVEL2THRESHUPPER OL-4806-01 Rev. A14 Description Indicates what percentage of calls should be rejected when an overload condition occurs.
Page 50: H.323 Stack Configuration
H.323 Stack Configuration Table 3-4 Dynamic System Data Parameters (continued) Parameter OVLDLEVEL3PERCENT OVLDLEVEL3FILTER OVLDLEVEL3THRESHLOWER CALLS OVLDLEVEL3THRESHUPPER CALLS OVLDLEVEL3THRESHLOWER OVLDLEVEL3THRESHUPPER CIAGENTSCANPERIOD ALARMDEBOUNCETIME CALLREFERENCEUSAGE DISKUSAGELIMIT RegFailureReleaseCause H.323 Stack Configuration The parameter name is based on the ASN.1 paths; but, in some cases, the parameter name has been shortened for convenience.
Page 51: Nonprovisionable Data
Chapter 3 Provisioning the Cisco HSI Nonprovisionable Data The parameters in Table 3-5 Nonprovisionable Data Parameters H323_SYS system.manualstart system.pdlname system.delimiter ras.gatekeeper ras.rasmulticastaddress h245.capabilities.manualoperation h245.masterslave.manualoperation q931.manualaccept q931.earlyH245 q931.autoanswer q931.manualcallprocessing q931.h245tunneling MML Provisionable Data H.323 System Parameters The parameters in Table 3-6, use the h323_sys MML name variable for the prov-add, prov-dlt, and prov-ed commands. Stop and restart the application for these changes to take effect.
Page 52 H.323 Stack Configuration Example prov-add:name=q931,maxCalls=2000 The Update Type column in is made: • Immediate means that the effect of the change is immediate. • Start means that the application needs to be restarted for the change to take effect. Next Call means that the next call has the new parameter set. •...
Page 53: Ras Parameters
Chapter 3 Provisioning the Cisco HSI RAS Parameters The parameters in use the ras MML name variable for the prov-add, prov-dlt, and prov-ed commands. In the following example, the prov-add command sets the RAS parameter maxfail to the value 3. Example prov-add:name=ras,maxfail=3 The array index [i] in some of the parameter names in the first column of...
Page 54 H.323 Stack Configuration Table 3-8 RAS Parameters (continued) Parameter Name allowCallsWhenNonReg manualRegistration timeToLive rasPort* compare15bitRasCrv maxRetries* maxMulticastTTL preGrantedArqUse manualDiscovery.ipAddress Cisco H.323 Signaling Interface User Guide 3-14 Description Type If this parameter is present, it NULL allows calls to proceed even if gatekeeper registration has not been done for the PGW 2200.
Page 55: H.245 Parameters
Chapter 3 Provisioning the Cisco HSI Table 3-8 RAS Parameters (continued) Parameter Name manualDiscovery.port gateway.prefix[i] gatekeeperId terminalAlias[i].e164 terminalAlias[i].h323ID endpointVendor.t35CountryCode endpointVendor.t35Extension endpointVendor.manufacturerCode endpointVendor.productId endpointVendor.versionId H.245 Parameters To modify the H.245 parameters listed in prov-dlt and prov-ed commands. In the following example, the prov-add command sets the H.245 parameter masterSlave.timeout to the value 5.
Page 56 H.323 Stack Configuration Table 3-9 H.245 Parameters Parameter Name Description masterSlave.terminalType The terminal type for the PGW 2200. masterSlave.manualResponse If this parameter is present, it cancels automatic acknowledgment of master or slave determination. masterSlave.timeout The maximum time (in seconds) the stack waits before it gives up on the master/slave procedure.
Page 57 Chapter 3 Provisioning the Cisco HSI Table 3-10 H.245 Terminal Capability Codec Parameters (continued) Parameter Name caps.table[i].audio.g722at56k caps.table[i].audio.g722at48k caps.table[i].audio.g7231.maxAudioFrames caps.table[i].audio.g7231.silenceSuppression caps.table[i].audio.g728 caps.table[i].audio.g729 Table 3-11 H.245 Channel Codec Parameters Parameter Name chan[i].name chan[i].audio.g711Alaw64k chan[i].audio.g711Alaw56k chan[i].audio.g711Ulaw64k chan[i].audio.g711Ulaw56k chan[i].audio.g722at64k chan[i].audio.g722at56k chan[i].audio.g722at48k chan[i].audio.g7231.maxAudioFrames chan[i].audio.g7231.silenceSuppression chan[i].audio.g728 chan[i].audio.g729 Table 3-12 H.245 Modes...
Page 58: Codec Selection
H.323 Stack Configuration Codec Selection The Cisco HSI negotiates the media stream codec to establish a match between the PSTN MGCP media gateway (for example, the Cisco AS5xxx series or Cisco MGX series) and the H.323 endpoint or gateway. To match codecs, the MGCP gateway must be configured to match what is expected at the H.323 end.
Page 59 Chapter 3 Provisioning the Cisco HSI Table 3-13 Common Call Control Parameters (continued) Parameter Name Parameter Value A_CC_Interworking 0—No interworking encountered (SS7 all the way) 1—Interworking encountered A_CC_Location 1—User 2—Private local 3—Public local 4—Transit 5—Public remote 6—Private remote 7—International 8—Interworking 9—Local interface 11—Local remote 12—Packet manager...
Page 60 H.323 Stack Configuration Table 3-14 Common Static System Data Parameters Parameter Name Parameter Values CarrierCodeMapping “enabled”—a string that indicates the • feature is enabled. Blank (“”)—indicates the feature is • disabled. “deleted”—indicates that the feature • is disabled. ClipClirSupported “enabled”—a string that indicates the •...
Page 61 Chapter 3 Provisioning the Cisco HSI Table 3-14 Common Static System Data Parameters (continued) Parameter Name Parameter Values NotifyMsgEnabled For example: “enabled”—a string that indicates the • feature is enabled. Blank (“”)—indicates the feature is • disabled “deleted”—indicates that the feature •...
Page 62: Hsi Feature Configuration
HSI Feature Configuration Table 3-16 presents common H.245 parameters for enabling the G.729 codec. Table 3-16 Common H.245 Parameters Parameter Name chan[i].name chan[i].audio.g729 caps.table[i].audio.g729 caps.table[i].entryNo modes[i].name modes[i].audio.g729 The following MML command example shows the command sequence used to provision the H.245 parameters provided in the preceding table for enabling the G.729 codec.
Page 63: Asymmetric Codec Treatment
Chapter 3 Provisioning the Cisco HSI • Configuring G.726 on the Cisco HSI Configuring G.729 Annex and G.729 Annex B • Asymmetric Codec Treatment The Asymmetric Codec Treatment feature averts the potential for inconsistencies in codec selection, which can result if the open channel requests are sent by each endpoint at nearly the same time, so that neither side has received an open channel request prior to sending one.
Page 64: T.38 Fax
HSI Feature Configuration Refer to Cisco PGW and Cisco IOS documentation at www.cisco.com for further information on these commands. T.38 Fax The T.38 Fax feature enables the HSI to alter a call, initially established for voice, to support a fax transmission.
Page 65: Hsi Support For Tech Prefixes
Chapter 3 Provisioning the Cisco HSI Support for the H.225 INFORMATION message is enabled by default. A crafts person can disable H.255 INFORMATION message support through a new property called Information MsgDisabled by issuing the following MML command: prov-add:name=sys_config_static,informationmsgdisabled = "True" HSI Support for Tech Prefixes The Cisco HSI now maps the '*' (asterisk, or star) and '#' (number sign, or hash) H.225 prefixes to the PGW for H.323 to PSTN calls as follows:...
Page 66 HSI Feature Configuration Table 3-17 presents examples of configuration commands that may be required to implement a particular G.Clear configuration. Table 3-17 Configuring Clear Channel Clear Channel Parameters Example Value H245, caps.table[i].audio.gclear “ClearChid” Note H245, 1010, 1011, 1012… caps.table[i].audio.entryNo Note H245, chan[i].audio.gclear “ClearChid”...
Page 67: Configuring G.726 On The Cisco Hsi
Chapter 3 Provisioning the Cisco HSI Configuring G.726 on the Cisco HSI The G.726 codec enables transcoding a PCM channel to or from an ADPCM data stream. The standard supports four data rates:16, 24, 32 and 40 kbit/sec. G.726 capability is advertised by the Cisco HSI and other H.323 gateways/endpoints in H.225 fast-start elements, in H.245 (tunneled or a separate TCP/IP connection) terminal capability (TCS) messages, and open logical channel (OLC) messages.
Page 68 HSI Feature Configuration If a non-preferred G.726 data rate is selected over a higher-preference codec, the HSI will continue with the call using the non-preferred data rate. This is preferable to the alternative (aborting the media stream, invoking an empty capability exchange followed by a re-negotiation of codecs and new OLC messaging). The alternative causes call processing delay and overhead associated with switching media streams.
Page 69 Chapter 3 Provisioning the Cisco HSI Table 3-18 Configuring G.726 (continued) G.726 Parameter H245, caps.table[i].entryNo H245, chan[i].audio.g726-cisco H245, chan[i].name H245, chan[i].audio.g726-cisco H245, modes[i].audio.g726-cisco H245, modes[i].name Configuring Cisco HSI g726-generic H245, caps.table[i].audio.g726-generic OL-4806-01 Rev. A14 Example Value Configuration Example 7261, 7262, … prov-add:name=h245, caps.table[5].entryNo=7261 Set this parameter to...
Page 70 HSI Feature Configuration Table 3-18 Configuring G.726 (continued) G.726 Parameter H245, caps.table[i].audio.g726-generic.bitOrder H245, caps.table[i].audio.g726-generic.maxSPP H245, caps.table[i].entryNo H245, chan[i].audio.g726-generic H245, chan[i].audio.g726-generic.bitOrder 1,2 or 3 H245, chan[i].audio.g726-generic.maxSPP 30, 40 H245, chan[i].name H245, modes[i].audio.g726-generic Cisco H.323 Signaling Interface User Guide 3-30 Example Value Configuration Example 1,2 or 3 prov-add:name=h245,...
Page 71: Configuring G.729 Annex And G.729 Annex B
Chapter 3 Provisioning the Cisco HSI Table 3-18 Configuring G.726 (continued) G.726 Parameter H245, modes[i].audio.g726-generic.bitOrder H245, modes[i].audio.g726-generic.maxSPP H245, modes[i].name Configuring G.729 Annex and G.729 Annex B Table 3-18 presents examples of configuration commands that may be required to implement a particular configuration of G.729 Annex A or G.729 Annex B.
Page 72 HSI Feature Configuration Table 3-19 Configuring G.729 Annex A and G.729 Annex B (continued) G.729 Parameter H245,modes[i].name H245,modes[i].audio.g729AnnexA Cisco H.323 Signaling Interface User Guide 3-32 Example Value Example Configuration “g729AnnexA” prov-add:name=h245,modes[4].name="g729AnnexA" “g729AnnexB” prov-add:name=h245,modes[5].name="g729AnnexB" “g729AnnexA prov-add:name=h245,modes[6].name="g729AnnexAwAnnexB" wAnnexB” “” prov-add:name=h245, modes[4].audio.g729AnnexA="" prov-add:name=h245, modes[5].audio.g729AnnexB="" prov-add:name=h245, modes[6].audio.g729AnnexAwAnnexB=""...
Page 73: Introduction
Managing the Cisco HSI Introduction This chapter provides information about operation and management tasks for the Cisco H.323 Signaling Interface (HSI) application. This chapter contains the following sections: Restarting the Cisco HSI Application, page 4-1 • Stopping Call Processing, page 4-1 •...
Page 74: Starting Call Processing
Starting Call Processing Starting Call Processing To start call processing, use the sta-callproc MML command. For more information about this command, see Stopping the Call Processing Application To stop the call processing application, use the stp-softw MML command. For more information about this command, see Starting the Call Processing Application To start the call processing application, use the sta-softw MML command.
Page 75: Call-Related Measurements
Chapter 4 Managing the Cisco HSI Call-Related Measurements The Cisco HSI application handles all call-related measurements. An SNMP MIB handles the collection of call-related measurement data. The call-related measurements are organized into counter groups. The following MML counter groups are required: RAS (see •...
Page 76 Measurements Table 4-2 Q.931 Counter Group Counter Name Measurement FC_INC_CALL_ATT_TOT H.225 Incoming Fast Connect Call Attempts FC_INC_CALL_SUCC_TOT H.225 Incoming Fast Connect Call Successes FC_OTG _CALL_ATT_TOT H.225 Outgoing Fast Connect Call Attempts FC_OTG_CALL_SUCC_TOT H.225 Outgoing Fast Connect Call Successes V1_INC_CALL_ATT_TOT H.225 Incoming Version 1 Call Attempts V1_INC_CALL_SUCC_TOT H.225 Incoming Version 1...
Page 77 Chapter 4 Managing the Cisco HSI Table 4-3 H.245 Counter Group Counter Name MASTER_SLAVE_ATT_TOT MASTER_SLAVE_SUCC_TOT TERM_CAP_XCHG_ATT_TOT TERM_CAP_XCHG_SUCC_TOT H.245 Terminal Capability OPEN_CH_ATT_TOT OPEN_CH_SUCC_TOT CLOSE_CH_ATT_TOT CLOSE_CH_SUCC_TOT AVG_ROUND_TRIP_DELAY EMPTY_CAP_SET_TOT H323_T38_FAX_ATT_TOT H323_T38_FAX_SUCC_TOT OL-4806-01 Rev. A14 Measurement Type H.245 Master Slave Integer Determination Attempts H.245 Master Slave Integer Determination Successes H.245 Terminal Capability...
Page 78: Resetting Measurements
Overload Table 4-3 H.245 Counter Group (continued) Counter Name ASYMMETRIC_TOT DTMF_ RELAY_ TOT Resetting Measurements The clr-meas MML command resets the measurement counters. This command resets an individual counter or all counters in a counter group. The following are valid counter groups: •...
Page 79: Overload Level 1
Chapter 4 Managing the Cisco HSI Disk usage can trigger a LOW_DISK_SPACE alarm. For more information about this alarm, see Chapter 5, “Troubleshooting Cisco HSI Alarms.” Overload Level 1 Use the following configuration parameters for overload level 1 (see HSI”): OVLDLEVEL1PERCENT •...
Page 80: Setting Overload Data
Overload Setting Overload Data The following MML commands set overload data: 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, filter=normal|all, percent=number The upper parameter specifies the threshold for overload detection, and the lower parameter specifies the hysteresis point at which the overload condition is removed. The lower value should be greater than the upper value of the next lower severity level.
Page 81: Logging
Chapter 4 Managing the Cisco HSI Logging The logging level of one or more service packages is set using the set-log MML command. For more information about this command, see 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.
Page 82: Log Messages
Logging Log Messages Log messages have the following format: Date and timestamp, Package Name, <log level>, LogID:<text of the message>. The following are examples of log messages: Thu Dec 7 03:55:32:837 2000, Infrastructure, <DEBUG>, 205: GWModule Registration - shutdownList() - NbOfItems 10 - Item 8 Thu Dec 7 03:55:32:837 2000, Infrastructure, <DEBUG>, 206 : GWModuleRegistration - shutdownList() - NbOfItems 10 - Item 9...
Page 83: Setting Logging Levels
Chapter 4 Managing the Cisco HSI We strongly recommend that you set all packages to log level 0x0000 in a live network. Set them to Note higher levels only when you debug on an offline network. Setting Logging Levels The set-log MML command dynamically alters the log level setting during the execution of the system. However, the set-log MML command does not affect the logging level of any current MML processes.
Page 84: Retrieving Call Gapping Data
Gapping Step 4 Enter the set-gapping MML command. For example, to gap 60 percent of all calls for both directions, enter: set-gapping:both:calltype=all,percent=60 Retrieving Call Gapping Data To retrieve the current levels of call gapping for all gapping clients, enter the rtrv-gapping command. The command displays text similar to the following: Client Name Overload...
Page 85: Introduction
Troubleshooting Cisco HSI Alarms Introduction This chapter contains information about Cisco H.323 Signaling Interface (HSI) alarms, troubleshooting procedures for these alarms, and information about detailed logging. This chapter contains the following sections: Alarms Overview, page 5-1 • Retrieving Alarm Messages, page 5-3 •...
Page 86: Retrieving And Reporting Alarms
Alarms Overview Table 5-1 Alarm Severity Levels Severity Level Critical Major Minor Informational Retrieving and Reporting Alarms Events with a severity level of critical, major, or minor are classified as alarms and can be retrieved through the Man-Machine Language (MML) interface and a Simple Network Management Protocol (SNMP) manager.
Page 87: Retrieving Alarm Messages
Chapter 5 Troubleshooting Cisco HSI Alarms Retrieving Alarm Messages Alarms can be displayed in noncontinuous mode or in continuous mode. Noncontinuous Mode To display all current alarms, use the rtrv-alms MML command. Figure 5-1 shows an example of an alarm message displayed with the rtrv-alms MML command (noncontinuous mode).
Page 88: Acknowledging And Clearing Alarms
Acknowledging and Clearing Alarms Table 5-3 Elements of Continuous Mode Messages Element systemId YYYY-MM-DD hh-mm-ss-ms severity almCat Acknowledgement Indicates whether the alarm has been acknowledged. Acknowledging and Clearing Alarms To acknowledge that an alarm is recognized but not cleared, use the ack-alm MML command. See Appendix A, “MML User Interface and Command Reference,”...
Page 89: Alarms List
Chapter 5 Troubleshooting Cisco HSI Alarms Alarms List Table 5-4 lists alarms and information events. Troubleshooting information for each of the alarms and information events can be found in the Table 5-4 Alarms and Informational Events Alarm Event and Reference H323_STACK_FAILURE, page 5-6 CONFIGURATION_FAILURE, page 5-6 EISUP_PATH_FAILURE, page 5-7...
Page 90: Troubleshooting
Troubleshooting Troubleshooting This section provides troubleshooting procedures for the alarms listed in H323_STACK_FAILURE Description Irrecoverable failure in the RADVision stack. This alarm is reported to the management interface and can be obtained with SNMP. Severity Level and Trap Type The severity level is critical. The trap type is 4. Cause The H.323 RADVision stack has failed to correctly initialize on an application startup.
Page 91: Severity Level And Trap Type
Chapter 5 Troubleshooting Cisco HSI Alarms Cause A major error has occurred in the configuration of the software packages. This is a potentially nonrecoverable situation that requires an application restart. Troubleshooting To clear the CONFIGURATION_FAILURE alarm, complete the following steps: Step 1 Use the restart-softw:init command to restart the application and revert to the base configuration.
Page 92: Troubleshooting
Troubleshooting GATEKEEPER_INTERFACE_FAILURE This alarm has not been implemented. GENERAL_PROCESS_FAILURE Description A general process failure has occurred. This alarm is reported to the management interface and can be obtained with SNMP. Severity Level and Trap Type The severity level is major. The trap type is 4. Cause The Cisco HSI (GWmain program) quit unexpectedly (that is, there were no requests to stop or restart the application).
Page 93: Low_Disk_Space
Chapter 5 Troubleshooting Cisco HSI Alarms Troubleshooting To clear the IP link failure alarm, complete the following steps: Use the rtrv-dest command to assess which PGW 2200 (standby or active) has been lost. Step 1 Check the network connections, cables, and routers for that system. Step 2 Use the clr-alm MML command to attempt to clear the alarm.
Page 94: Vsc_Failure
Troubleshooting Cause The OVERLOAD_LEVEL3 alarm is triggered when the CPU occupancy or the number of active calls rises above the upper limits set in the overload configuration for level 3. Gapping is then initiated. Troubleshooting To clear the OVERLOAD_LEVEL3 alarm, complete the following steps: Step 1 Wait for the number of calls to drop.
Page 95: Overload_Level2
Chapter 5 Troubleshooting Cisco HSI Alarms OVERLOAD_LEVEL2 Description An overload level 2 condition exists. This alarm is reported to the management interface and can be obtained with SNMP. This alarm automatically clears when the CPU occupancy or the number of active calls drops below the lower limits set in the overload configuration for level 2.
Page 96: Endpoint_Call_Control_Interface_Failure
Troubleshooting ENDPOINT_CALL_CONTROL_INTERFACE_FAILURE Description An individual call failure has occurred. This informational event is reported to the management interface and can be obtained with SNMP. Severity Level and Trap Type The severity level is information. The trap type is 3. Cause The RADVision stack reports this alarm.
Page 97: Gapped_Call_Normal
Chapter 5 Troubleshooting Cisco HSI Alarms GAPPED_CALL_NORMAL Description A normal call has been rejected due to call gapping. This informational event is reported to the management interface and can be obtained with SNMP. Severity Level and Trap Type The severity level is information. The trap type is 2. Cause The GAPPED_CALL_NORMAL alarm is triggered when gapping levels cause a normal call to be rejected.
Page 98: Overload_Level1
Troubleshooting Troubleshooting To clear the GAPPED_CALL_PRIORITY informational event, complete the following steps: Change the MML gapping levels to less than 100 percent and change the call type to normal. Step 1 Change the provisioned overload call filter type to normal. Step 2 OVERLOAD_LEVEL1 Description...
Page 99: Provisioning_Session_Timeout
Chapter 5 Troubleshooting Cisco HSI Alarms Cause The provisioning session has been inactive for 20 minutes. The provisioning session will be closed if there is no activity within the next 5 minutes. Troubleshooting Ensure that activity in the provisioning session occurs at least every 20 minutes. PROVISIONING_SESSION_TIMEOUT Description The current session has been terminated.
Page 100: Detailed Logging
Detailed Logging Troubleshooting This is an informational event. Detailed Logging Logging occurs on 16 different levels for each package, and the logging mask (which is a 16-bit number from 0x0000 to 0xFFFF) allows each specific log level to be turned on and off. The most-significant-bit positions correspond to higher (that is, more processor intensive) levels of debugging.
Page 101: Appendix
MML User Interface and Command Reference Introduction This appendix provides information about Man-Machine Language (MML) command syntax and conventions, batch files, and procedures for starting and stopping MML sessions in the Cisco H.323 Signaling Interface (HSI) application. The appendix contains the following sections: Starting an MML Command Session in the Cisco HSI, page A-1 •...
Page 102: Mml Commands
MML Commands MML Commands To execute MML commands, log in to Cisco HSI and perform one of the following tasks: Start the MML session (see the • command. Type a batch file command to start an MML session (see the •...
Page 103: Case Sensitivity
Appendix A MML User Interface and Command Reference The MML commands can be interpreted and monitored through a network Transaction Language 1 (TL1) interface. The TL1 symbols shown in Table A-2 TL1 Symbols Used in MML Symbol & Case Sensitivity Command names and parameter names are not case sensitive You can enter commands and parameters in either upper- or lowercase.
Page 104: Batch Files
Batch Files Batch Files The Cisco HSI application supports the use of batch files. You can create an ASCII file of MML provisioning commands for use as a batch file. You can also use a script file. When the commands are read, the Cisco HSI executes them sequentially.
Page 105: Mml Responses
Appendix A MML User Interface and Command Reference The following example shows the start of a batch file named nolog.bat with these contents: prov-sta:srcver=active,dstver=nolog prov-ed:name=logging,eisup=0x0000 prov-cpy and this output: gp-capetown-16-> mml -b nolog.bat Starting in batch mode. Connecting to port 10129 on host gp-capetown Welcome to the Cisco H.323 Signaling Interface.
Page 106: Error Messages
MML Help Error Messages If an MML command does not perform, an error message is displayed. messages and their descriptions. Table A-4 MML Error Messages and Descriptions Error Message DENY ICNV IDNV IISP IITA IPRM SABT SNVS SNSP SROF MML Help MML has an online help feature.
Page 107: Mml Command Reference
Appendix A MML User Interface and Command Reference MML Command Reference This section describes the following MML commands: ack-alm • clr-alm • clr-meas • diaglog • • help • prov-add • • prov-cpy • prov-dlt prov-ed • • prov-exp prov-rtrv •...
Page 108: Ack-Alm
ack-alm • stp-call stp-callproc • stp-softw • stp-trc • ack-alm The ack-alm command acknowledges that an alarm event is recognized but does not clear the alarm. ack-alm:event=alarm event Syntax Description alarm event Usage Guidelines The format of the alarm category name must be the same as the format of the alarm category name that the rtrv-alms command displays.
Page 109: Clr-Alm
Appendix A MML User Interface and Command Reference clr-alm The clr-alm command clears an alarm event. clr-alm:event=alarm event Syntax Description alarm event Usage Guidelines The alarm category must match the format shown in the alarm when the rtrv-alms command displays it.
Page 110: Diaglog
diaglog Examples In this example, a measurement counter, GK_DISC_ATT_TOT (Gatekeeper Discovery Attempts), is reset in the counter group RAS: gw mml> clr-meas:RAS GW Signaling Interface SUCC mml> mml> clr-meas:RAS:name=GK_DISC_ATT_TOT GW Signaling Interface SUCC Related Commands Command rtrv-ctr diaglog The diaglog command starts and stops event logging into a diagnostics log. diaglog:file name:start | stop Syntax Description file name...
Page 111: Help
Appendix A MML User Interface and Command Reference The h command redisplays a command or a series of commands. Items displayed depend on a specified number or range. If no number is specified, only the last command is displayed. h[::start=number[,end=number]] Syntax Description start Examples...
Page 112 help Examples The command shown in the following example displays help for a specific command: mml> help:rtrv-ctr H323 Signalling Gateway M SUCC Purpose: Format: Description: * counter group -- The name of an MML counter group (RAS, Q931 or H245) Example: If you enter the help command without a parameter, the help file displays information about all available commands.
Page 113: Prov-Add
Appendix A MML User Interface and Command Reference prov-add The prov-add command adds a component to the Cisco HSI. prov-add:name=MML name,param name=param value,... Syntax Description MML name param name param value Usage Guidelines To define more than one parameter, enter additional param name=param value descriptions on the command line.
Page 114: Prov-Cpy
prov-cpy prov-cpy The prov-cpy command activates the current provisioning session. If any client-level parsing fails during the prov-cpy command, the system might prompt for confirmation to force the HSI to activate the configuration (prov-cpy[:confirm]). However, we recommend that you never use prov-cpy:confirm unless you are asked to do so by Cisco.
Page 115: Prov-Dlt
Appendix A MML User Interface and Command Reference prov-dlt The prov-dlt command deletes a provisioned component. It allows you to delete a parameter rather than deleting the MML group. prov-dlt:name=MML name prov-dlt:name=MML name,param=param name prov-dlt:name=MML name param name Syntax Description MML name param name Usage Guidelines...
Page 116: Prov-Ed
prov-ed Command prov-rtrv prov-sta prov-stp prov-ed The prov-ed command modifies a provisioned component. prov-ed:name=MML name,param name=param value,... Note Enter only those parameters that must be modified. Syntax Description MML name param name param value Usage Guidelines To change more than one parameter, enter additional param name=value descriptions on the command line.
Page 117: Prov-Exp
Appendix A MML User Interface and Command Reference Related Commands Command prov-add prov-cpy prov-dlt prov-exp prov-rtrv prov-sta prov-stp prov-exp The prov-exp command exports the current provisioned configuration of the Cisco HSI in MML command form to a file. With this configuration file, you can prime a system with a cloned configuration from an existing system.
Page 118: Prov-Rtrv
prov-rtrv Related Commands Command prov-add prov-cpy prov-dlt prov-ed prov-rtrv prov-sta prov-stp prov-rtrv The prov-rtrv command retrieves information about an existing provisioning session. prov-rtrv:name=MML name prov-rtrv:all prov-rtrv:session prov-rtrv:list The prov-rtrv:list command is the only prov-rtrv command that can be executed outside of a Note provisioning session.
Page 119 Appendix A MML User Interface and Command Reference Usage Guidelines Chapter 3, “Provisioning the Cisco HSI,” associated values. Examples The prov-rtrv command shown in the following example displays information about the MML name ras: gw mml> prov-rtrv:name=ras H323 Signaling Interface Sun Jan 7 14:46:01 2001 M SUCC MML Name : ras.
Page 120: Prov-Sta
prov-sta prov-sta The prov-sta command establishes a provisioning session. The data files are copied from the source version to the destination version. prov-sta::srcver=version,dstver=version Syntax Description srcver=version dstver=version Usage Guidelines If the source and destination filenames are the same, the new configuration overwrites the old configuration.
Page 121: Prov-Stp
Appendix A MML User Interface and Command Reference The MML command shown in the following example starts a provisioning session, opens the existing configuration named ver1, and saves the updated configuration as ver2: gw mml> PROV-STA::SRCVER="ver1", DSTVER="ver2" Related Commands Command prov-add prov-cpy prov-dlt...
Page 122 prov-stp Examples The MML command in the following example terminates the current provisioning session: gw mml> prov-stp:confirm H323 Signaling Interface Sun Jan 7 14:46:01 2001 M SUCC Successfully stopped provisioning session "ver1" The MML command in the following example terminates the uk9 provisioning session: gw mml>...
Page 123: Quit
Appendix A MML User Interface and Command Reference quit The quit command ends an MML session. quit Syntax Description This command has no arguments or keywords. Examples The command in the following example ends an MML session. gw mml> quit radlog The radlog command starts or stops RADVision logging into a specified log file.
Page 124: Restart-Softw
restart-softw restart-softw The restart-softw command restarts the call processing application. It applies the provisioning data specified in the configVersion (if present) that overrides the existing active provisioning data. restart-softw[:configVersion][:confirm] Syntax Description configVersion confirm Examples In the following example, the call processing application restarts using the etc/GWmain.conf configuration files as the provisioning data: gw mml>...
Page 125: Rtrv-Alms
Appendix A MML User Interface and Command Reference rtrv-alms The rtrv-alms command retrieves all active alarms. rtrv-alms rtrv-alms:cont Syntax Description cont Examples In the following example, the output contains the standard alarm definition and also a NACK or an ACK for noninformational alarms.
Page 126: Rtrv-Calls
rtrv-calls rtrv-calls The rtrv-calls command displays all actively connected calls. If the time elapsed parameter is provided (in units of minutes), calls display only if they exceed the specified time. The output includes the call direction, time connected, calling and called address, and call reference. rtrv-calls[:time elapsed] Syntax Description time elapsed...
Page 127: Rtrv-Dest
Appendix A MML User Interface and Command Reference rtrv-dest The rtrv-dest command retrieves status information about the IP links and EISUP signalling path to the PGW 2200. The output produced by this command shows the states of the H323 signalling gateway external interfaces to the PGW 2200s: •...
Page 128: Rtrv-Gapping
rtrv-gapping rtrv-gapping The rtrv-gapping command retrieves information about overload-triggered call gapping. The following information displays: The active or inactive status of call gapping • The percentage of calls that are gapped • The type of calls to which gapping is applied •...
Page 129: Rtrv-Mml
Appendix A MML User Interface and Command Reference Examples In the following example, the command displays the logging levels of all packages: gw mml> rtrv-log:all H323 Signaling Interface Thu Dec 14 16:28:44 2000 M RTRV Logging levels: Application...0x0000 CallControl...0xFFFF Connection...0x0000 DataManager...0x0000 Eisup...0xFFFF FaultManager...0x0000...
Page 130: Rtrv-Ne
H323 Signaling Interface Thu Dec 14 16:29:19 2000 M RTRV Type: H323 Signaling Interface Hardware platform: Sun netra t1 Vendor: Cisco Systems, Inc. Location: H323 - GW1 Version: R1_1_0 Platform Status: Signaling interface: Active Call processing: Running...
Page 131: Rtrv-Overload
Appendix A MML User Interface and Command Reference Examples In the following example, the command displays information about the Cisco HSI status: gw mml> rtrv-ne-health VSC H-323 Signaling Interface - H323-GW1 2000-06-20 10:04:28 M RTRV CPU Load: Disk space: Number of connected calls: 23 Number of calls in setup: rtrv-overload The rtrv-overload command displays overload status information and value settings for the three...
Page 132: Rtrv-Softw
rtrv-softw Command Related Commands set-overload rtrv-softw The rtrv-softw command displays the status of the Cisco HSI and call processing activity. The following software states can be displayed for the Cisco HSI: Not running • Starting • Active • Restart pending •...
Page 133: Set-Dest-State
Appendix A MML User Interface and Command Reference set-dest-state The set-dest-state command changes the service state of an IP link or E-ISUP signaling path to IS (in service) or OOS (out of service). set-dest-state:ipLink1toVscA:IS|OOS set-dest-state:ipLink2toVscA:IS|OOS set-dest-state:ipLink1toVscB:IS|OOS set-dest-state:ipLink2toVscB:IS|OOS set-dest-state:EisupPath:IS|OOS set-dest-state:ipLinkNms:IS|OOS Syntax Description Examples In the following example, the command changes the service state of an IP link signaling path to IS: gw mml>...
Page 134: Set-Gapping
set-gapping set-gapping The set-gapping command sets the type of calls to be gapped. set-gapping: inc | otg | both : calltype=normal | all, percent=number Syntax Description both normal number Usage Guidelines If call gapping is set to 100 percent, all calls are gapped irrespective of the normal or all parameter setting.
Page 135: Set-Log
Appendix A MML User Interface and Command Reference set-log The set-log command sets the logging level of a package or all packages. set-log:package:level=level, [confirm] set-log:all:level=level, [confirm] Syntax Description package level confirm 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.
Page 136: Set-Overload
set-overload 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 level 1 | level 2 | level 3 Overload behavior can be provisioned at three separate levels: 1, 2, and 3 lower=number upper=number Usage Guidelines...
Page 137: Sta-Callproc
Appendix A MML User Interface and Command Reference Related Commands Command rtrv-overload sta-callproc The sta-callproc command starts call processing. sta-callproc Syntax Description This command has no arguments or keywords. Examples In the following example, the command starts call processing: gw mml> sta-softw gw mml>...
Page 138: Sta-Trc
sta-trc Related Commands Command sta-callproc sta-trc The sta-trc command starts the call processing tracing function. sta-trc:Calltype=calltype,TraceLevel=trace level[,CdAddress=address] [,CgAddress=address],log=filename[,prd=n] Syntax Description Calltype=calltype TraceLevel=trace level CdAddress=address CgAddress=address log=filename prd=n Defaults The default trace for all calls is 30 minutes. Usage Guidelines Only one trace command at a time can be active. If an additional request is issued, the command is rejected with a call trace already active indication.
Page 139: Stp-Call
Appendix A MML User Interface and Command Reference Examples In the following example, the command starts the call processing tracing function: gw mml> sta-trc:Calltype=both, TraceLevel=terse, dAddress=012,CgAddress=013, log=tlog.txt, prd=10 H323 Signaling Interface Day Mon 1 hh:mm:ss YYYY M SUCC Related Commands Command stp-trc stp-call...
Page 140: Stp-Callproc
stp-callproc stp-callproc The stp-callproc command stops further call processing by immediately terminating the handling of new call requests. stp-callproc[:timeout=T] Syntax Description timeout Examples In the following example, the command stops further call processing by immediately terminating the handling of new call requests: gw mml>...
Page 141: Stp-Trc
Appendix A MML User Interface and Command Reference stp-trc The stp-trc command halts the currently active tracing and closes the trace file. stp-trc Syntax Description This command has no arguments or keywords Examples In the following example, the command halts the currently active tracing and closes the trace file: gw mml>...
Page 142 Appendix A MML User Interface and Command Reference stp-trc Cisco H.323 Signaling Interface User Guide A-42 OL-4806-01 Rev. A14...
Page 143: Appendix
Skeleton Configuration File Provisionable and configurable data elements within the Cisco H.323 Signaling Interface (HSI) are grouped as dynamic, static, or constant data. You can modify dynamic and static data through the provisioning MML commands. At startup, the Cisco HSI reads a skeleton file, which contains information for every configurable item within the system.
Page 144: Appendix B Skeleton Configuration File
#****** sys_config_static ************************ #Static SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC Cisco H.323 Signaling Interface User Guide Appendix B Nodeid HOST_PORT_NUMBER1...
Page 145 Appendix B Skeleton Configuration File SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC...
Page 146 SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC SYS_CONFIG_STATIC Cisco H.323 Signaling Interface User Guide CC_EC_PreemptionCctUnavailable CC_EC_Prefix0DialledInError CC_EC_Prefix1DialledInError...
Page 147 Appendix B Skeleton Configuration File #****** system ************************ #Static H323_SYS H323_SYS H323_SYS H323_SYS H323_SYS H323_SYS H323_SYS H323_SYS H323_SYS H323_SYS #****** sys_config_dynamic************* #Dynamic SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC...
Page 148 SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC SYS_CONFIG_DYNAMIC #****** ras ************************ #Static manualRAS #****** ras ************************ #Dynamic responseTimeOut maxFail allowCallsWhenNonReg manualRegistration timeToLive rasPort compare15bitRasCrv maxRetries maxMulticastTTL preGrantedArqUse Cisco H.323 Signaling Interface User Guide OvldLevel2ThreshUpperCPU OvldLevel3Percent OvldLevel3Filter OvldLevel3ThreshLowerCalls OvldLevel3ThreshUpperCalls OvldLevel3ThreshLowerCPU OvldLevel3ThreshUpperCPU CiAgentScanPeriod...
Page 149 Appendix B Skeleton Configuration File #****** q931 ************************ #Dynamic Q931 Q931 Q931 Q931 Q931 Q931 Q931 Q931 #****** h245 ************************ #Dynamic H245 H245 H245 H245 H245 H245 H245 H245 H245 H245 H245 H245 H245 H245 caps.table[i].audio.g711Alaw64k H245 caps.table[i].audio.g711Alaw56k H245 caps.table[i].audio.g711Ulaw64k H245 caps.table[i].audio.g711Ulaw56k H245...
Page 150 H245 caps.table[i].audio.g7231.maxAudioFrames H245 caps.table[i].audio.g7231.silenceSuppression H245 chan[i].name H245 chan[i].audio.g711Alaw64k H245 chan[i].audio.g711Alaw56k H245 chan[i].audio.g711Ulaw64k H245 chan[i].audio.g711Ulaw56k H245 chan[i].audio.g722at64k H245 chan[i].audio.g722at56k H245 chan[i].audio.g722at48k H245 chan[i].audio.g728 H245 chan[i].audio.g729 H245 chan[i].audio.g7231.maxAudioFrames H245 chan[i].audio.g7231.silenceSuppression H245 modes[i].name H245 modes[i].audio.g711Alaw64k H245 modes[i].audio.g711Alaw56k H245 modes[i].audio.g711Ulaw64k H245 modes[i].audio.g711Ulaw56k H245 modes[i].audio.g722at64k H245 modes[i].audio.g722at56k H245...
Page 151 Appendix B Skeleton Configuration File Logging FaultManager Logging Gapping Logging H323 Logging Infrastructure Logging Overload Logging ProcessManager Logging Provisioning Logging Signal Logging Snmp Logging SnmpSubagent Logging Statistics Logging Trace Logging UserInterface Logging Configuration Logging Timer Logging EISUP Logging OTLogging #### Call Control Package CCPackage CCPackage CCPackage...
Page 152 CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage Cisco H.323 Signaling Interface User Guide B-10 A_CC_BNumDataNOA A_CC_BNumDataNPI...
Page 153 Appendix B Skeleton Configuration File CCPackage CCPackage CCPackage # Cause code map CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CCPackage CC_EC_FacilityRejected CCPackage CCPackage CC_EC_NormalUnspecified CCPackage CC_EC_NoCircuitAvailable CCPackage CC_EC_NetworkOutOfOrder CCPackage...
Page 154 CCPackage CC_EC_PrecedenceBlocked CCPackage CC_EC_ResourcesUnavailUnspec CCPackage CC_EC_QualityUnavail CCPackage CC_EC_ReqFacilityNotSubscr CCPackage CC_EC_OutgoingCallsBarredInCug CCPackage CC_EC_IncomingCallsBarredInCug CCPackage CC_EC_BearcapNotAuthorized CCPackage CC_EC_BaercapNotAvail CCPackage CC_EC_InconOutgoingAccAndSubClass CCPackage CC_EC_ServiceOrOptionNotAvail CCPackage CC_EC_BearcapNotImp CCPackage CC_EC_ChTypeNotImp CCPackage CC_EC_ReqFacilityNotImp CCPackage CC_EC_OnlyRestrictDigInfoBearer CCPackage CC_EC_ServiceOrOptionNotImpUnspec CCPackage CC_EC_InvalidCallReferenceValue CCPackage CC_EC_ChIdNotExist CCPackage CC_EC_SuspendExistButNotThisId CCPackage CC_EC_CallIdInUse CCPackage CC_EC_NoCallSuspended CCPackage CC_EC_CallIdHasBeenCleared CCPackage...
Page 155 Appendix B Skeleton Configuration File CCPackage CC_HC_MisdialedTrunkPrefix CCPackage CC_HC_ChannelUnacceptable CCPackage CCPackage CC_HC_Preemption CCPackage CCPackage CC_HC_NormalCallClearing CCPackage CC_HC_UserBusy CCPackage CC_HC_NoUserresponding CCPackage CC_HC_NoAnswerFromAlertedUser CCPackage CC_HC_SubscriberAbsent CCPackage CC_HC_CallRejected CCPackage CC_HC_NumberChanged CCPackage CC_HC_RedirectionToNewDestination CCPackage CC_HC_ExchangeRouteError CCPackage CC_HC_NonSelectedUserClearing CCPackage CC_HC_DestinationOutOfOrder CCPackage CC_HC_InvalidNumberFormat CCPackage CC_HC_FacilityRejected CCPackage CC_HC_ResponceToStatusEnquiry CCPackage CC_HC_NormalUnspecified...
Page 156 CCPackage CCPackage CC_HC_ChannelTypeNotImplemented CCPackage CC_HC_RequestedFacilityNotImplemented CCPackage CCPackage CC_HC_ServiceOrOptionNotImplemented CCPackage CC_HC_InvalidCallreferenceValue CCPackage CC_HC_IdentifiedChannelDoesnotExist CCPackage CC_HC_ASuspendedCallExistsThisCallIdDoesNot CCPackage CC_HC_CallIdentityInUse CCPackage CC_HC_NoCallSuspended CCPackage CC_HC_CallHavingTheRequestedCallIdHasBeenCleared C CCPackage CC_HC_UserNotMemberOfCUG CCPackage CC_HC_IncompatibleDestination CCPackage CC_HC_NonExistantCUG CCPackage CC_HC_InvalidTransitNetworkSelection CCPackage CC_HC_InvalidMessage CCPackage CC_HC_MandatoryInformationElementIsMissing CCPackage CC_HC_MessageTypeNonExistantOrNotImplemented CCPackage CC_HC_MessageTypeNotCompatibleWithStateOrNonExistantOrNotImplemented C STRING CCPackage CC_HC_InformationElementParameterNonExistantOrNotImplemented C CCPackage CC_HC_InvalidInformationElementContents...
Page 157 Appendix B Skeleton Configuration File # Priority treatment determines the treatment of priority calls # during gapping. # GapAlways indicates priority calls are treated as normal calls # GapNever indicate priority calls are never to be gapped # GapOn100PercentGapping indicates priority calls are only gapped # when 100 percent gapping is applied.
Page 158 Trace Trigger2.h323.CalledPartyNumber Trace Trigger2.h323.OriginatingIPAddress Trace Trigger2.h323.OriginatingIPMask Trace Trigger2.h323.TerminatingIPAddress Trace Trigger2.h323.TerminatingIPMask Trace Trigger3.eisup.CallingPartyNumber Trace Trigger3.eisup.CalledPartyNumber Trace Trigger3.h323.CallingPartyNumber Trace Trigger3.h323.CalledPartyNumber Trace Trigger3.h323.OriginatingIPAddress Trace Trigger3.h323.OriginatingIPMask Trace Trigger3.h323.TerminatingIPAddress Trace Trigger3.h323.TerminatingIPMask Trace Trigger4.eisup.CallingPartyNumber Trace Trigger4.eisup.CalledPartyNumber Trace Trigger4.h323.CallingPartyNumber Trace Trigger4.h323.CalledPartyNumber Trace Trigger4.h323.OriginatingIPAddress Trace Trigger4.h323.OriginatingIPMask Trace Trigger4.h323.TerminatingIPAddress Trace Trigger4.h323.TerminatingIPMask Trace...
Page 159 Appendix B Skeleton Configuration File Trace TriggerGate2 Trace TriggerGate3 Trace TriggerGate4 Trace TriggerGate5 ## Package EISUP #The period for CISCO's RUDP timer manager in milli seconds EISUP RUDP_TIMER_CHECK_PERIOD_MSEC #The time to wait before failing over to another vsc. EISUP WAIT_TIME_BEFORE_FAIL_OVER_MILLI_SEC ## Package Application Application DefaultCallProcessingStatus...
Page 160 H323 maxTimers H323 tickPeriod H323 defaultSDPt H323 overrideConfig H323 defaultRadLog ## Statistics Statistics StatLogFileName Statistics StatOutputTime # Test entries for provisioning tests. NumberNoRangeConst NumberRangeDynamic2_4 H245 NumberNoRangeConst H245 NumberRangeStatic1_4 Q931 QuotedDynamic Q931 NonQuotedConst Q931 ConnectTimeoutConst Cisco H.323 Signaling Interface User Guide B-18 Appendix B Skeleton Configuration File...
Page 161: Appendix
A P P E N D I X Example of an HSI Configuration File This appendix presents an example of an HSI configuration file. The configuration file does not contain a complete list of all configurable items. Note #verified # $Id: GWmain.base.conf,v 1.6 2002/09/09 15:27:10 syousaf Exp $ # This is the base configuration file that is concatenated to # a file derived from questions at install time, to generate the GWmain.conf # file, which is used by the Application GWmain.
Page 162 Connection #Connection DataManager #Eisup Eisup FaultManager Gapping H323 Infrastructure Overload ProcessManager Provisioning Signal Snmp SnmpSubagent Statistics Trace UserInterface ################################################################################### # H323 Service Package # Not modifiable at runtime (Static Provisionable Data) Package = H323 maxTimers = 20 tickPeriod = 1000 defaultSDPt = "v=0\r\no=\r\ns=\r\nt=0 0\r\nc=IN IP4 0.0.0.0\r\nm=audio 0 RTP/AVP 0 8\r\n"...
Page 163 Appendix C Example of an HSI Configuration File # Not modifiable at runtime (Static Provisionable Data) Package = H323_SYS maxCalls = 2500 maxChannels = 2 ################################################################################### # Q931 RADVIsion PACKAGE Package = Q931 responseTimeOut = 60 connectTimeOut = 180 callSignalingPort = 1720 maxCalls = 2500 #notEstablishControl = overlappedSending =...
Page 164 Appendix C Example of an HSI Configuration File #manualRegistration = endpointVendor.productID = "GoldWing" endpointVendor.t35CountryCode = 11 endpointVendor.t35Extension = 11 endpointVendor.manufacturerCode = 9 timeToLive = 600 rasPort = 0 #compare15bitRasCrv = maxRetries = 3 maxMulticastTTL = 3 preGrantedArqUse = direct ################################################################################### #### # H245 RADVision PACKAGE # Dynamically Provisionable except for manualOperation(s)
Page 165 Appendix C Example of an HSI Configuration File caps.table[3].entryNo = 728 caps.table[3].audio.g728 = 20 chan[1].name = g711Alaw64k chan[1].audio.g711Alaw64k = 20 chan[2].name = g711Ulaw64k chan[2].audio.g711Ulaw64k = 20 chan[3].name = g728 chan[3].audio.g728 = 20 modes[1].name = g711Alaw64k modes[1].audio.g711Alaw64k = modes[2].name = g711Ulaw64k modes[2].audio.g711Ulaw64k = #modes[3].name = g728 #modes[3].audio.g728 =...
Page 166 Appendix C Example of an HSI Configuration File A_CC_tEchoCancIr = A_CC_tLineAccess = A_CC_BNumDataNOA = # CalledPN A_CC_BNumDataNPI = A_CC_BNumDataINN = A_CC_ANumDataNOA = # CallingPN A_CC_Clir = A_CC_ANumDataSI = A_CC_ANumDataNPI = A_CC_A_Cli = A_CC_oLinecall = # CallingPC A_CC_Location = # CauseInd A_CC_CodeStandard = A_CC_ProgressRestrict = # Event Info...
Page 167 Appendix C Example of an HSI Configuration File # CC: Call Control, EC: Eisup Cause, HC: H323 Cause # For the H323 cause code values see ITU-T: Q.850 # The mappings below are considered constant and not provisionable. # They can be made provisionable by moving them from the CCPackage # to the SYS_CONFIG_STATIC package.
Page 168 CC_EC_NormalUnspecified CC_EC_NoCircuitAvailable CC_EC_NetworkOutOfOrder CC_EC_PermanentFrameModeOos CC_EC_PermanentFrameModeOperational = CC_HC_PermanentFrameModeConnectionOperational CC_EC_TemporaryFailure CC_EC_SwitchingEquipCongestion CC_EC_AccessInfoDiscarded CC_EC_ReqCircuitUnavail CC_EC_PrecedenceBlocked CC_EC_ResourcesUnavailUnspec CC_EC_QualityUnavail CC_EC_ReqFacilityNotSubscr CC_EC_OutgoingCallsBarredInCug CC_EC_IncomingCallsBarredInCug CC_EC_BearcapNotAuthorized CC_EC_BaercapNotAvail CC_EC_InconOutgoingAccAndSubClass CC_EC_ServiceOrOptionNotAvail CC_EC_BearcapNotImp CC_EC_ChTypeNotImp CC_EC_ReqFacilityNotImp CC_EC_OnlyRestrictDigInfoBearer CC_EC_ServiceOrOptionNotImpUnspec CC_EC_InvalidCallReferenceValue CC_EC_ChIdNotExist CC_EC_SuspendExistButNotThisId CC_EC_CallIdInUse CC_EC_NoCallSuspended CC_EC_CallIdHasBeenCleared CC_EC_UserNotMemberOfCug CC_EC_IncompatibleDest CC_EC_NonExistentCug CC_EC_InvalidTns CC_EC_InvalidMsgUnspec CC_EC_MandatoryElementMissing CC_EC_MsgTypeNotImp Cisco H.323 Signaling Interface User Guide Appendix C Example of an HSI Configuration File = CC_HC_NormalUnspecified...
Page 169 Appendix C Example of an HSI Configuration File CC_EC_MsgTypeNotImpOrWrongState = CC_HC_MessageTypeNotCompatibleWithStateOrNonExistantOrNotImplemented CC_EC_ElemTypeNotImp = CC_HC_InformationElementParameterNonExistantOrNotImplemented CC_EC_InvalidElemContents CC_EC_MsgInWrongState CC_EC_RecoveryOnTimerExpiry CC_EC_ParamUnrecPassed # When the H323 cause on the left is received from H323, # the Eisup cause on the right is sent to Eisup. # Note: the reverse is not true, this is a one way mapping.
Page 170 CC_HC_NoCircuitChannelAvailable CC_HC_NetworkOutOfOrder CC_HC_PermanentFrameModeConnectionOutOfService = CC_EC_PermanentFrameModeOos CC_HC_PermanentFrameModeConnectionOperational = CC_EC_PermanentFrameModeOperational CC_HC_TemporaryFailure CC_HC_SwitchingEquipmentCongestion CC_HC_AccessInformationDiscarded CC_HC_RequestedCircuitChannelNotAvailable CC_HC_PrecedenceCallBlocked CC_HC_ResourceUnavailable CC_HC_QualityOfServiceNotAvailable CC_HC_RequestedFacilityNotSubscribed CC_HC_OutgoingCallsBaredWithinCUG CC_HC_IncomingCallsBaredWithinCUG CC_HC_BearerCapabilityNotAuthorized CC_HC_BearerCapabilityNotPresentlyAvailable CC_HC_InconsistencyAcessInfoSubscriberClass CC_HC_ServiceOrOptionUnavailable CC_HC_BearerCapabilityNotImplemented CC_HC_ChannelTypeNotImplemented CC_HC_RequestedFacilityNotImplemented CC_HC_OnlyRestrictedDigitalBearerInfoCapability CC_HC_ServiceOrOptionNotImplemented CC_HC_InvalidCallreferenceValue CC_HC_IdentifiedChannelDoesnotExist CC_HC_ASuspendedCallExistsThisCallIdDoesNot CC_HC_CallIdentityInUse CC_HC_NoCallSuspended CC_HC_CallHavingTheRequestedCallIdHasBeenCleared = CC_EC_CallIdHasBeenCleared CC_HC_UserNotMemberOfCUG CC_HC_IncompatibleDestination CC_HC_NonExistantCUG CC_HC_InvalidTransitNetworkSelection CC_HC_InvalidMessage CC_HC_MandatoryInformationElementIsMissing CC_HC_MessageTypeNonExistantOrNotImplemented = CC_EC_MsgTypeNotImp CC_HC_MessageTypeNotCompatibleWithStateOrNonExistantOrNotImplemented =...
Page 171 Appendix C Example of an HSI Configuration File CC_HC_InformationElementParameterNonExistantOrNotImplemented = CC_EC_ElemTypeNotImp CC_HC_InvalidInformationElementContents = CC_EC_InvalidElemContents CC_HC_MessageNotCompatibleWithCallState = CC_EC_MsgInWrongState CC_HC_RecoveryOnTimerExpiry = CC_EC_RecoveryOnTimerExpiry CC_HC_ParameterNonExistantOrNotImplementedPassedOn = CC_EC_ParamUnrecPassed # ---------------------------------------------------------------------------------------------------------------- ################################################################################### # FAULTMANAGEMENT PACKAGE Package = FaultManagement FMRaiseRecoveryAction = "ON" FMClearRecoveryAction = "ON" ################################################################################### # GAPPING PACKAGE # Set the gapping percentage level for each side.
Page 172 Appendix C Example of an HSI Configuration File # GapOn100PercentGapping indicates priority calls are only gapped when 100 percent # gapping is applied. #PriorityCallTreatment = GapOn100PercentGapping #PriorityCallTreatment = GapNever PriorityCallTreatment = GapAlways ################################################################################### # TRACE PACKAGE # There are five trace trigger locations. Each location can hold one type of # six trigger types as follows: # EISUP CallingPartyNumber (E.164 address) # EISUP CalledPartyNumber (E.164 address)
Page 173 Appendix C Example of an HSI Configuration File Trigger2.eisup.CalledPartyNumber=1900 #Trigger2.h323.CallingPartyNumber=0299 #Trigger2.h323.CalledPartyNumber=0388 #Trigger2.h323.OriginatingIPAddress=203.188.2.3 #Trigger2.h323.OriginatingIPMask=255.255.0.0 #Trigger2.h323.TerminatingIPAddress=203.15y5.7.9 #Trigger2.h323.TerminatingIPMask=255.255.0.0 #Trigger3.eisup.CallingPartyNumber=1800 #Trigger3.eisup.CalledPartyNumber=1900 #Trigger3.h323.CallingPartyNumber=0299 #Trigger3.h323.CalledPartyNumber=0388 Trigger3.h323.OriginatingIPAddress=203.188.2.3 Trigger3.h323.OriginatingIPMask=255.255.0.0 #Trigger3.h323.TerminatingIPAddress=203.155.7.9 #Trigger3.h323.TerminatingIPMask=255.255.0.0 #Trigger4.eisup.CallingPartyNumber=1800 #Trigger4.eisup.CalledPartyNumber=1900 #Trigger4.h323.CallingPartyNumber=0299 Trigger4.h323.CalledPartyNumber=0388 #Trigger4.h323.OriginatingIPAddress=203.188.2.3 #Trigger4.h323.OriginatingIPMask=255.255.0.0 #Trigger4.h323.TerminatingIPAddress=203.155.7.9 #Trigger4.h323.TerminatingIPMask=255.255.0.0 #Trigger5.eisup.CallingPartyNumber=1800 #Trigger5.eisup.CalledPartyNumber=1900 #Trigger5.h323.CallingPartyNumber=0299 #Trigger5.h323.CalledPartyNumber=0388 #Trigger5.h323.OriginatingIPAddress=203.188.2.3 #Trigger5.h323.OriginatingIPMask=255.255.0.0 Trigger5.h323.TerminatingIPAddress=203.155.7.9 Trigger5.h323.TerminatingIPMask=255.255.0.0 # TraceTriggerSwitch(for CLI/SNMP application) # This gates the output of the trigger data for each location Cisco H.323 Signaling Interface User Guide C-13...
Page 174 Appendix C Example of an HSI Configuration File TriggerGate1=ON TriggerGate2=ON TriggerGate3=ON TriggerGate4=ON TriggerGate5=ON ################################################################################### # EISUP PACKAGE Package = EISUP #The period for CISCO's RUDP timer manage, in milli seconds #RUDP_TIMER_CHECK_PERIOD_MSEC=20 #The time to wait before failing over to another VSC. WAIT_TIME_BEFORE_FAIL_OVER_MILLI_SEC=1000 ################################################################################### # APPLICATION PACKAGE...
Page 175 Appendix C Example of an HSI Configuration File ################################################################################### # DYNAMIC SYSTEM DATA Package = SYS_CONFIG_DYNAMIC # Alternate Gatekeeper ALTERNATEGATEKEEPERIP gatekeeper, otherwise insert IP address e.g. 10.70.54.55 ALTERNATEGATEKEEPERPORT = 1719 ALTERNATEGATEKEEPERID # Logging LOGDIRECTORY LOGFILENAMEPREFIX LOGPRIO CRIT}. Default: "WARN" LOGFILEROTATESIZE LOGFILEROTATEINTERVAL = 1440 # Overload DISKUSAGELIMIT...
Page 176 OVLDLEVEL2FILTER "NORMAL" OVLDLEVEL2THRESHUPPERCPU OVLDLEVEL2THRESHLOWERCPU OVLDLEVEL2THRESHUPPERCALLS OVLDLEVEL2THRESHLOWERCALLS OVLDLEVEL3PERCENT OVLDLEVEL3FILTER Default: "NORMAL" OVLDLEVEL3THRESHUPPERCPU OVLDLEVEL3THRESHLOWERCPU OVLDLEVEL3THRESHUPPERCALLS OVLDLEVEL3THRESHLOWERCALLS ################################################################################### Package = SYS_CONFIG_STATIC # Call Control # For the H323 cause code values see ITU-T: Q.850 # The default cause codes, used when there is no map entry for a received cause CC_EC_DEFAULT CC_HC_DEFAULT # Unassigned Eisup cause codes...
Page 177 Appendix C Example of an HSI Configuration File CC_EC_BlacklistBNumberMatched CC_EC_BlacklistCliLengthInvalid CC_EC_BlacklistCliMatched CC_EC_BlacklistCpcRestricted CC_EC_BlacklistNoCli CC_EC_BlacklistNoaRestricted CC_EC_Busy CC_EC_CallRejectCallGapping CC_EC_CallTerminated CC_EC_CallTypeIncompatible CC_EC_CallingDroppedWhileOnHold CC_EC_CallingPartyOffHold CC_EC_ChannelOutOfService CC_EC_Congestion CC_EC_CotFailure CC_EC_CugAccessBarred CC_EC_DteControlledNotReady CC_EC_DteUncontrolledNotReady CC_EC_ExcessiveDigCallProceeding CC_EC_FacilityNotRegistered CC_EC_FlowControlledCongestion CC_EC_GroupRestrictions CC_EC_IncomingCallsBarred CC_EC_InterceptedSubscriber CC_EC_InterworkUnspec CC_EC_InvalidCallRef CC_EC_MesgWithUnrecElemDiscarded CC_EC_MessageNotUnderstood CC_EC_MisroutedCallPortedNumber CC_EC_NetworkAddressExtensionError CC_EC_NetworkTermination CC_EC_NewDestination CC_EC_NumberUnobtainable CC_EC_OperatorPriorityAccess CC_EC_OutOfCatchmentArea...
Page 178 CC_EC_PreemptionCctUnavailable CC_EC_Prefix0DialledInError CC_EC_Prefix1DialledInError CC_EC_Prefix1NotDialled CC_EC_PriorityForcedRelease CC_EC_Proprietary CC_EC_ProtErrThresholdExceeded CC_EC_ProtocolErrorUnspec CC_EC_Reject CC_EC_RejectedDivertedCall CC_EC_RemoteProcError CC_EC_RepeatAttempt CC_EC_RouteOutOfService CC_EC_SelectiveCallBarring CC_EC_ServiceIncompatible CC_EC_ServiceTemporarilyUnavailable CC_EC_ServiceUnavailable CC_EC_SignalNotUnderstood CC_EC_SignalNotValid CC_EC_SignallingSystemIncompatible CC_EC_SubControlledIcb CC_EC_SubNotFoundDle CC_EC_SubscriberCallTerminate CC_EC_SubscriberIncompatible CC_EC_SubscriberMoved CC_EC_SubscriberOutOfService CC_EC_TemporaryOos CC_EC_TerminalCongestion CC_EC_Transferred CC_EC_TranslationOos CC_EC_UnallocatedDestNumber CC_EC_UndefinedBg CC_EC_Unknown CC_EC_UnrecElemPassedOn CC_EC_VacentCode CC_EC_WhitelistCliNotMatched Cisco H.323 Signaling Interface User Guide C-18 Appendix C Example of an HSI Configuration File...
Page 179 Appendix C Example of an HSI Configuration File # T38 Fax default configuration T38MaxVal = "MaxBit 0x90, FxMaxBuf 0xc8, FxMaxData 0x48" T38Options = "FxFillBit 0, FxTransMMR 0, FxTransJBIG 0, FxRate Trans, FxUdpEC Red" # EISUP Settings for GoldWing to look at EISUP Test Tool # Point GWmain to look at the test tool HOST_PORT instead of the VSC's #VSCA_IPADDR1=samson #VSCA_PORT_NUMBER1=18613...
Page 180 Appendix C Example of an HSI Configuration File Cisco H.323 Signaling Interface User Guide C-20 OL-4806-01 Rev. A14...
Page 181: E-Isup Name-To-Cause Value Lookup
E-ISUP Name-to-Cause Value Lookup This appendix lists the Cisco E-ISUP protocol names and their associated cause values. Name ----- CC_EC_AccessBarred CC_EC_AccessInfoDiscarded CC_EC_Acknowledgement CC_EC_AddressIncomplete CC_EC_AnonymousCallRejection CC_EC_BaercapNotAvail CC_EC_BearcapNotAuthorized CC_EC_BearcapNotImp CC_EC_BlacklistBNumberMatched CC_EC_BlacklistCliLengthInvalid CC_EC_BlacklistCliMatched CC_EC_BlacklistCpcRestricted CC_EC_BlacklistNoCli CC_EC_BlacklistNoaRestricted CC_EC_Busy CC_EC_CallAwardedDeliveredEstCh CC_EC_CallIdHasBeenCleared CC_EC_CallIdInUse CC_EC_CallRejectCallGapping CC_EC_CallRejected CC_EC_CallTerminated CC_EC_CallTypeIncompatible CC_EC_CallingDroppedWhileOnHold CC_EC_CallingPartyOffHold...
Page 182 CC_EC_IncomingCallsBarred CC_EC_IncomingCallsBarredInCug CC_EC_IncompatibleDest CC_EC_InconOutgoingAccAndSubClass CC_EC_InterceptedSubscriber CC_EC_InterworkUnspec CC_EC_InvalidCallRef CC_EC_InvalidCallReferenceValue CC_EC_InvalidElemContents CC_EC_InvalidMsgUnspec CC_EC_InvalidNumberFormat CC_EC_InvalidTns CC_EC_MandatoryElementMissing CC_EC_MesgWithUnrecElemDiscarded CC_EC_MessageNotUnderstood CC_EC_MisdialledTkPrefix CC_EC_MisroutedCallPortedNumber CC_EC_MsgInWrongState CC_EC_MsgTypeNotImp CC_EC_MsgTypeNotImpOrWrongState CC_EC_NetworkAddressExtensionError CC_EC_NetworkOutOfOrder CC_EC_NetworkTermination CC_EC_NewDestination CC_EC_NoAnswerAlertedUser CC_EC_NoCallSuspended CC_EC_NoCircuitAvailable CC_EC_NoRouteToDest CC_EC_NoRouteToTns CC_EC_NoUserResponding CC_EC_NonExistentCug CC_EC_NonSelectedUserClearing CC_EC_NormalClearing CC_EC_NormalUnspecified CC_EC_NumberChanged CC_EC_NumberUnobtainable CC_EC_OnlyRestrictDigInfoBearer CC_EC_OperatorPriorityAccess CC_EC_OutOfCatchmentArea CC_EC_OutgoingCallsBarred CC_EC_OutgoingCallsBarredInCug CC_EC_ParamUnrecPassed CC_EC_PermanentFrameModeOos...
Page 183 Appendix D E-ISUP Name-to-Cause Value Lookup CC_EC_ReqCircuitUnavail CC_EC_ReqFacilityNotImp CC_EC_ReqFacilityNotSubscr CC_EC_ResourcesUnavailUnspec CC_EC_ResponseToStatusEnquiry CC_EC_RouteOutOfService CC_EC_RoutingError CC_EC_SelectiveCallBarring CC_EC_ServiceIncompatible CC_EC_ServiceOrOptionNotAvail CC_EC_ServiceOrOptionNotImpUnspec CC_EC_ServiceTemporarilyUnavailable CC_EC_ServiceUnavailable CC_EC_SignalNotUnderstood CC_EC_SignalNotValid CC_EC_SignallingSystemIncompatible CC_EC_SpecialInformationTone CC_EC_SubAbscent CC_EC_SubControlledIcb CC_EC_SubNotFoundDle CC_EC_SubscriberCallTerminate CC_EC_SubscriberIncompatible CC_EC_SubscriberMoved CC_EC_SubscriberOutOfService CC_EC_SuspendExistButNotThisId CC_EC_SwitchingEquipCongestion CC_EC_TemporaryFailure CC_EC_TemporaryOos CC_EC_TerminalCongestion CC_EC_Transferred CC_EC_TranslationOos CC_EC_UnallocatedDestNumber CC_EC_UnallocatedNumber CC_EC_UndefinedBg CC_EC_Unknown CC_EC_UnrecElemPassedOn CC_EC_UserBusy...
Page 184 Appendix D E-ISUP Name-to-Cause Value Lookup Cisco H.323 Signaling Interface User Guide OL-4806-01 Rev. A14...
Page 185: E-Isup Cause Value-To-Name Lookup
E-ISUP Cause Value-to-Name Lookup This appendix lists the Cisco E-ISUP cause values and their associated names. Value Name ----- ---- CC_EC_AccessInfoDiscarded CC_EC_BearcapNotAuthorized CC_EC_BearcapNotAvail CC_EC_BearcapNotImp CC_EC_CallAwardedDeliveredEstCh CC_EC_CallIdHasBeenCleared CC_EC_CallIdInUse CC_EC_CallRejected CC_EC_ChIdNotExist CC_EC_ChTypeNotImp CC_EC_ChUnacceptable CC_EC_DestOutOfOrder CC_EC_ElemTypeNotImp CC_EC_FacilityRejected CC_EC_IncompatibleDest CC_EC_InterworkUnspec CC_EC_InvalidCallReferenceValue CC_EC_InvalidElemContents CC_EC_InvalidMsgUnspec CC_EC_InvalidNumberFormat CC_EC_InvalidTns CC_EC_MandatoryElementMissing CC_EC_MsgInWrongState...
Page 186 CC_EC_ReqFacilityNotImp CC_EC_ReqFacilityNotSubscr CC_EC_ResourcesUnavailUnspec CC_EC_ResponseToStatusEnquiry CC_EC_ServiceOrOptionNotImpUnspec CC_EC_ServiceOrOptionNotAvail CC_EC_SuspendExistButNotThisId CC_EC_SwitchingEquipCongestion CC_EC_TemporaryFailure CC_EC_UnallocatedNumber CC_EC_UserBusy CC_EC_InterceptedSubscriber CC_EC_AccessBarred CC_EC_Acknowledgement CC_EC_AddressIncomplete CC_EC_Busy CC_EC_ChannelOutOfService CC_EC_DteControlledNotReady CC_EC_Congestion CC_EC_CallTerminated CC_EC_FacilityNotRegistered CC_EC_IncomingCallsBarred CC_EC_ServiceIncompatible CC_EC_MessageNotUnderstood CC_EC_NetworkAddressExtensionError CC_EC_NetworkTermination CC_EC_NumberUnobtainable CC_EC_PriorityForcedRelease CC_EC_Reject CC_EC_RouteOutOfService CC_EC_SubscriberIncompatible CC_EC_SignalNotUnderstood CC_EC_SignalNotValid CC_EC_SubscriberOutOfService CC_EC_SignallingSystemIncompatible CC_EC_ServiceTemporarilyUnavailable CC_EC_ServiceUnavailable CC_EC_DteUncontrolledNotReady CC_EC_Transferred CC_EC_IncomingCallsBarredInCug CC_EC_SpecialInformationTone CC_EC_UserNotMemberOfCug CC_EC_MisdialledTkPrefix...
Page 187 Appendix E E-ISUP Cause Value-to-Name Lookup CC_EC_TemporaryOos CC_EC_OperatorPriorityAccess CC_EC_CugAccessBarred CC_EC_SubscriberCallTerminate CC_EC_FlowControlledCongestion CC_EC_OutOfCatchmentArea CC_EC_TranslationOos CC_EC_PermanentIcb CC_EC_SubscriberMoved CC_EC_SubNotFoundDle CC_EC_AnonymousCallRejection CC_EC_TerminalCongestion CC_EC_RepeatAttempt CC_EC_VacentCode CC_EC_Prefix0DialledInError CC_EC_Prefix1DialledInError CC_EC_Prefix1NotDialled CC_EC_ExcessiveDigCallProceeding CC_EC_ProtErrThresholdExceeded CC_EC_OutgoingCallsBarredInCug CC_EC_InconOutgoingAccAndSubClass CC_EC_NonExistentCug CC_EC_MesgWithUnrecElemDiscarded CC_EC_PreemptionCctRes CC_EC_PermanentFrameModeOos CC_EC_PermanentFrameModeOperational CC_EC_BlacklistNoCli CC_EC_BlacklistCliLengthInvalid CC_EC_BlacklistCliMatched CC_EC_BlacklistCpcRestricted CC_EC_BlacklistNoaRestricted CC_EC_BlacklistBNumberMatched CC_EC_WhitelistCliNotMatched CC_EC_PortedNumber CC_EC_RedirectionToNewDest CC_EC_CotFailure CC_EC_MisroutedCallPortedNumber...
Page 188 Appendix E E-ISUP Cause Value-to-Name Lookup Cisco H.323 Signaling Interface User Guide OL-4806-01 Rev. A14...
Page 189: H.323 Name-To-Cause Value Lookup
H.323 Name-to-Cause Value Lookup This appendix lists the H.323 names and their associated cause values. Name ---- CC_HC_ASuspendedCallExistsThisCallIdDoesNot CC_HC_AccessInformationDiscarded CC_HC_BearerCapabilityNotAuthorized CC_HC_BearerCapabilityNotImplemented CC_HC_BearerCapabilityNotPresentlyAvailable CC_HC_CallAwardedEstablishedChannel CC_HC_CallHavingTheRequestedCallIdHasBeenCleared CC_HC_CallIdentityInUse CC_HC_CallRejected CC_HC_ChannelTypeNotImplemented CC_HC_ChannelUnacceptable CC_HC_DEFAULT CC_HC_DestinationOutOfOrder CC_HC_ExchangeRouteError CC_HC_FacilityRejected CC_HC_IdentifiedChannelDoesnotExist CC_HC_IncomingCallsBaredWithinCUG CC_HC_IncompatibleDestination CC_HC_InconsistencyAcessInfoSubscriberClass CC_HC_InformationElementParameterNonExistantOrNotImplemented CC_HC_InvalidCallreferenceValue CC_HC_InvalidInformationElementContents CC_HC_InvalidMessage CC_HC_InvalidNumberFormat CC_HC_InvalidTransitNetworkSelection CC_HC_MandatoryInformationElementIsMissing...
Page 190 CC_HC_NumberChanged CC_HC_OnlyRestrictedDigitalBearerInfoCapability CC_HC_OutgoingCallsBaredWithinCUG CC_HC_ParameterNonExistantOrNotImplementedPassedOn CC_HC_PermanentFrameModeConnectionOperational CC_HC_PermanentFrameModeConnectionOutOfService CC_HC_PrecedenceCallBlocked CC_HC_Preemption CC_HC_PreemptionCircuitReservedForReuse CC_HC_QualityOfServiceNotAvailable CC_HC_RecoveryOnTimerExpiry CC_HC_RedirectionToNewDestination CC_HC_RequestedCircuitChannelNotAvailable CC_HC_RequestedFacilityNotImplemented CC_HC_RequestedFacilityNotSubscribed CC_HC_ResourceUnavailable CC_HC_ResponceToStatusEnquiry CC_HC_SendSpecialInformationTone CC_HC_ServiceOrOptionNotImplemented CC_HC_ServiceOrOptionUnavailable CC_HC_SubscriberAbsent CC_HC_SwitchingEquipmentCongestion CC_HC_TemporaryFailure CC_HC_UnallocatedNumber CC_HC_UserBusy CC_HC_UserNotMemberOfCUG Cisco H.323 Signaling Interface User Guide Appendix F H.323 Name-to-Cause Value Lookup OL-4806-01 Rev. A14...
Page 191 H.323 Cause Value-to-Name Lookup This appendix lists the H.323 cause values and their associated names. Value Name ----- ---- CC_HC_UnallocatedNumber CC_HC_NoRouteToSpecifiedTransitNetwork CC_HC_NoRouteToDestination CC_HC_SendSpecialInformationTone CC_HC_MisdialedTrunkPrefix CC_HC_ChannelUnacceptable CC_HC_CallAwardedEstablishedChannel CC_HC_Preemption CC_HC_PreemptionCircuitReservedForReuse CC_HC_NormalCallClearing CC_HC_UserBusy CC_HC_NoUserresponding CC_HC_NoAnswerFromAlertedUser CC_HC_SubscriberAbsent CC_HC_CallRejected CC_HC_NumberChanged CC_HC_RedirectionToNewDestination CC_HC_ExchangeRouteError CC_HC_NonSelectedUserClearing CC_HC_DestinationOutOfOrder CC_HC_InvalidNumberFormat CC_HC_FacilityRejected CC_HC_ResponceToStatusEnquiry CC_HC_DEFAULT...
Page 192: G H.323 Cause Value-To-Name Lookup
CC_HC_ServiceOrOptionUnavailable CC_HC_BearerCapabilityNotImplemented CC_HC_ChannelTypeNotImplemented CC_HC_RequestedFacilityNotImplemented CC_HC_OnlyRestrictedDigitalBearerInfoCapability CC_HC_ServiceOrOptionNotImplemented CC_HC_InvalidCallreferenceValue CC_HC_IdentifiedChannelDoesnotExist CC_HC_ASuspendedCallExistsThisCallIdDoesNot CC_HC_CallIdentityInUse CC_HC_NoCallSuspended CC_HC_CallHavingTheRequestedCallIdHasBeenCleared CC_HC_UserNotMemberOfCUG CC_HC_IncompatibleDestination CC_HC_NonExistantCUG CC_HC_InvalidTransitNetworkSelection CC_HC_InvalidMessage CC_HC_MandatoryInformationElementIsMissing CC_HC_MessageTypeNonExistantOrNotImplemented CC_HC_MessageTypeNotCompatibleWithStateOrNonExistantOrNotImplemented CC_HC_InformationElementParameterNonExistantOrNotImplemented CC_HC_InvalidInformationElementContents CC_HC_MessageNotCompatibleWithCallState CC_HC_RecoveryOnTimerExpiry CC_HC_ParameterNonExistantOrNotImplementedPassedOn Cisco H.323 Signaling Interface User Guide Appendix G H.323 Cause Value-to-Name Lookup OL-4806-01 Rev. A14...
Page 193 ack-alm command acknowledging alarms active log file ALARMDEBOUNCETIME parameter alarm messages continous mode noncontinuous mode alarms acknowledging cleared state clearing CONFIG_CHANGE 5-11 CONFIGURATION_FAILURE debounce period EISUP_PATH_FAILURE ENDPOINT_CALL_CONTROL_INTERFACE_FAILU 5-12 ENDPOINT_CHANNEL_INTERFACE_FAILURE GAPPED_CALL_NORMAL 5-13 GAPPED_CALL_PRIORITY 5-13 GATEKEEPER_INTERFACE_FAILURE GENERAL_PROCESS_FAILURE H323_STACK_FAILURE IP_LINK_FAILURE list LOW_DISK_SPACE OVERLOAD_LEVEL1 5-14 OVERLOAD_LEVEL2 5-11...
Page 194 Index CIAGENTSCANPERIOD parameter Cisco HSI See HSI clearing alarms clr-alm command 5-4, A-8 clr-meas command 4-6, A-9 codec parameters 3-15 commands ack-alm clr-alm 5-4, A-8 clr-meas 4-6, A-9 diaglog A-4, A-10 A-10 help A-6, A-11 MML configuration prov-add 3-3, 3-6, 3-9, A-12 prov-cpy A-13 prov-dlt...
Page 195 dynamic provisionable static debounce default active log file detailed logging 5-16 diaglog command A-4, A-10 documentation related document conventions xiii dynamic configuration data system data parameters E-ISUP overview protocol EISUP_PATH_FAILURE alarm empty capability set 3-17 ENDPOINT_CALL_CONTROL_INTERFACE_FAILUR E alarm 5-12 ENDPOINT_CHANNEL_INTERFACE_FAILURE alarm 5-12 Enhanced ISDN User Part...
Page 196 Index HSI INFORMATION Message Support HSI Support for Tech Prefixes 3-19 installing previous version 2-12 procedures required information subdirectories MML sessions, configuring overview performance and sizing preinstallation tasks recovery removing 2-12 restarting security services software requirements 1-5, 2-1 starting 2-11 status stopping 2-11...
Page 197 syntax MML configuration commands component export session MML response messages error status MML sessions configuring help quitting starting noncontinuous mode alarm messages nonprovisionable data parameters OAM subsystem overlappedSending parameter 3-11 overload data retrieving setting description level 1 level 2 level 3 OVERLOAD_LEVEL1 alarm 5-14 OVERLOAD_LEVEL2 alarm...
Page 198 Index OVLDLEVEL3PERCENT OVLDLEVEL3THRESHLOWERCPU OVLDLEVEL3THRESHUPPERCALLS OVLDLEVEL3THRESHUPPERCPU Q.931 3-10 3-11 PGW 2200 description PKINST file 2-9, 2-12 protocols E-ISUP H.225 Q.931 RUDP prov-add command 3-3, 3-6, 3-9, A-12 prov-cpy command A-13 prov-dlt command 3-3, 3-6, 3-9, A-14 prov-ed command 3-3, 3-6, 3-9, A-15 prov-exp command A-16 PROVISIONING_INACTIVITY_TIMEOUT alarm...
Page 199 signaling interface See HSI Simple Network Management Protocol See SNMP skeleton configuration file SNMP manager subagent 2-11, 4-2 trap types software requirements Solaris 8 operating system installation platform requirements sta-callproc command 4-2, A-34 starting batch files call processing call processing application Cisco HSI 2-11 MML sessions...

This manual is also suitable for:

Hsi 4.1

Cisco Signaling Interface H.323 User Manual

Preface

CHAPTER 1 Cisco H.323 Signaling Interface Overview

CHAPTER 2 Installing and Configuring Cisco HSI Software

Chapter 3 Provisioning the Cisco HSI

CHAPTER 4 Managing the Cisco HSI

Troubleshooting

Appendix

MML User Interface and Command Reference

Help

Quit

Appendix

Skeleton Configuration File

Appendix B Skeleton Configuration File

Appendix

Example of an HSI Configuration File

E-ISUP Name-To-Cause Value Lookup

Appendix

E-ISUP Cause Value-To-Name Lookup

H.323 Name-To-Cause Value Lookup

G H.323 Cause Value-To-Name Lookup

Quick Links

Troubleshooting

Related Manuals for Cisco Signaling Interface H.323

Summary of Contents for Cisco Signaling Interface H.323

This manual is also suitable for:

Table of Contents