• No results found

View Menu

In document Intelligent Network (Page 59-65)

3. Manual Setting

2.27 View Menu

The View menu contains the following items:

Tags Provides a window with current call instance data. The data may be manipulated from this window.

Dialogue Shows the complete INAP dialogue between the SSF and the SCF and between the SCF and the SDF.

Monitor List Shows the SCF’s monitor list.

Labels This displays a menu with choices for labelling the logic modules in the service logic display.

NPROCES List Shows a window where you may start a new SCF process from a queued list of processes provided by the NPROCES control type.

2.27.1 Tag Values Window

The Tag Values window shows the call instance data. It is possible to see if the tags have changed from one step to the next. An asterisk appears next to the most recently changed tags. The Tag Values window is shown below:

Figure 2.18 Tag Values Window

The Tag Values window includes the following:

Find Includes options to search for a string forward and backwards.

Save This menu enables you to save the current tag values in one of five slots. The tag values can be reloaded later using the Load menu or the Auto-load feature. An asterisk (*) next to the slot name on the menu indicates the slot is used.

Saving into a used slot will overwrite its contents. A slot can be cleared by selecting save when there are no tags in the tag buffer.

Load This menu enables you to load previously saved tags into the tag buffer from one of five slots.

The slot name on the menu is enabled when it contains at least one tag.

Auto-load Tags can be automatically loaded from a particular slot each time service execution begins. It is possible to select None (which disables Auto-load), or one of the slots created from the Save menu. When Auto-clear is activated, the tag buffer will be emptied before auto loading the tags. This ensures a known starting point each time service execution begins.

Tag Displays the name of the selected Tag.

This sets a tag breakpoint. A tag breakpoint will cause continuous service execution to stop when the tag with a breakpoint is changed.

This clears a tag breakpoint.

Auto-clear When Auto-clear is checked (default), all tag values are cleared each time the simulation is run. If this option is not checked, the tag values will remain when the simulation is restarted.

This is useful when it is desired to edit tag values before running the service.

Value Displays the value of the Tag.

Set This sets the value of a selected tag.

Delete This deletes a tag, which has been selected.

Delete All This deletes all tags.

The Tag Values window pane contains a list of current tags. The list includes four columns:

KoX This displays the Kind-of-Number,

of -Variable, of-LongInteger, Kind-of-String of the Tag.

Tag Name This displays the mnemonic name of the Tag.

Buf This displays which kind of Buffer is used.

There are four different Buffers: R-Response, Q-Query, T-Temporary and E-Event.

Value This displays the current value of the Tag.

2.27.2 SSF/SCF Dialogue Window

The SSF/SCF Dialogue window is shown below:

Figure 2.19

SSF/SCF Dialogue Window

By default, the SSF/SCF Dialogue window shows the INAP messages passed to and from the SCF and SSF. An option on the properties window allows you to select other information which can also be shown in the dia-logue window. Any combination of the following may be selected:

Dialogue INAP messages between SCF and SSF.

Changed Tags A list of tags that have changed after the execution of a logic module.

Logic Module The SA name, the SA side (OP or NOP), the SSL name and version, the outlet used, and the logic module name are listed as each logic module is executed.

Error Text Messages from the SCF which are normally only displayed in the window footer are also placed in the dialogue window.

In the left column in the SSF/SCF Dialogue window a character displays the type of the dialogue: I-Initial, A-Assisting, N-Non call, S-SDP/SCF dialogue.

The contents of the dialogue window may be saved to a file or printed for future reference.

2.27.3 SCF Monitor List Window

The SCF Monitor List window is shown below:

Figure 2.20

SCF Monitor List window

The SCF Monitor List includes the following columns:

Prio This displays the priority of the monitor request.

When several requests for the same event have been made, the priority will decide in which the order that the event is distributed to each requester. Requests with a priority of 0 will get the event first, requests with a priority of 15 will get the event last.

LM Name This displays the name of the Logic Module that requested the event.

SA Name This displays the name of the Service

Administrator that contains the requesting Logic Module.

SC Name This displays the name of the Service Customer that was in use when the monitor request was posted.

INVK The invoke id that the monitor request is associated with.

LEG The Leg shows which leg is being monitored.

EVNT This displays the type of event. Possible events are:

BCSM Error

EventNotificationCharging ApplyChargingReport CallInformationReport ReturnResultPromptCollect SpecializedResourceReport Internal

ErrorLevel2

BCSM When the event is BCSM, this column shows the mask for the monitored BCSM events. Use the right mousebutton to display the mask values.

The events possible are:

Alerting (CS1+) Answer

No Answer Disconnect

Re-answer (CS1+) Midcall

Abandon

Suspended (CS1+) Route Select Failure Called Party Busy

Called Party Not Reachable (CS1+) Collect Information

Analyzed Information

Mode This displays the mode of the event. There are three different modes: Notify & Continue, Interrupted, and Transparent.

2.27.4 Labels Menu

The Labels menu is shown below:

Figure 2.21 Label Menu

With the Label menu it is possible to decide how to label logic modules in the SSL display area.

LM names This option will present all logic modules with their Logic Module name.

DM ids This option will present the Data Module ID of the logic modules that have data.

None This option removes all logic module labels.

In document Intelligent Network (Page 59-65)