Mapping Web Data to Route Request Variables

You populate the Route Request message with information gathered in the Web request using a text file called the input map. Trailhead's Input map (in.map.properties) is a text file that maps fields found on the Trailhead callback form with ICM fields. The format of each entry is as follows:

<ICM variable> = <Web variable>

For instance, the file might contain this entry:

CED=Route

This entry specifies that the value in the Route field on the web request should be passed in the CED (Caller Entered Digits) variable in the Route Request message. In this way, the Input Map translates the information from the incoming web request and populates a route request message submitted to ICM.

Note that you can set the ICM variable to a literal string rather than a Web variable. For instance, consider the following example entry:

DN="1000"

This line ensures that 1000 is always passed in the DN field.

Important: Mapping DN to a literal string ensures that the same script is run for all web calls. See How the ICM script is selected for alternative methods for selecting scripts.

A sample input map appears in the Configuration File Reference section of this guide.

Using ICM Call Variable 10 (Lucent switches only)

When using the predictive call strategy with a Lucent switch, Media Blender makes internal use of Call variable 10. If you need to be able to use call variable 10 in your application, you can free up variable 10 by setting the calltag property in ACD.ciscocti.properties to another ICM call variable. See the Media Blender Reference Guide for a description of this and all ECTI properties.