☰
Navigation :

Destination Translation

Destination Translation

When handling N2IWF sessions, an internal representation of the “destination” is kept for both the OCS and the network response (if applicable).

The destination is initially defaulted to a normalised protocol-specific field after
N2SVCD rule engine variable population is completed:

After initialisation, the destination is stored in the service context separately for both the OCS and the network and may have destination translation rules applied accordingly.

All destination translations for the N2IWF are configured in the TRANSLATIONS LogicApp service global variable as an N2SVCD rule engine ruleset where the N2IWF selector rule extensions apply. A maximum of one translation may apply during ruleset matching.

A sample translation configuration might be:

<global name="TRANSLATIONS" type="array">
    <translation original="111" translation="222" var="network" value="home" />
    <translation original="111" translation="000" />
    <translation original="222" network="444" ocs="333" />
    <translation original="333" network="444" />
</global>

In the above, three translations are defined and would have the following effect:

Original Destination Sent to OCS Sent to Network
111 222 222
222 333 444
333 333 444

Translation Definition

Each translation can support the following parameters:

Attribute Type Description
original String [Required] The received normalised destination, as determined by the protocol handler.
translation String The normalised destination to use for both OCS and network interactions.
ocs String The normalised destination to use for OCS interaction. Not used for network interaction.
network String The normalised destination to use for network interaction. Not used for OCS interaction.