Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The configuration of the GTP' agent includes the following tabs:

  • Source
  • Miscellaneous
  • Advanced

Source Tab

The  Source  tab includes connection type settings.

ItemDescription

Protocol

The protocol type that you want the agent to use: TCP or UDP. For further information, see Limitations - GTP' Transported Over TCP in GTP' Agent MZSH Commands, Events and Limitations[hide]3.0[/hide].

Port

The port through which the agent should await incoming data packages. This port must be located on the host where the EC is running.

The default value is set to 3386.

Note!

Two workflows that are running on the same EC, can subscribe to the same Port and GSNs, if they use different Protocol settings.

GSN IP Address

The IP addresses or hostnames of the GSN nodes that provide the data.

Server Port

The server port number for each node. The agent will detect GGSN source port changes via the Node Alive Request or Echo Request messages. If a change is detected, it is is registered in the System Log. The agent's internal configuration is updated.

Note!

If more than one source is defined on one IP address, port changes are not supported and only connections from the specified ports are accepted from that host.

Miscellaneous Tab

The Miscellaneous tab includes collected format and storage settings of the data that is collected by the agent.

Field/OptionDescription

Format

Format must match the Data Record Format in Data Record Packet IE. This is applicable if the Packet Transfer Command is either Send Data Record Packet or Send possibly duplicated Data Record Packet.

Perform Format Version Check

When selected, the Data Record Format Version in Data Record Packet IE must be identical to the setting in Format Version.

Format Version

Format version must match the Data Record Format Version in Data Record Packet IE. This is applicable if the Packet Transfer Command is Send Data Record Packet or Send possibly duplicated Data Record Packet.

Directory

Specify either the relative pathname to the home directory of the user account, or the absolute pathname of the target directory in the file system on the local host, where the intermediate data for the collection is stored.

The intermediate data includes:

  • Files that keep track of sequence numbers and restart values

  • A directory called duplicates, where duplicates are saved.

    Note!

    This directory must be attended to manually.

    Note!

    When using several ECs, make sure that the file system that contains the GTP' information is mounted on all ECs.

Acknowledgement from APL

Select this checkbox to enable an acknowledgement from the APL module that connects to the GTP' agent. This enables you to make sure that data is transmitted completely.

No Private Extension

Select this checkbox to remove the private extension from any of the agent's output messages.

Use seq num of Cancel/Release req.

Select this checkbox to change the type of the sequence numbers that are populated in a Data Record Transfer Response to either Release Data Record Packet, or Cancel Data Record Packet, in the Requests Responded field. Otherwise, the agent applies the sequence number of the released, or cancelled, Data Record Packet.

Advanced Tab

The Advanced tab consists of the transmission, sequence and duplicate handling settings for the agent.

ItemDescription

Max Wait for a Response (sec)

The maximum time for which the GTP' agent can expect a Node Alive Response message.

If both this value and the Max Number of Request Attempts value, are exceeded, a message is sent to the System Log.

For example: If Max Wait for a Response is 20 and Max Number of Request Attempts is 5, the warning message will be logged after 100 seconds.

Note!

The value also indicates the maximal period during which the GTP' agent awaits a Redirection Response. This period begins right after the agent releases a Redirection Request to the agents that it is configured to receive data from.

Max Number of Request Attempts

Specify the maximum number of attempts to perform in order to receive a Node Alive Response and Redirection Response.

Max Outstanding Numbers

Specify the maximal number of packages that you want kept in memory for sequence number checking.

Max Drift Between Two Numbers

Specify the maximum numbers that can be skipped between two sequence numbers.

Clear Checking

Select this checkbox to avoid saving the last sequence number when the workflow has been stopped.

Clear the checkbox to save the sequence number of the last collected package when the workflow is stopped. This way, as soon as the workflow is restarted, a package with the subsequent number is expected and the workflow continues processing from the where it had stopped.

Agent Handles Duplicates

Select this option to store duplicates in a persistent data directory that you specify on the Miscellaneous tab. The packet will remain in the directory until the agent receives a request to release or to cancel it.

Route Duplicates to

Select this option to route duplicates to a link that you select from the drop-down list.

Alternate Node

Enter the hostname or IP-address of a host that runs an alternate Charging Gateway device as a backup.

If you enter an IP address, the GTP' agent will include it in the redirection request that it sends to the GSN.

Note!

The GTP' agent does not backup any of the data that it manages. Make sure that the GSN node takes care of backup.

Decoder Tab

The Decoder tab consists of the decoder settings.

ItemDescription

Decoder

Click Browse and select a pre-defined decoder. These decoders are defined in the Ultra Format Editor, and are named according to the following syntax:

<decoder> (<module>)

The option MZ Format Tagged UDRs indicate that the expected UDRs are stored in the specific format. Select this option to make the Tagged UDR Type list accessible for configuration.

Tagged UDR Type

Click Browse and select a pre-defined Tagged UDR Type. These UDR types are stored in the Ultra and Code servers. The naming format is:

<internal>(<module>)

If the decoder is intended to reprocess UDRs of an internal format, the Decoder MZ format tagged UDRs has to be selected enabling this list. Once enabled, the internal format must be selected.

Full Decode

Select this check box to enable full decoding of the UDR, before it enters the workflow. This, in turn, might reduce performance rate.

Clear this check box empty to minimize decoding work in the agent. By leaving this check-box empty, you postpone decoding, and discovery of corrupt data to a later phase in the workflow.


  • No labels