Table of ContentsCisco Pre-Paid Debitcard
Overview of the Multi-Language Feature
Multi-Language Feature Implementation
Testing and Debugging Your Multi-Language Script
Modifying the Existing Script
Call Flow Example
The baseline prepaid debitcard application supports the playing of pre-recorded static and dynamic prompts for English, Spanish, and Chinese (Mandarin). The building of the dynamic prompts for these languages is performed as part of the Cisco Internetwork Operating System (IOS). If an additional language is needed, it has to be delivered as a change to the Cisco IOS and follow the Cisco IOS release process. This can be a very time-consuming and costly process. The Multi-Language feature provides the user with the ability to accommodate languages, other than those originally implemented in the Cisco IOS, by making changes within the debitcard Tool Command Language (TCL) application. Because the modifications are at the script level, the user can implement any defined language. Script changes are relatively easy when the language's dynamic prompt rules are supplied and translated into the script.
Language exceptions are defined as languages outside the originally supported three languages. This document concentrates on the building of dynamic prompts for language exceptions, rather than static prompts, because the script handles static prompts the same way for all languages. When a language is selected, the script prepends a language prefix and passes that prompt to the interactive voice response (IVR) Application Programming Interface (API) playPrompt verb.
- The Multi-Language feature script debitcard_multi-lang_Cisco.184.108.40.206.tcl or later
- Complete set of professionally recorded language prompts for each configured language. Languages available with the Multi-Language feature debitcard script are English (en), Spanish (sp), Mandarin (ch), Thai (th), Cantonese (ca), Japanese (ja), and Russian (ru).
- Cisco IOS Release 12.1(3)xi or later.
- The Multi-Language feature is based on the debitcard application; therefore, it requires a RADIUS billing server for AAA.
- When setting up the language selection prompts associated with the configured languages, you must put all the actual files in the language 1 configured directory. Refer again to the above example. The files th_lang_sel2.au, ru_lang_sel3.au, ja_lang_sel4, ca_lang_sel5, sp_lang_sel6 and ch_lang_sel7 must all reside in directory tftp://dirt/au/en/. All other language prompts reside in the individual language directories.
- The maximum amount that the script handles for $amt and creditTime converted to hours and minutes is 999,999.99.
- TCL IVR API Version 1.0 Programmer's Guide
Version 1.0 commands for writing TCL scripts for the Cisco IVR feature on the Cisco AS5300 gateway.
- TCL IVR API Version 2.0 Programmer's Guide
Version 2.0 commands for writing TCL scripts for the Cisco IVR feature on the Cisco AS5300 gateway.
- RADIUS Vendor-Specific Attributes Voice Implementation Guide
Reference of Cisco RADIUS VSAs for use with VoIP call authorization.
Developers using this programmer's guide may be interested in joining the Cisco Developer Support Program. This new program has been developed to provide you with a consistent level of support that you can depend on while leveraging Cisco interfaces in your development projects.
A signed Developer Support Agreement is required to participate in this program. For more details, and access to this agreement, please visit us at http://www.cisco.com/warp/public/779/servpro/programs/ecosystem/devsup/ or contact firstname.lastname@example.org.
The Multi-Language feature is built on the application infrastructure of the debitcard script. The script is rewritten, but the call flow from debitcard is essentially unmodified. The original call flow is followed through all procedures for selecting a language, collecting a card number, performing authorization, and placing a call. The modifications necessary for the Multi-Language feature were made to procedures do_get_dest and do_second_authorization to accommodate the playing of pre-recorded dynamic creditAmount and creditTime for the new languages.
Step 1 Build the language's master prompt spreadsheet. This will be used to determine the language exceptions and how the language should build dynamic prompts.
Step 2 Determine what numbering structure the language belongs to. Is it SSDHTT, SDDHTT, or another form? Refer to the example in Table 1 to determine if modifications in procedure do_whole_part are required.
Step 3 Based on the numbering structure, modify the necessary procedures. If a language has a dynamic prompt exception for a digit, as defined in Table 1, then add the language prefix to the switch in the necessary procedure (do_tens, do_hundreds, do_thousands, or do_hthousands). See "Modifying the Existing Script". Under most circumstances, the switch default case should not have to be modified.
|Digit 1||Digit 2||Digit 3||Digit 4||Digit 5||Digit 6|
Included in this guide are seven new TCL procedures that can be used to build the language-specific dynamic prompts, while modifications were made in procedures do_get_dest and do_second_authorization. To implement a language exception, the procedures do_get_dest and do_second_authorization, as well as at least some of the other seven procedures, must be modified.
This modified procedure is used after successful first authorization. A TCL switch statement is included that directs the flow to the language exception procedures or uses the default for Cisco IOS implemented languages. For the TCL implemented language exceptions, this procedure separates the billing server returned amount (creditAmt) into two parts and calls the prompt building procedures of do_whole_part and do_decimal_part.
Note Some TCL script implementations must be based on the returned values from the RADIUS billing server for creditAmt and creditTime.
Example 1 Sample Modifications to Procedure do_get_dest
This is a modified procedure, used after successful authorization to play the dynamic prompt for creditTime. A TCL switch statement is included that directs the flow to the language exception procedures or uses the default for Cisco IOS implemented languages.
This new procedure separates the whole number string into its numeric prompt components for tens, hundreds, thousands, and hundred thousands. This is explained in more detail in Table 1. This procedure places these values in the numbers array and calls the appropriate procedure based on the arrays index containing a value, as shown in the following example.
Example 2 Example of Procedure do_whole_part
This new procedure is used to build the language dynamic prompt for the value stored in the numbers (tens) array index. In this procedure, the language exception code is written if the language handles the tens numbers different than the default method.
Example 3 Example of Procedure do_tens
This new procedure is used to build the language dynamic prompt for the value stored in the numbers (hundreds) array index. In this procedure, the language exception code is written if the language handles the hundreds numbers different than the default method, as shown in the following example.
Example 4 Example of Procedure do_hundreds
This new procedure is used to build the language dynamic prompt for the value stored in the numbers (thousands) array index. In this procedure, the language exception code is written if that language handles the thousands numbers different than the default method. The language form explained in Table 1 has an effect on how the language is implemented in this procedure. The procedure has to know if the numbers (thousands) array index contains a one- or two-digit number.
Example 5 Example of Procedure do_thousands
This new procedure is used to build the language dynamic prompt for the value stored in the numbers (hthousands) array index. In this procedure, the language exception code is written if that language handles the hundred thousand numbers different than the default method. The language form explained in Table 1 has an effect on how the language is implemented in this procedure. The procedure has to know if the numbers (hthousands) array index contains a one- or two-digit number.
Example 6 Example of Procedure do_hthousands
Example 7 Example of Procedure do_decimal_part
In procedures do_get_dest and do_second_authorization, a TCL switch statement was added to the branch if the selected language is a language exception (refer to Modifying the Existing Script). If not, the script executes the default case for playPrompt as previously implemented in the debitcard script. If the selected language is a language exception the switch statement in procedure do_get_dest starts the prompt building process.
Example 1 on page 5 shows the switch statement and language exception (ru). The default statement for the switch is the standard execution of playPrompt from previous debitcard applications. The switch statement is used in the else part of nested if for amount. It is implemented if the creditAmt returned from the billing server is greater than 0 and less than or equal to the maximum amount allowed (999,999.99).
- In Example 1, the exception code shown in the first statement splits the value for creditAmt ($amt) returned from the billing server into two parts, a whole part and a decimal part. After the split function, we are left with a two-element list. The string contained in list element 0 represents the whole part of the $amt variable, and the string contained in list element 1 represents the decimal portion.
- Next, as shown in Example 2 on page 6, we start the dynamic prompt building process with a procedure call to do_whole_part. The do_whole_part procedure makes a determination on the size and characteristic of the number being passed. The string representing the whole part of the creditAmt can be said to have a four-part characteristic. based on its length and characters representing a tens, a hundreds, a thousands, and a hundred thousands place.
Depending on the language form, a dynamic prompt for a language can be shown as a 6-digit whole number of the form SDDHTT, where S represents the hundred thousands position, DD represents the thousands position, H represents the hundreds position and TT represent the tens position. Another form of dynamic prompt for a language also can be shown as a 6-digit whole number of the form SSDHTT, where S represents the ten thousands position, D represents the thousands position, H represents the hundreds position, and TT represents the tens position.
- Example 4 on page 8 shows where the switch builds the numbers array differently based on a string length of 5 or 6 (refer to Table 1 regarding the difference of language exception number translation). In this example, the default case builds the numbers array around the SDDHTT form, while the exceptions are built for Cantonese (ca) and Japanese (ja), where the numbers array uses the form SSDHTT.
- When the whole part number form is established, a value is entered for the numbers array indexes. If a value is stored in the numbers index for tens, hundreds, thousands, or hthousands, the procedure is called to build the dynamic prompt. Example 3 on page 7 shows one way to handle the TT numbers using the procedure do_tens. In this example, the exception is for Thai (th). In the procedure the default case appends to the prompt list the language prefix and the value stored in numbers (tens) with some exceptions for string length. For Thai (th) there are exceptions for several different string combinations. The procedures do_hundreds, do_thousands, and do_hthousands are similar in design.
After the procedures do_tens, do_hundreds, do_thousands, and do_hthousands append the number files to build the dynamic prompt the call flow returns to the do_get_dest switch, where the script appends the language's currency denomination.
- The flow then proceeds to build the dynamic prompt for the decimal part. The do_decimal_part procedure shown in Example 7 on page 11, follows most of the same rules as do_tens procedure for most languages; but in some cases, there are different word gender rules. There are also some differences in handling the split decimal part strings. The string returned from the billing server for decimal part for numbers of ".10", ".20", ".30", and so on, is returned as .1, .2 and .3, and so on. Some special handling is needed when you append the necessary prompt. You can see this in the switch where string lengths are 1.
Example 8 Example of Procedure do_second_authorization Modifications
After the procedure do_decimal_part appends the number files to build the decimal number portion of the dynamic prompt, the call flow returns and the script appends the language's currency denomination for the decimal currency.
The billing server value for creditTime is handled in the procedure do_second_authorization, see Example 8 on page 13. The language modification is simply a call to the procedure do_creditTime_prompt. This was made a separate procedure to minimize lines of code. The procedure do_second_authorization had two places where almost identical operations were performed, so a separate procedure was created to handle the operations.
This new procedure is used after successful second authorization. It converts the billing server returned creditTime value of seconds to a two-element list whose whole part is hours and whose decimal part is minutes. The procedure follows the same process described previously for building the language dynamic prompts.
Example 9 Example of Procedure do_creditTime_prompt
Example 10 Example of Procedure do_creditTime_prompt (continued)
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
- WWW: http://www.cisco.com
- WWW: http://www-europe.cisco.com
- WWW: http://www-china.cisco.com
- Telnet: cco.cisco.com
- Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or email@example.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or firstname.lastname@example.org.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
For a list of other internetworking terms, see Internetworking Terms and Acronyms document that is available on the Documentation CD-ROM and Cisco Connection Online (CCO) at the following URL: http://www.cisco.com/univercd/cc/td/doc/cisintwk/ita/index.htm.