Rules for Call Number Conversion

Rules can be deposited by means of which call numbers incoming and outgoing are converted.

With networked PBX's, for example, messages with a particular area code can be sent via a PBX at another site therewith.

The following kinds of numbers can be defined as "search parameter" and as "to be changed" by rules.

·D = Destination (CalledPartyNumber)

·O = Originator (CallingPartyNumber)

·R = Redirector (RedirectingNumber, DivertedNumber)

Examples:

Problem 1:

Because of the PBX-networking, the site 00498142 can be addressed directly with the "code" 8 via the networking.

Outgoing messages to e.g. 00498142xxxxxxxxx shall always be sent to 8xxxxxxxxxx.

Solution:

Deposit a rule at the ixi-UMS Kernel:

O;D=00498142;D=8[9]

Please take care of the following syntax:

<Direction>;<MatchExpression>;<ConversionExpression>

Function:

When a fax is sent to the number 0049 8142 4795875, the %PRODUKTNAME% Kernel checks in the table of rules whether there is a rule for this number.

The entry

O;D=00498142;D=8[9]

is found here.

O = Outgoing message

D = Destination 00498142

The actual rule is contained in the last part:

D=8[9]

D = number to be changed = Destination

8 = the 8 is added in front of the number to be copied

[9] = everything from the 9th digit on (incl.) is copied

So the rule transforms the number

0049 8142 4795875

into the actually dialed number

84795875

Problem 2:

1) Incoming messages are received via another networked PBX or collective connections.

2) The number conversion in the PBX has been changed. The numbers coming in at the ixi-UMS Kernel now are not in the LDAP data base and all the recipient numbers in the AD would have to be changed now.

Solution:

Deposit a rule at the ixi-UMS Kernel:

I;D=785;D=5[4]

Function:

The recipient numbers +49 8142 47995456, that are also dialed from outside, are listed in the LDAP.

Because of changes in the PBX, the code 78 had been added by internal routing.

An incoming fax to the number +49 8142 47995456 thus is delivered to the ixi-UMS Kernel with the extension 785456.

In order not to have to change all the recipient numbers in the LDAP, the "78" has to be removed at the ixi-UMS Kernel.

The only information the ixi-UMS Kernel gets from the PBX is the extension information: 785456

The entry

I;D=785;D=5[4]

is found here.

I = incoming message

D = to the recipient

785 = part of the recipient number the rule accesses

The actual part of the rule is contained in the last part:

D = recipient number shall be changed

5 = the 5 is added in front of the number to be copied

[4] = everything from the 4th digit on (incl) shall be copied

Alternative rule:

I;D=785;D=[3]

I = incoming message

D = to the recipient

785 = part of the recipient number the rule accesses

The actual rule is contained in the last part:

D = recipient number shall be changed

[3] = everything from the 3rd digit is copied

In both cases, the incoming number 785456 is "changed" into the number 5456 and then canoned into the number (now valid in the LDAP) by theixi-UMS Kernel:

+49 8142 47995456

Further information and configuration at ixi-UMS Kernel Configuration.

In a complex environment if mutual dependence and linked rules are necessary, they have to be entered manually.

For more information, see How To.