C H A P T E R 3 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 • H.323 Stack Configuration, page 3-10 • HSI Feature Configuration, page 3-22 Cisco HSI Configuration All configuration data is contained within configuration files.
Chapter 3 Provisioning the Cisco HSI 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.
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration 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 (System Configuration Data).
Chapter 3 Provisioning the Cisco HSI 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 Step 3 To exit the MML command interpreter, issue the following command: quit Reverting to the Base Configuration The following MML command examples show how to revert to the base HSI configuration: Step 1 To begin an MML session, issue t
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration Table 3-3 Static System Data Parameters Parameter Type Description HOST_PORT_NUMBER1 [0-65535] The first port number to be used by the Cisco HSI. The default value is 0. Note HOST_PORT_NUMBER2 [0-65535] This value must match the peer port setting on the PGW1 2200 E-ISUP IPLNK object. The second port number to be used by the Cisco HSI. The default value is 0. Note This value should always be set to 0.
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration Table 3-3 Static System Data Parameters (continued) Parameter Type Description PavoRedirPresInd [0-3] The value of the Pavo redirecting number presentation indicator. (If this parameter is not provisioned, the default is Q.931 zero—no indication.) CliInDisplaySupported STRING T38MaxVal STRING If this parameter is present and set to anything other than “”, the Calling Number is also sent in the DISPLAY IE.
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration Table 3-3 Static System Data Parameters (continued) Parameter Type Description DualCLISupported STRING To enable Dual CLI support (see H.246 Annex C), set this parameter to anything other than “”. For example, to explicitly enable Dual CLI support, set this parameter to “Enabled.” InjectPi8 STRING If this parameter is set to a text value (for example, “enabled” or “true”), the HSI inserts a progress indicator value of 8 into the H.
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration Dynamic System Data To modify the dynamic system data parameters in Table 3-4, use the sys_config_dynamic MML name 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.
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration Table 3-4 Dynamic System Data Parameters (continued) Parameter Description OVLDLEVEL1PERCENT 20 Indicates what percentage of calls should be rejected when an overload condition occurs. This parameter is used in conjunction with the OVLDLEVEL1FILTER parameter. The overload level 1 value is the lowest level of overload and must be less than or equal to the provisioned values for OVLDLEVEL2PERCENT and OVLDLEVEL3PERCENT.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-4 Dynamic System Data Parameters (continued) Parameter Description OVLDLEVEL3PERCENT Indicates what percentage of calls should be rejected when an 90 overload condition occurs. The parameter is used in conjunction with the OVLDLEVEL3FILTER parameter. This is the highest level of overload and must be greater than or equal to the provisioned values for OVLDLEVEL1PERCENT and OVLDLEVEL2PERCENT.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Nonprovisionable Data The parameters in Table 3-5 cannot be altered through MML commands. Table 3-5 Nonprovisionable Data Parameters H323_SYS Description system.manualstart Present system.pdlname Absent system.delimiter #FF ras.gatekeeper Absent ras.rasmulticastaddress 224.0.1.41.1718 h245.capabilities.manualoperation Present h245.masterslave.manualoperation Present q931.manualaccept Present q931.earlyH245 Present q931.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Example prov-add:name=q931,maxCalls=2000 The Update Type column in Table 3-7 shows when the change to a parameter takes effect once a change is made: Table 3-7 • 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.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration RAS Parameters The parameters in Table 3-8 are required for RAS stack initialization. To modify the RAS parameters, 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.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-8 RAS Parameters (continued) Parameter Name Description Type Example Update Type allowCallsWhenNonReg If this parameter is present, it NULL allows calls to proceed even if gatekeeper registration has not been done for the PGW 2200. Not present Immediate manualRegistration If this parameter is present, the stack does not perform automatic gatekeeper registration procedures (it waits to be driven by the application).
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-8 RAS Parameters (continued) Parameter Name Description manualDiscovery.port Example Update Type The port associated with the INTEGER(0, 65535) manualDiscovery.ipAddress, which can, by agreement, be either a well-known port or another port. 1719 Start gateway.prefix[i] STRING The gateway registers the telephone prefix specified by this parameter to indicate that it is able to terminate it.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-9 H.245 Parameters Parameter Name Description Type Example Update Type masterSlave.terminalType The terminal type for the PGW 2200. INTEGER(0, 255) 60 Next Call masterSlave.manualResponse NULL If this parameter is present, it cancels automatic acknowledgment of master or slave determination. Present Next Call masterSlave.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-10 H.245 Terminal Capability Codec Parameters (continued) Parameter Name Type caps.table[i].audio.g722at56k INTEGER(1, 256) caps.table[i].audio.g722at48k INTEGER(1, 256) caps.table[i].audio.g7231.maxAudioFrames INTEGER(1,256) caps.table[i].audio.g7231.silenceSuppression INTEGER(0,1) caps.table[i].audio.g728 INTEGER(1, 256) caps.table[i].audio.g729 INTEGER(1, 256) Table 3-11 H.
Chapter 3 Provisioning the Cisco HSI 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. Similarly, the Cisco HSI also must be configured with the same codecs.
Chapter 3 Provisioning the Cisco HSI H.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-14 Common Static System Data Parameters Parameter Name Parameter Values Description CarrierCodeMapping • ClipClirSupported • “enabled”—a string that indicates the Allows transit of CLI presentation/screening feature is enabled. information. • Blank (“”)—indicates the feature is disabled • “deleted”—indicates that the feature is disabled • “dtmf”—the recommended value for Selects the DTMF type during H.
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-14 Common Static System Data Parameters (continued) Parameter Name Parameter Values NotifyMsgEnabled For example: Description Allows transit of connected number, display information, and generic notification indicator in • “enabled”—a string that indicates the H.225 Notify messages. feature is enabled.
Chapter 3 Provisioning the Cisco HSI 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 Parameter Value chan[i].name For example: prov-add:name=”H245”,chan[4].name=”g729” chan[i].audio.g729 For example: prov-add:name=”H245”,chan[4].audio.g729=”2” caps.table[i].audio.g729 For example: prov-add:name=”H245”,caps.table[4].audio.g729=”2” caps.table[i].entryNo For example: prov-add:name=”H245”,caps.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration • 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.
Chapter 3 Provisioning the Cisco HSI 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. When a fax call is initiated, a voice call is established. When the terminating gateway detects the fax tone generated by the terminating fax machine, the gateway initiates a T.38 mode request using H.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration 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.
Chapter 3 Provisioning the Cisco HSI 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, caps.table[i].audio.entryNo H245, chan[i].audio.gclear prov-add:name=h245, caps.table[9].audio.gclear="ClearChid" prov-add:name=h245, caps.table[10].audio.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration 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. Currently, H.
Chapter 3 Provisioning the Cisco HSI 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.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration Table 3-18 Configuring G.726 (continued) G.726 Parameter Example Value Configuration Example H245, caps.table[i].entryNo 7261, 7262, … prov-add:name=h245, caps.table[5].entryNo=7261 Note H245, chan[i].audio.g726-cisco Set this parameter to prov-add:name=h245, a unique integer caps.table[6].entryNo=7262 value “G726r16” “G726r24” “G726r32” prov-add:name=h245, chan[5].audio.g726-cisco="G726r16" prov-add:name=h245, chan[6].audio.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration Table 3-18 Configuring G.726 (continued) G.726 Parameter Example Value Configuration Example H245, caps.table[i].audio.g726-generic.bitOrder 1,2 or 3 prov-add:name=h245, caps.table[7].audio.g726-generic.bitOrder=2 H245, caps.table[i].audio.g726-generic.maxSPP H245, caps.table[i].entryNo Note 30, 40 Note This field is an integer value from 0...65535. 7263, 7264 Note H245, chan[i].audio.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration Table 3-18 Configuring G.726 (continued) G.726 Parameter Example Value Configuration Example H245, modes[i].audio.g726-generic.bitOrder 1, 2 or 3 prov-add:name=h245, modes.table[7].audio.g726-generic.bitOrder=2 prov-add:name=h245, modes.table[8].audio.g726-generic.bitOrder=3 H245, modes[i].audio.g726-generic.maxSPP 30, 40 prov-add:name=h245, modes[7].audio.g726-generic.maxSPP=30 prov-add:name=h245, modes[8].audio.g726-generic.
Chapter 3 Provisioning the Cisco HSI HSI Feature Configuration Table 3-19 Configuring G.729 Annex A and G.729 Annex B (continued) G.729 Parameter Example Value Example Configuration H245,modes[i].name “g729AnnexA” prov-add:name=h245,modes[4].name="g729AnnexA" “g729AnnexB” prov-add:name=h245,modes[5].name="g729AnnexB" H245,modes[i].audio.g729AnnexA “g729AnnexA wAnnexB” prov-add:name=h245,modes[6].name="g729AnnexAwAnnexB" “” prov-add:name=h245, modes[4].audio.
