BusinessPhone Communication Platform 7.0
Facilities

## Individual Number Translation

## Definition

This feature supports an individual number translation of the public network DDI number as well as a private network CN numbers to corresponding internal directory numbers and vice versa. From release 13 onwards internal directory numbers (fictive numbers) can be translated in the DDI number translation table.

Note

This feature has been renamed and was formerly called “DDI number translation”

## Use

The reason for a number translation is relevant in cases, in which the DDI/CN number range provided by the network does not fit or is not available for use, partly or completely, as internal number range within the system.

The DDI number translation for internal calls makes it possible to configure a homogenous numbering plan with unique directory numbers of up to 8 digits within the whole corporate network.

Furthermore it can be used for a scenario where the PBX may be connected to two different network operators with different numbering plans. Two different number translation tables may be used.

The following list shows the facilities which are implemented in Release 13 and covered by DDI number translation:

- Bypass call diversion and IID
  (Individual Internal Diversion - follow me)
- Call handling
  (ACD, automatic callback, call pick-up, conference, fictive number, intrusion, integrated cordless and transfer are included)
- Call Information Logging (CIL)
- Directory numbers (DDI table)
- Diversion direct
- Diversion on busy Diversion on no reply (div. on not available)
- Individual Internal Diversion (IID - follow me)
- Information
- Mailbox system
  (voice mailbox/external, voice messages, voice message before answering, conversation recording and dictaphone functions are included)
- Message system
- Operator (temporary answering position)
- Telephone directory

## Operation

### Number translation

The number translation is provided in following way:

A programmable cross reference table (including two different number translation tables) allows up to 400 internal directory numbers to be translated to corresponding external/private DDI numbers.

The number translation can be made both for incoming and outgoing calls per dedicated trunk:

- an external/private DDI/CN number (1-8 digits) is translated to the corresponding internal 1-4 digit directory number.
- an internal directory number is translated to the corresponding external/private DDI/CN number when creating and providing the calling/connected line identification.

If an external or internal number is not found in the translation table or no translation can be done, the ordinary number analysis will be performed in any case.

Note

By performing a cold start all configuration settings for DDI number translation are set to default. If warm start is performed, all settings (command 2263 as well as DDI table) will be leaved unchanged.

### Display handling (of internal calls)

The DDI number is indicated on all displays, if internal DDI number handling is enabled. The only exception is the display of the A-party, where the dialed number is indicated in the same format, as the user dialed it.

If an incoming call relies on an individual number translation, and the call is redirected from the called (searched) B-party to another C-party, the display of the C-party will shows the called DDI/CN number of the B-party (and not the internal primary directory number). The same information is also carried at redirected network calls to other CN C-party.

A party |  | the calling party. |
B party |  | the called party. |
C party |  | the diverted-to party in case of diversion or follow me. |

### Interaction with other features

#### Composition of public calling/connected number

The public DDI number translation concerns the least significant part of the A-/B- subscriber number. The most significant part, defined with system category ‘Public directory numbers’ is not affected by the translation when the new public A-/B-number is to be composed. The complete number is then used in conjunction with ISDN/DSS1 calling/connected line identification for services such as CLIP, COLP and AOC.

#### Handling of public called party numbers

The existing handling and categories for control, remove and include of pre-digits to the received DDI digits from public network are executed before the DDI number analysis and translation starts.

#### Composition of private calling/connected number

The private number translation concerns primarily the least significant part of the complete private A-/B- , (LOC+ CN number), thus the CN number part. This is related to a closed number plan usage.

In some cases own LOC (LOcation Code) has to be translated and also other LOCs in some transit call cases. This is related to an open number plan usage.

The complete number is then used in conjunction with ISDN/QSIG calling/connected line identification for services such as CLIP, COLP and AOC.

Additionally for proprietary CN calls the translation concerns also the alerted and complementary (redirected) number identification.

#### Gateway/transit calls

At incoming calls the received DDI/CN number can always be translated. The call may terminate in the system or continue thereafter as gateway/transit call setup.

The calling/connected line identification for services, CLIP, COLP and AOC, are not affected by the gateway/transit system.

#### Interaction with external applications

The interaction with external applications/facilities such as CTI, PES is not affected by the individual number translation.

#### Interaction with internal applications

The interaction with internal applications/facilities such as call logging and call metering is not affected, the existing interaction with the internal directory numbers is valid for call registration.

## Capacity

The feature is independent of used line or register signalling, i.e. at incoming calls:

- available for all types of automatic incoming calls
  and outgoing calls
- available where calling/connected numbers are supported.

It offers two different number translations for 400 internal directory numbers (in max. 200 intervals).

## Limitations

Although it is possible with the individual number translation to expand the corporate number plan in a private network, the total number length in the network is still limited to eight digits, i.e.,

- in a closed numbering plan 1-8 digit CN number
- in an open numbering plan 1-8 digit LOC + CN no.’s

The following facilites and applications are not expandable to support DDI numbers from internal calls:

- Abbreviated number - individual numbers
- Authorisation code
- Automated Attendant
- Call Metering (CM)
- Computer Telephony Integration (CTI)
- DISA with password control
- Individual internal diversion (IID - follow me)
  from Operator
- Group (PBX) - hunting
- Hotel facilites
- Least Cost Routing
- Name selection
- Programmable and fixed keys
  (Phone programming)
- System programming

## Programming

The DDI number translation table for internal and external calls can be enabled or disabled via command 2263 Type of individual number translation.

If DDI number handling for internal calls is enabled, the user will dial and see DDI numbers instead of internal directory numbers. If DDI number handling for internal calls is disabled the user interface will remain unchanged.

In BMS the corresponding DDI number will be displayed in a detailed screen of the selected extension.

The following command values are accepted:

Value | Description
0 | DDI number translation for internal calls is disabled
1 | DDI number translation according to table “DDI1”
2 | DDI number translation according to table “DDI2”
3 | DDI number translation according to tables in order “DDI1” and “DDI2”
4 | DDI number translation according to tables in order “DDI2” and “DDI1”

These commands are only accessible via BMS:

2260 |  | DDI/CN number translation

2263 |  | Type of individual number translation

1804 |  | DDI number translation

## Equipment

The feature is supported by ASB 150 02 R13 or higher system releases.

In order to have access to the feature, the proper licensing concept has to be used, see Facility Description – General (155 34-ASB 150 02 Uen), chapter ASB150 02 Licensing.

Revision: E © Ericsson Enterprise 2005