ページ1に含まれる内容の要旨
CHAPTER 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. Cisco HSI starts
ページ2に含まれる内容の要旨
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. All configuration data that can be set in the system is defined in the Skeleton Configuration file (see Appendix B, “Skeleton Con
ページ3に含まれる内容の要旨
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). Initiating an MML Session to Enable DTMF on the HSI The following MML command example shows how to start
ページ4に含まれる内容の要旨
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
ページ5に含まれる内容の要旨
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. 1 Note This value must match the peer port setting on the PGW 2200 E-ISUP IPLNK object. HOST_PORT_NUMBER2 [0-65535] 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. VSCA_IPADDR1 STRING The prim
ページ6に含まれる内容の要旨
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 If this parameter is present and set to anything other than “”, the Calling Number is also sent in the DISPLAY IE. The NetMeeting endpoint retrieves the ca
ページ7に含まれる内容の要旨
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 th
ページ8に含まれる内容の要旨
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. The prov-ed command modifies the value of
ページ9に含まれる内容の要旨
Chapter 3 Provisioning the Cisco HSI Cisco HSI Configuration Table 3-4 Dynamic System Data Parameters (continued) Parameter Description Default OVLDLEVEL1PERCENT Indicates what percentage of calls should be rejected when an 20 overload condition occurs. This parameter is used in conjunction with the OVLDLEVEL1FILTER parameter. The overload level 1 value is the lowest level of overload and must be less than or equal to the provisioned values for OVLDLEVEL2PERCENT and OVLDLEVEL3PERCENT. N
ページ10に含まれる内容の要旨
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-4 Dynamic System Data Parameters (continued) Parameter Description Default 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. Note If this value
ページ11に含まれる内容の要旨
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.autoansw
ページ12に含まれる内容の要旨
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: 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. Note Immediate and Next Call update types refer to dynamic system
ページ13に含まれる内容の要旨
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. Example prov-add:name=ras,maxfail=3 The array index [i] in some of the parameter names in the first column of Table 3-8 must be replaced wi
ページ14に含まれる内容の要旨
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 Not present Immediate allows calls to proceed even if gatekeeper registration has not been done for the PGW 2200. manualRegistration If this parameter is present, NULL Not present Stop/Start the stack does not perform automatic gatekeeper registration procedures (it waits to be
ページ15に含まれる内容の要旨
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-8 RAS Parameters (continued) Parameter Name Description Type Example Update Type manualDiscovery.port The port associated with the INTEGER(0, 65535) 1719 Start manualDiscovery.ipAddress, which can, by agreement, be either a well-known port or another port. gateway.prefix[i] The gateway registers the STRING 0208 Immediate telephone prefix specified by this parameter to indicate that it is able to terminate it. gate
ページ16に含まれる内容の要旨
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-9 H.245 Parameters Update Parameter Name Description Type Example Type masterSlave.terminalType The terminal type for the INTEGER(0, 255) 60 Next Call PGW 2200. masterSlave.manualResponse If this parameter is present, it NULL Present Next Call cancels automatic acknowledgment of master or slave determination. masterSlave.timeout The maximum time (in seconds) INTEGER(0, 65535) 5 Immediate the stack waits before it give
ページ17に含まれる内容の要旨
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.245 Channel Codec Parameters Parameter Name
ページ18に含まれる内容の要旨
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. The Cisco HSI receives a list of codecs from t
ページ19に含まれる内容の要旨
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-13 Common Call Control Parameters (continued) Parameter Name Parameter Value Description A_CC_Interworking 0—No interworking encountered (SS7 all Backward call indicator, Interworking indicator the way) 1—Interworking encountered A_CC_Location 1—User Cause indicator, Location 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—Packe
ページ20に含まれる内容の要旨
Chapter 3 Provisioning the Cisco HSI H.323 Stack Configuration Table 3-14 Common Static System Data Parameters Parameter Name Parameter Values Description CarrierCodeMapping “enabled”—a string that indicates the Allows the mapping of a special tech prefix (the feature is enabled. format of which is CCxCy) to the DestinationCircuitID “group” field in the ARQ Blank (“”)—indicates the feature is message. This feature works only with IOS disabled. Gatekeeper build Release 12.2(15)T10 o
