Connect to SRF

required, custom

Select whether the IVR is connected to using a ConnectToResource (CTR) or EstablishTemporaryConnection (ETC) message. A ETC message is used when the IVR function is performed by a physically separate machine to the MSC or switch.

IP Address

optional

When using ConnectToResource, this field is used to identify the IP routing address - the E.164 address of the IP function on the switch or MSC. It may be left empty in which case the switch must be able to select toe IVR location.

When using EstablishTemporaryConnection, this field must identify the location (in E.164 number format) of the IVR function.

Examples

• 6422 3333333

When Oracle OCNCC is used with an ETC, the address may include both the correlation ID and SRF ID within the address field. The format usually is <IVR prefix><correlation ID><SRF ID> which is then decoded by the IVR.

In this situation, enter the prefix in this field and tick the "Merged Address Field?" option.

Examples

• 642200 0001 1

SRF ID

optional

In networks with an external IVR, the IVR must send a Specialised Resource Report to the SCF when it is ready to play an announcement. As there may be multiple SCFs within the network, the EstablishTemporaryConnection must include the ID of the SCF that is requesting the announcement being played.

Examples

• 4

Message ID(s)

required

When requesting the IVR to play an announcement the announcement to play is identified by a numeric number.

The number is mapped on the IVR to a sound file to play.

Multiple announcement IDs can be provided (separated by commas), in which case the PlayAnnouncement request will send the list of IDs.

Examples

• 1010
• 1010, 4890

Hang Up At Announcement?

required

Use this option to choose whether the listening party hangs up before or during the announcement, or listens to the entire announcement.

When listening to the entire announcement ("no" is selected), this node will respond to the IN with an "announcement successfully played" message (an INAP SpecializedResourceReport). A subsequent node is expected to deal with call completion.

When "before" or "during" is selected, the IN Tester will respond to the IN with an appropriate message (see the "Expect RRBCSM?" field) indicating that the calling party has disconnected. This ends the call.

Expect RRBCSM?

required

Use this flag to choose whether to expect a RequestReportBCSM message before the ConnectToResource or EstablishTemporaryConnection message is received.

If set to "yes", the test expects a RequestReportBCSM message prior to the ETC or CTR with both Abandon and Disconnect (leg #1) armed.

If set to "no", no such message is expected.

If set to "yes", and a call hangup occurs during the announcment ("Hang Up At Announcement?" is set to "before" or "during") then an EventResponseBCSM is sent to the SCP, rather than a TCAP Abort.

Minimum # of Digits

optional

The minimum number of digits that the user must enter before their response will be considered valid and sent back to the SCP.

This defaults to 1 so by default the user must enter at least one digit.

Examples

• 1
• 32

Maximum # of Digits

optional

The maximum number of digits that the user may enter before their response is automatically considered complete. Digits entered after this maximum will be ignored by the SRF in generally.

There is no default for this, so unless it is specified the user will need to enter the stop digit (usually a '#') to indicate their entry is finished.

Usually the minimum and maximum would be set to 1 for IVR menus.

Examples

• 1
• 32

Is Announcement Interruptable

optional

If this flag is set to true, the user can start responding to the prompt prior to the announcement to the user completing.

The default for this flag is true, so unless explicitly set to false, users will be able to interrupt the announcement.

Collected Digits

required

The digits entered by the user, excluding any stop digit entered by the user.

Examples

• 5
• 12789450985101824