You are here: CSP Developer’s Guide: Overview > 11 Call Routing > Stage/String Translation

Stage/String Translation

You can configure the CH component to translate inpulsed data to be used for an outbound call. Inpulsed digits are stored into specified Inpulsed Data TLVs, and then reassembled in a specific order for the outbound call. There are eight generic Inpulsed Digits TLVs with which you can store incoming digits, and eight Outpulse Digits TLVs with which you can place the digits for outgoing calls.

Figure 11-11 Stage/String Translation

Inpulsed Digits

You configure Inpulsed Digits TLVs to store specific stage/string data from incoming calls. For example, you could configure the Inpulsed Digits 1 TLV (0x4E) to store Stage 1/String 1 data. Or you could configure it to store Stage 2/String 1 and Stage 4/String 1 data. Or, you could configure Inpulsed Digits TLV 1 to store Stage 2/String 1 data, and configure Inpulsed Digits TLV 2 to store Stage 4/String 1 data.

Outpulse Digits

Each Outpulse Digits TLV is used to outpulse a specific stage/string combination. You configure each Outpulse Digits TLVs to use the data from one or more Inpulsed Digits TLVs to send in the Outseize Control message. For example, you could configure Outpulsed Digits TLV 1 to outpulse the digits stored in Inpulsed Digits TLV 1. You could configure Outpulse Digits TLV 2 to outpulse the digits stored in Inpulsed Digits TLVs 1 and 2.

TLV Formats

Inpulsed Digits TLVs (0x4E–0x55)

Use these TLVs in conjunction with Outpulse Digits TLVs (0x56–5D) for Stage/String translation for tandem routing. The inpulsed digits stored in these TLVs are used to construct the Outseize Control message. You configure each TLV to store any stage/string combination(s) from the inpulsed digits.

Inpulsed Digits TLV values are as follows:

0x4E = Inpulsed Digits 1

0x4F = Inpulsed Digits 2

0x50 = Inpulsed Digits 3

0x51 = Inpulsed Digits 4

0x52 = Inpulsed Digits 5

0x53 = Inpulsed Digits 6

0x54 = Inpulsed Digits 7

0x55 = Inpulsed Digits 8

Table 11-9 TLV Formats

Description | Byte (Value)
--- | ---
Tag | Data[0] (0x4E–55)
Length | Data[1] Variable
Value | Data[3] Stage Number
Data[4] String Number
Data[:] Stage Number
Data[:] String Number
:
:

Outpulse Digits TLVs (0x56–5D)

These TLVs are used to construct the outpulse data in the Outseize Control message from the inpulsed digits stored in the Inpulsed Digits TLVs (0x4E–55). Each TLV outpulses a specific stage/string combination. You configure each TLV for which Inpulsed Digits TLV(s) it retrieves the digits to outpulse. The digits are then outpulsed in the Outseize Control message in the stage/string specified by that TLV.

The Outpulse Digits TLVs begin at PPL Config Byte 125 of the CH component. Byte 125 specifies the number of TLVs to follow. You configure PPL Config Bytes with the PPL Configure message.

Outpulse Digits TLV values are as follows:

0x56 = Outpulse Digits 1 (Stage 1/String 1)

0x57 = Outpulse Digits 2 (Stage 1/String 2)

0x58 = Outpulse Digits 3 (Stage 2/String 1)

0x59 = Outpulse Digits 4 (Stage 2/String 2)

0x5A = Outpulse Digits 5 (Stage 3/String 1)

0x5B = Outpulse Digits 6 (Stage 3/String 2)

0x5C = Outpulse Digits 7 (Stage 4/String 1)

0x5D = Outpulse Digits 8 (Stage 4/String 2)

Table 11-10 TLV Formats

Description | Byte (Value)
--- | ---
Tag | Data[0] (0x56–5D)
Length | Data[1] Variable
Value | Data[2] Inpulsed Digits TLV #
Data[3] Inpulsed Digits TLV #
:

Example

This example shows the configuration required for stage/string translation for an E1 R2 to ISDN tandem call. A block diagram representation of the sequence is shown next.

Figure 11-12 Stage/String Translation Example

The following are traces of an example message sequence for configuring TLVs for this scenario.

Important! Values that are part of a string, such as header data, AIBs, or config byte/value combinations, are enclosed in brackets. Bytes important to this configuration are in bold, with descriptive information following in parenthesis.

The following PPL Configure message configures Inpulse Digits TLV 1 (0x4E) to store stage 1/string 1 and stage 3/string 1 incoming digits.

[00 1d 00 d7 00 00 ff] [01 02 0d 03 00 00 00 0d 03 00 1f 17] [00 61] 01 04 [47 4e] (Inpulse Digits TLV 1) [48 02] [49 01] (stage 1) [ 4a 01] (string 1) [4b 03] (stage 3) [4c 01] (string 1)

The following PPL Configure messages configure Outpulse Data TLVs to reassemble inpulsed digits for outbound calls.

This PPL Configure message configures byte 125 (Number of TLVs) to 2.

[00 17 00 d7 00 00 ff] [01 02 0d 03 00 00 00 0d 03 00 1f 17] [00 61] 01 01 [7d 02]

The following PPL Configure message configures Outpulse Data TLV 1 (0x4E) to use the digits in Inpulse Digits TLV 1 for the outbound call. The digits will be placed in stage 1/string 1 of the Outseize Control message.

[00 1b 00 d7 00 00 ff] [01 02 0d 03 00 00 00 0d 03 00 1f 17] [00 61] 01 03 [7e 56] (Outpulse Digits TLV 1) [7f 01] [80 4e] (Inpulse Digits TLV 1)

Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.
Outgoing call setup during real-time call processing on a specific channel.
See Programmable Protocol Language.
A digital communications link - voice, data, and video at a 2.048 Mbps rate; 30B/2D or 31B/1D (ISDN); non-North American version of T1.
See Integrated Services Digital Network.