Table 1-16 describes GTD parameters. Table 1-17 describes the GTD messages mapped to the GTD parameters and their fields.
Note A GTD parameter can be sent or received in any GTD message.
Table 1-16 GTD Parameters
GTD Parameter Name Description
RGN Redirecting Number The number of the endpoint from which the call is re-directed.
RNI Redirection Information Sent in the forward direction. Includes redirecting indicator, redirect reason, and redirect count. OCN Original Called Number In the case of multiple redirections it contains the
number of the endpoint at which the first redirection occured.
RNN Redirection Number The number of the endpoint to which the call is redirected.
RNR Redirection Number Restriction
Indicates whether the redirection number may be presented by the caller.
CDI Call Diversion Information
Sent in the backward direction. Indicates the reason for the diversion.
GNO Generic Notification Indicator
Indicates call status for supplementary services. CNN Connected number Final connected number
GEA Generic address Contains additional addresses indentified by qualifier.
CPC Calling party category Type of caller: subscriber, operator, payphone, etc. OLI Origination line
information
Type of caller for North American networks: For example, subscriber, operator, payphone. CID Carrier ID Identifies a transit carrier in North American
networks. TNS Transit network
selection
PCI Parameter compatibility information
Contains ISUP variant specific parameter that is not defined in GTD.
FDC Field compatibility information
Contains an ISUP variant specific parameter that is not defined in GTD.
TMR Transmission medium required
Bearer capacity BCI Backward call
indicators
Information sent from the called party to the calling party.
CHN Charge number Additional number used for charging. CAI Cause indicator CCITT and ANSI cause codes.
CPN Called party number Same as DNIS. It provides additional parameters such as nature of address and numbering plan indicator.
RDC Redirect capability Indicates the point at which redirection is possible in a call setup.
UUS User-to-user information
—
Table 1-17 GTD Parameters and Fields
GTD Parameter. Field RGN.noa RGN.npi RGN.pi RGN.# RNI.ri RNI.orr RNI.rc RNI.rr OCN.noa OCN.npi OCN.pi OCN.# CHN.npi CHN.# CHN.noa GEA.type GEA.noa
Table 1-16 GTD Parameters (continued)
GEA.cni GEA.pi GEA.# GEA.si CPC.cpc OLI.oli CID.ton CID.cid TNS.nip TNS.cc TNS.tns PCI.instr PCI.tri PCI.dat FDC.parm FDC.instr FDC.dat RNN.noa RNN.inn RNN.npi RNN.# RNR.rnr CDI.nso CDI.rr GNO.ni CNN.noa CNN.npi CNN.pi CNN.si CNN.# PRN.prot PRN.c PRN.o PRN.prv RDC.rc CGN.noa
Table 1-17 GTD Parameters and Fields (continued)
To create, modify, and read GTDs, the following Cisco objects are used:
• com.cisco.objclass.gtd
This is a JavaScript Cisco-specific object class that is used to create new GTD messages. To create an object of a specific class (instantiate) for creating a new GTD message, use:
X= new com.cisco.objclass.gtd()
Later, the GTD message can be represented in a format similar to:
X.message_type = "IAM"
Note IAM is used only as an example.
• com.cisco.signal.gtdlist
This is a Cisco-specific session variable that represents an array of GTD objects (each object representing a GTD message) for signaling events arriving on the incoming leg. The elements of this array can be accessed in read-only mode. The VoiceXML script accesses the GTD parameters and their fields from this session variable which is indexed by the signaling event as shown in the following format:
com.cisco.signal.gtdlist[“setup_indication”] where The elements of this array are read-only.
The VoiceXML/JSE script can access the GTD parameters and their fields from
com.cisco.signal.gtdlist indexed by the signaling event as in:
X = com.cisco.signal.gtdlist[“setup_indication”]
Initially, at the start of a session, an array is created with only one element (for Setup Ind event). Later, as other events are received, the GTD objects for the associated GTD messages are added to this array. For example,
X = com.cisco.signal.gtdlist[“setup_indication”] where X is read-only.
dat1 = X.PCI[0].dat for the dat field in the first instance of the PCI parameter. CGN.npi CGN.pi CGN.si CPN.noa CPN.npi CAI.cau 1 UUS.dat 1. CAI.cau is set by passing it as an attribute cisco-disc_cause through the <disconnect> element.
Table 1-17 GTD Parameters and Fields (continued)
Another Object can be created from com.cisco.signal.gtdlist using the new operation in com.cisco.objclass.gtd as in:
Y = new com.cisco.objclass.gtd(com.cisco.signal.gtdlist[“setup_indication”])
In this case, the new object Y contains a copy of the GTD message that arrived with the Setup Ind event and is a read-write object. Y can now be used for modifying GTD parameters.
• <transfer-name>$.com.cisco.signal.gtdlist
This is a Cisco-specific shadow variable that is used by the VoiceXML script to access GTD parameters on the outgoing leg after the <transfer> is complete. The shadow variable consists of the transfer name and “$” prepended to com.cisco.signal.gtdlist.
In <transfer name= “gtd_xfer”..../>, gtd_xfer$.com.signal.gtdlist is an array of GTD objects for the outgoing leg indexed by signaling event names mentioned in
gtd_xfer$.com.cisco.signal.gtdlist[“<event-name>”] where
<event-name> represents the following signaling events arriving on the incoming leg:
– alert_indication
– connect_indication
– disconnect_indication Example:
<assign name="data" expr=
"gtd_xfer$.com.cisco.signal.gtdlist['alert_indication'].PCI[0].dat"/>