Info

Messages:

(1) Origination_Attempt.

(2) Info_Collected.

(3) Info_Analyzed.

(4) Termination_Attempt.

Source: TR-NWT-001285. Reprinted with permission of Bellcore. Copyright © 1992.

(1) Origination_Attempt.

(2) Info_Collected.

(3) Info_Analyzed.

(4) Termination_Attempt.

Source: TR-NWT-001285. Reprinted with permission of Bellcore. Copyright © 1992.

are stored in semipermanent memory of SSP, and parameters with information "dialed" by the caller. The parameters are listed in Table 16.6-1.

For calls originated by analog or ISDN lines attached to SSP, UserlD (Par.l), ChargeNumber (Par.8), LATA (Par.9), and CallingPartyBGID (Par.18) are stored attributes.

Some parameters are stored attributes of the calling analog subscriber line, or the incoming non-ISUP trunk, but are parameters in SETUP messages received from ISDN users (Section 10.3.2), or in IAM (initial address) messages for trunks with ISUP signaling (Section 11.2.4). For example, BearerCapability (Par.5) for analog lines always indicates "3.1 kHz audio," but the BearerCapability received in SETUP and IAM messages can indicate various capabilities. The same holds for CallingPartylD (Par.7).

PrimaryCarrier (Par. 10) is an attribute of analog and ISDN lines that can be overwritten by the caller, by dialing a \GXXX code.

CalledPartylD (Par.13), FeatureCode (Par.14), AccessCode (Par.15), CollectedAddressInfo (Par.16), and CollectedDigits (Par.17) are parameters that always hold information received from the calling party. Table 16.6-2 shows the combinations of these parameters in messages caused by the various trigger types. For example, the info_collected message, sent when an OHD trigger has been encountered, may include CollectedAddressInfo only

Table 16.6-2 Combinations of parameters holding dialed digits.
0 0

Post a comment