Address Translation

Choosing destination or source for pattern matching

When an address translation is used for CLI addresses of outbound calls, then optional attribute useSourceAsComparer can be used to specify whether pattern matching is done against

the destination address of the call - useSourceAsComparer="false" (default)
the source (CLI) of the call - useSourceAsComparer="true"

In both cases, the output translation is applied to the source address.

Example

A call is made from 381234 (source) to 07878123456 (destination).

If

useSourceAsComparer="false" -
The CLI translation will look at the destination, e.g. "07*" to match mobile numbers, and then apply a translation to the source, e.g. to make it complete "+441296381234".
useSourceAsComparer="true" -
The CLI translation will look at the source - "381234" - and if it matches, apply a transformation to the source, e.g. translating "3?12*" to "+4412963?12*".

DNIS matching

The dnis attribute is optional and provides a secondary pattern match. If used, both the primary CLI pattern and the secondary DNIS pattern must be matched for the CLI translation rule as a whole to match and be applied. It can be used for

outbound destination address translations
inbound CLI translations

See Example 5 below

Show examples

Example 2

This takes everything from the incoming string and places it where * is in the translated string:

Using the above translation:

Original	Translated
01296381200	sip:01296381200@sip.gradwell.net

Example 3

This takes everything after 0 on the incoming string and places it where * is in the translated string:

Using the above translation:

Original	Translated
0711111111	sip:0711111111@sip.gradwell.net

Example 4

This takes the data contained after sip: and before @, copies it and places it between sip: and @sip.gradwell.net:

Using the above translation:

Original	Translated
sip:12345@10.1.1.1	sip:12345@sip.gradwell.net

Example 5

For all inbound calls, if the DNIS begins with sip:6469374@, the CLI will be prefixed with 09018.

If a DNIS check is not required, simply omit the DNIS parameter.

Using the above translation:

Original	Translated
sip:12345@10.1.1.1	sip:0901812345@10.1.1.1

The importance of order

Incoming address strings are compared in the order the translations are listed. The first address translation that matches the incoming address string is the translation which is used.

For example, consider the address translations:

Using the above translations:

Original	Translation used	Translated
sip:0711111111	first (not the second, despite the match)	0711111111
sip:01234111111	second	01234111111

FAQ

Q1: We use a * translation rule to send all outbound calls to the SIP load balancer, e.g.

If incoming calls are passed through address translation, will incoming calls then be rerouted back out to the SIP load balancer rather than being passed to the Softdial CallGem™ processing engine?

The short answer here is No.

The generation of an InboundConnect [IC] message to the dialler (and associated logic) is controlled by the handler that has been associated with the inbound route in the following section of the STG config.xml :-

<inboundRoutes>
  <inboundRoute name="FromSIP">

    
    <handler>Dialer</handler>

    
    <ipCallProfile>Customers</ipCallProfile>

    
    <stripSipAddress>0</stripSipAddress>

  </inboundRoute>
</inboundRoutes>

Different incoming calls can be sent either to Softdial CallGem™ or proxied through STG by using ingress routing. See Configuration (Softdial Telephony Gateway™) - Ingress routes section

The translateBeforeIC setting is only applied when the route selected is Dialer. See Configuration (Softdial Telephony Gateway™) - Translations section