BusinessPhone Communication Platform 7.0
Facilities

## Networking Based on Digital Lines

Definition
Definitions & Abbreviations
Standards
Use
Private Network with only ASB 150 02 systems
Private Network with ASB 150 02 and ASB 501 systems
Private Network with ASB 150 02 and other-vendor PBXs
Operation
General
Networking packages
Features and Services – Overview
System feature – Common Corporate Numbering Plan
System feature – Location code
System feature – Node Identity
System feature – Private Network Routing
System feature – Number conversion
System feature – Basic call
Supplementary service – Calling/Connected Line/Name Identity
Supplementary service – Advice of charge
Supplementary service – User-to-User Signalling
Needed UUS services for proprietary CN features
Proprietary service – Account number
Proprietary service – Call Transfer
Proprietary service – Centralised Operator
Proprietary service – Camp on
Proprietary service – Called party number transfer via UUS1
Proprietary service – Intrusion
Proprietary service – Message waiting indication
Proprietary service – Rerouting
Dependency of Facilities on Internal/External Handling of Private Network Calls
Capacity/Limitations
Programming
Q/T Link settings
General settings
Programming of the “Own location code”
Programming of the Private Network Router (PNR)
PNR alternative Routing
Basic call service – Travelling Class Mark
Basic call service – Transit counter
Calling/Connected Line/Name identity
Supplementary service UUS
Proprietary service – Call back
Proprietary service – Call diversion
Proprietary service – Camp on
Proprietary service – Intrusion
Proprietary service – Message Waiting Indication
Proprietary service – Rerouting
Extension settings
Tone settings
Equipment

## Definition

Digital Private Networking is centered around two main concepts:

- Digital private networking between ASB 150 02 and
  ASB 501 systems, based on DSS1 signalling (ETSI standard) over switched public lines.

- The interface between the private network and ASB 150 02 is at the T-reference point.

- Digital private networking between ASB 150 02/ASB 501 and other-vendor exchanges, based on QSIG (ETSI/ECMA/ISO standard) over leased lines.

- The interface between the private network and ASB 150 02 is located at the Q-reference point

At the interface between the private network and ASB 150 02, Basic Access (BA, = 2B+D) and Primary Rate Access (PRA, = 30B+D) are supported for point-to-point connection, at the Q-reference point as well as the T-reference point.

Connection via switched public ISDN lines is referred to as a part of a Virtual Private Network, as non-permanent connections are used.

The feature “VPN service from PSTN” which allows to connect ASB 150 02 via switched lines with a public network supporting the central database for storage of all private network numbers is not affected by the VPN functionality in ASB 150 02 (for more information concerning the feature “VPN service from PSTN” refer to the corresponding document (364/155 34-ASB 150 02 Uen).

### Definitions & Abbreviations

Abbreviation / Term | Definition (Sheet 1 of 2)
AOC | Supplementary Service Advice of Charge
BA | Basic Access (2B+D), T- or Q-reference point to the network
CLIP | Calling Line Identification Presentation
COLP | COnnected Line identification Presentation
CLIR | Calling/Connected Line Identification Restriction.
CNIP | Calling Name Identification Presentation
CONP | COnnected Name identification Presentation
CNIR | Calling/Connected Name Identification Restriction
CN | Corporate Network
CN-number | Corporate Network number
CN call | Call between CN users
CNP | Co-ordinated Numbering Plan
COP | Centralised Operator
Corporate digital networking | Private digital networking
DSS1 | Digital subscriber Signalling System number 1
ECMA | European Computer Manufacturers Association
ETSI | European Telecommunications Standards Institute
Gateway call | A call setup between two trunk interfaces using different signalling protocols, (e.g. QSIG incoming to DSS1 outgoing)
GFP | Generic functional protocoll (base for each QSIG - supplementary service except CLIP/CLIR which is based on the DSS1 protocoll)
IE | Information element All QSIG messages are built up of different information elements, which contain specific information
ISDN | Integrated Services Digital Network
ISDN service functionality | Calls where features and services are supported by DSS1 supplementary services.
LOC | LOcation Code based numbering plan
Main node | A PBX in a private network that supports: 1) gateway functionality, 2) centralised service features (e.g. Centralised Operator), 3) intelligent routing service node PBX in a private network environment.
Node | PBX in a private network environment
Non-proprietary CN call | Call between CN users which is only based on Standard QSIG functionality
Other vendors PBX | Exchange which does not support proprietary services
PNR | Private Network Router
PNAC | Private Network Access Code
PRA | Primary Rate Access (30B+D), T- / Q-reference point to the network
Private lines | tie lines + leased lines
Proprietary CN call | Call between CN users where proprietary services are supported
Proprietary service functionality | VPN or QSIG call with features and services being supported by DSS1 or QSIGsupplementary services, and additionally, proprietary features and services being supported by the proprietary ISDN UUS protocol.
PSS1 | Private Signalling System, Number 1
Public gateway exchange | The PBX in the private network from where calls leave the private network and will be terminated in the public net
QSIG (PSS1) | Q interface SIGnalling protocol, a uniform international corporate network signalling standard.
QSIG service functionality | QSIG call = Corporate call via the private ISDN network with features and services being supported by QSIG supplementary services.
TCM | Travelling Class Mark
Transit call | A call which will be routed through a network node, whereby two trunk interfaces will be occupied. The Signalling scheme between the two trunk interfaces can either be the same or different ones.
TON | Type Of Number
UUI | User-to-User Information
UUS | User-to-User Signalling
VPN | Virtual Private Network
VPN call | A VPN call is a corporate call via the public ISDN network (T-reference point) for which the private called destination number is partly or completely converted by ASB 150 02 into a public called destination number

### Standards

QSIG Basic Call control according to the ETSI and ISO standards:
ETS 300 172 and ISO 11572, 11574

QSIG Generic Functional Protocol (GFP) according to the ETSI and ISO standards:
ETS 300 239 and ISO 11582, within the scope of the supported QSIG Supplementary services (see below)

QSIG Supplementary services CLIP, COLP, CLIR according to the ETSI and ISO standards:
ETS 300 173 and ISO 14136

QSIG Supplementary services CNIP, CONP, CNIR according to the ETSI and ISO standards:
ETS 300 238 and ISO 13864, 13868

QSIG Supplementary service Advice of Charge according to the ECMA 211/212 standard

## Use

### Private Network with only ASB 150 02 systems

The following example shows a private network with only ASB 150 02 nodes.

Standard QSIG and proprietary services are supported via leased and / or switched lines.

Example:

The symbols Q & T mean 1 or more Q-/T-interfaces.

### Private Network with ASB 150 02 and ASB 501 systems

The following example shows a private network with ASB 501 as main node and ASB 150 02 as end nodes (“branch offices”). Standard QSIG and proprietary services are supported via leased and / or switched lines.

Example:

The symbols Q & T mean 1 or more Q-/T-interfaces.

All gateway and main node functionalities are provided by ASB 501. The ASB 150 02 nodes can have own public network access for own public traffic, so as not to overload connections with the main node. Furthermore, it is also possible to connect the ASB 150 02 end nodes (dotted lines) directly, to prevent overloading of connections to the main node by traffic carried only between the end nodes.

### Private Network with ASB 150 02 and other-vendor PBXs

ASB 150 02 relies on QSIG signalling via leased lines to connect the system to other-vendor PBXs.

Gateway between public and private network is only supported for Basic Calls.

Example:

The symbols Q & T mean 1 or more Q-/T-interfaces.

## Operation

### General

A digital private network depends on two major issues:

- Type of interworking PBX equipment
- Type of network

#### Type of interworking PBX equipment

There are two different types of PBX equipment to be connected in a private network:

- Ericsson PBXs, ASB 150 02 or ASB 501

- Interconnection based on DSS1 signalling (via public ISDN or leased lines) or QSIG signalling (via leased lines) supporting the standard and proprietary services and features

- Other-vendor PBX

- interconnection based on DSS1 signalling (via public ISDN or leased lines) or QSIG signalling (via leased lines) supporting the standard services and features

#### Type of network

There are two different types of interconnected networks:

- ASB 150 02 is interconnected to other nodes via the public switched ISDN network as a node in a VPN:

- Public ISDN signalling protocol DSS1 signalling is used.
- Basic call control and supplementary services are based on ETSI standards.
- Proprietary services are carried in standard public ISDN supplementary service UUS using the proprietary ASB 501 protocoll.

- ASB 150 02 is interconnected to other nodes via leased lines (tie lines):

- QSIG signalling is used
- Basic call control and supplementary services are based on ECMA/ETSI standards
- Proprietary services are carried in standard public ISDN supplementary service UUS using the proprietary ASB 501 protocoll.

### Networking packages

The private digital networking functionality is packaged and licensed.

A Networking Package license is valid for BTU-B (Basic Access), BTU-D (Primary Rate Access) and IPU

Protection covers services and system features.

In order to have access to the services of a given Networking package (Standard digital Networking, Full digital Networking), the proper licensing concept has to be used, see Facility Description – General (155 34-ASB 150 02 Uen), chapter ASB150 02 Licensing

The selected licensing defines the enabled services as well as the number of supported interface (B-channels) used for networking purposes.

#### FNetworking package – Overview

Functions | Standard digital Networking Package | Full digital Networking Package
CN-System features | X | X
Interworking with ASB 150 02 | X | X
Interworking with ASB 501 | X | X
Interworking with other vendors | X |
Switched lines DDS1 supplementary services (VPN) | X | X
Switched lines proprietary services over UUS |  | X
Leased or VoIP lines QSIG supplementary services | X | X
Leased or VoIP lines proprietary services over UUS |  | X

### Features and Services – Overview

#### System features

- Common corporate numbering plan
- Location code
- Node identity
- Private Network Routing (over leased and switched lines)
- Number conversion
- Basic call routing (gateway traffic) between public and private ISDN.
- Basic call services (QSIG standard services)

- Calling line category
- Transit Transit counter

#### Supplementary services (QSIG standard services)

- Advice of charge (QSIG)
- Calling/Connected Line Identity (QSIG and DSS1)
- Calling/Connected Name Identity (QSIG)
- UUS 1, 2, 3; carrier mechanism for proprietary service (QSIG and DSS1)

#### Proprietary services based on the UUS protocol

- Account Code
- Bypass call forwarding
- Call back on no reply/busy
- Call diversion & follow me
- Call Transfer
- Calling line category
- Calling/Connected line identification
- Calling/Connected name identification
- Camp on
- Centralised Operator
- Day/night service notification
- Intrusion
- Message waiting indication
- Rerouting
- Transit counter
- Travelling class mark
- CN number transfer via UUS 1

### System feature – Common Corporate Numbering Plan

In the Common Corporate Numbering Plan each addressable entity in the private network is identified by a unique network identity.

A network identity consists of:

- a unique location code and/or a unique node identity for each node (1-4 digits)
- an internal directory number (1-4 digits)

3 different types of Common Corporate Numbering Plan are possible:

- LOC (LOcation Code based numbering plan)

- Each node or group of nodes is identified by a unique location code. One or more nodes can form a logical group. The grouping of nodes is independent of geographical or public boundaries.
- The dialling format is: LOCxxxx
  LOC: location code
  xxxx: internal directory number

- CNP (Co-ordinated Numbering Plan)

- Each node is identified by a unique internal directory number. This numbering plan is related to the fixed or co-ordinated numbering plan for tie-line traffic but:

- no prefixing is necessary
- complete dialled number is sent to the network

- The dialling format is: yyxx
  yy: node identity
  yyxx: internal directory number

- Mixed numbering plan

- Covering the nodes within a local segment by a CNP and covering the whole network by LOC.
- I.e.: Nodes within a local segment are covered by CNP and one or more logical segments are covered by one LOC.

In order to be flexible with regard to corporate networks using a more than 4-digit numbering plan, or a numbering plan which does not fit to the internal
4-digit numbering scheme, ASB 150 02 supports an individual DDI number translation.
The number translation can be made both for incoming and outgoing calls per dedicated trunk:

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

Note

Although it is possible with the individual number translation to expand the size of the numbering scheme of each network node, the supported CN number length is still limited to eight digits.

For further information please refer to the document “Individual Number Translation (170/155 34-ASB 150 02 Uen).

##### Example for a Common Corporate Numbering plan

##### Example of programming the Private Network Router

For this example only 2 route choices will be used.

Private network Access Code | Destination PBX | TON priv calling | 1 Route choice | 2 Route choice
|  | digit arrangement |  |  | digit arrangement
route choice | TON priv/pub called | remove | predigits | route choice | TON priv/pub called | remove | predigits
PBX A:
18 | proprietary | RL0 | 14 | UNK, priv |  |  |  |  |  |
3102 | proprietary | RL0 | 14 | RL0 |  |  |  |  |  |
22 | proprietary | RL0 | 15 | UNK, priv |  |  |  |  |  |
23 | proprietary | RL0 | 15 | UNK, priv |  |  |  |  |  |
7 | proprietary | RL0 | 13 | UNK, priv |  |  | 12 | UNK,pub | 1 | 03865257
850 | proprietary | RL1 | 11 | UNK, priv |  |  | 12 | UNK,pub | 3 | 00468719
PBX B:
2 | other | RL0 | 00 | UNK, priv |  |  |  |  |  |
4 | proprietary | RL0 | 01 | UNK, priv |  |  |  |  |  |
5 | proprietary | RL0 | 01 | UNK, priv |  |  |  |  |  |
843 | proprietary | RL1 | 02 | UNK, priv |  |  | 03 | UNK,pub | 3 | 00431811
PBX C:
3102 | proprietary | RL0 | 11 | RL0 |  |  | 12 | NAT | 4 | 18113102
4 | proprietary | RL0 | 11 | UNK, priv |  |  | 12 | UNK,pub | 1 | 018114
5 | proprietary | RL0 | 11 | UNK, priv |  |  | 12 | UNK,pub | 1 | 018115
18 | proprietary | RL0 | 11 | UNK, priv |  |  | 12 | UNK,pub | 2 | 0181118
22 | proprietary | RL0 | 11 | UNK, priv |  |  | 12 | UNK,pub | 2 | 0181122
23 | proprietary | RL0 | 11 | UNK, priv |  |  | 12 | UNK,pub | 2 | 0181123
850 | proprietary | RL1 | 11 | UNK, priv |  |  | 12 | UNK,pub | 3 | 00468719
PBX F:
2 | other | RL0 | 0 | UNK, priv |  |  |  |  |  |
9 | proprietary | RL0 | 0 | UNK, priv |  |  |  |  |  |
843 | proprietary | RL1 | 0 | UNK, priv |  |  |  |  |  |

### System feature – Location code

Within a “Location” (Arear) one or more PBXs may be grouped together in order to be identified by the Location code consisting of up to 4 digits. This number is used in a corporate network to define the PBX, or a group of PBXs to which the call should be routed.

### System feature – Node Identity

Within a corporate network every PBX is identified by the Node Identity consisting of up to 4 digits. This number is used in a corporate network to define the PBX to which the call should be routed.

The node-ID is implicitely given with the definition of routes in the other connected nodes.

In a mixed number plan consisting of several locations (groups of PBXs) each PBX in the corporate network may be reached by dialling the Location Code and the Node Identity of the desired PBX. If the location only consists of one PBX, this PBX will not have a node-ID.

### System feature – Private Network Routing

#### Definition

In ASB 150 02 without Digital Private Networking two types of external call routing are available:

- basic routing
- least cost routing.

Basic routing gives access to defined trunk(s), but makes alternative routing by a simple prefixing to the called number (via tie line) also possible.

Least cost routing (LCR) makes a more enhanced analysis of the route (carrier) choice and, if necessary, carries out a number conversion of the destination number. Cross reference tables enable the destination number conversion between different types of network choices.

Both routing features do not meet the requirements and are not suitable for the structure of private network routing.

For private network calls the Private Network Router (PNR) will be initiated as soon as the internal number analysis gives a private access number.

The PNR is intended to be a routing mechanism of its own, which has the following main tasks:

##### Routing based on dialled number

According to the dialled number a destination number conversion based on the chosen route will be performed.

##### VPN functionality

VPN functionality with full number conversion of private network directory numbers to public numbers (conversions up to max. 16-digit public directory numbers).

##### Alternative routing

The PNR offers 4 route choices for each private network directory number, with the first one having the highest and the fourth one the lowest priority.

#### Route selection principle

The 4 route choices are always available in case of internally-originated calls, as well as non-proprietary calls. All route choices will be checked according to their priority and if all route choices fail due to one of the special causes described below, the call will be released and the originator will receive congestion.

In case of a programmed trunk reroute position, transit calls will be rerouted according to the conditions in the node, otherwise the node sends congestion to the preceding PBX, and this exchange may perform alternative routing according to its capabilities.
In case of proprietary transit calls the number of available route choices can be restricted. This restriction makes it possible to exclude unintentional routes (e.g. public connections) and to force the preceding PBX to perform a more cost effective alternative routing (e.g. by selecting a leased line).

Internal calls via LCR will only use the first route choice. If this route choice cannot be accessed due to one of the special causes described below, the LCR function selects the next carrier according to the LCR analysis.

##### Causes which force the PNR to perform alternative routing

- Busy route

- All trunks included in the route are occupied or blocked.

- Travelling Class Mark (TCM) mismatch

- The TCM value of the originator is lower than that requested from the route.

- Network failures

- Network failures will normally be detected after seizure of a route and call set-up will be released by the network, before any alerting or before connection to the desired party can be established.
- The following network problems will be detected:

- (2) No route to specific network
- (3) No route to destination
- (21) Call rejected
- (27) Destination out of service
- (34) No circuit/channel available
- (38) Network out of order
- (41) Temporary failure
- (42) Switching equipment congestion
- (44) Requested circuit/channel not available
- (47) Resource unavailable, unspecified
- (58) Bearer capability presently not available
- (81) Invalid call reference value
- (82) Identified channel does not exist

- After release of the trunk, a new call set-up will be established automatically. Every call set-up will be logged in a CIL record.
- Before the alternative routing is performed the internal originator ( not valid for transit calls ) is informed ( programmable ) about the alternative selection by a special ‘Expensive route warning tone‘. This is especially useful, if the system tries to set up a VPN connection towards the public net. The alternative routing is delayed for about 4seconds and during this time the ‘Expensive route warning tone‘ is sent to the user, who can decide whether or not to continue the call set up or not.

#### Operation

This PNR facility can be accessed by:

- the user dialling the private network access code
- a dialled-in number from the public network, i.e. continues as gateway call

#### Limitations

- A re-routed call from another router, e.g. LCR (routing from PNR back to LCR is not allowed due to the fact that it is not logical and in order to avoid possible looping).

#### Capacity

A maximum of 1000; 1-4 digit private network access codes can be defined

### System feature – Number conversion

#### Definition

The entries in the PNR (the private network access code, PNAC) contain partial CN-number as well as complete CN-number with 1-4 digits, which will be used to convert the dialled number to the addressed CN node

##### Partial CN-number

A partial CN-number means that only parts of the CN-number such as Location codes and Node ids will be programmed in the PNR. According to the programmed entires, the PNR is able to identify the node, however the caller has to continue dialling in order to reach the desired directory number

In case of CN-calls via the public network, the remaining part (= directory number) of the complete number is sent out transparently without any further conversion. This requires a relation between the corporate network numbering plan (private number plan) and public (ISDN) numbering plans. The last digits of the corporate network number (CN-number) and the partial DDI number of the ISDN numbering plan have to be the same, i.e. the same directory number.

The dialling format is: LOC xxxx -> PDN xxxx

LOC |  | (network) location code (1-4-digit network location)

PDN |  | public destination number (1-16-digit public network number)

xxxx |  | post dialled digits (desired directory number)

Example (see Example of programming the Private Network Router):

850 is programmed as a Private Access Number corresponding to the LOCation code number. The user dials a private network number 850 2xxx. The call will be routed to the public network and must therefore be converted into the corresponding public number 00 46 8 719 2xxx. The number conversion of the LOCation code 850 into the subscriber number 00 46 8 719 is possible, but the postdialled directory number is sent to the network without any translation or check by the system. In both numbering plans, private and public, the directory number part therefore must be the same 2xxx in order to reach the same destination.

##### Complete CN-number

If the private network access code covers the complete private number, the called destination (end extension) can be reached without suffix dialling.

It is not recommended to program only complete CN-numbers in the PNR, in order to avoid capacity problems.

There are however, restrictions:

- The complete private number must be a 1-4-digit internal directory number
- The complete public number conversion is limited to 16 digits

The dialling format is: xxxx -> PDN

xxxx |  | complete private number (1-4 digit private network number)

PDN |  | public destination number (1-16 digit public network number)

Example (see Example of programming the Private Network Router):

3102 is a complete private network number and has been programmed as Private Network Access number. The user dials the private number 3102 which will be routed e.g. to the public network and must therefore be converted into the corresponding public number 18113102. A complete number translation is possible and by this even the least significant digits can be converted.

### System feature – Basic call

Basic Call is used for circuit mode switched calls like voice, video or data.

Three types of logical ISDN network accesses are possible:

- public ISDN: non-corporate network access via the public network
- private QSIG: corporate network access via the private network
- private VPN: corporate network access via the public network

In conjunction with basic call control, the following network features and services are possible:

- Calling line category: QSIG and proprietary
- Transit counter: QSIG and proprietary
- Travelling class mark: proprietary

#### Basic call service – Calling line category

Calling line category functionality is used to indicate the category of the calling/connected party involved in the call to another PBX in the corporate network.

Calling line category translation between different signalling types:

ASB 150 02 users | Proprietary services (ASB 501) | QSIG standard (other-vendor PBX)
Digital extension | Digital extension | Extension
Analog extension | Analog extension | Extension
– | Terminal (Data extension) | –
Operator | Operator | Operator
Trunk line | Trunk line | Unknown
Tie line | Tie line | Unknown
– | Emergency Extension | Emergency extension
ISDN Extension | ISDN Extension | Unknown
Cordless Extension | Cordless Extension | Extension
Other facility | – | Unknown

#### Basic call service – Transit counter

Transit counter functionality limits the number of points in the corporate network through which a call can be routed in order to avoid uncontrolled looping in the network.

#### Basic call service – Travelling Class Mark (TCM)

The TCM feature makes possible to control and restrict the call originator (user) of routing in private networks. Each originator (e.g. extensions, operators, incoming trunks) is assigned a ‘facility restriction level’ category which is passed through the network as TCM value. In addition, each route choice defined for a given destination in the network is also assigned a TCM value. By comparing TCM levels for call originator and chosen route, it is decided whether a call setup can continue or be rerouted/rejected.

To allow continued call setup, the TCM value for the call originator must be higher or equal in comparision to the chosen route.

Assignment of TCM category: TCM category must be introduced for all calling originating call parties in the system.

Each of the defined route(s) for a certain ‘private network access code’ will have a TCM category between 0 and 7. TCM category not programmed means ‘no routing restriction, calls may always pass through‘

### Supplementary service – Calling/Connected Line/Name Identity

#### Definition

This feature is available as supplementary and proprietary service for private network calls.

It includes:

- CLIP (Calling Line Identity Presentation)
- CLIR (Calling/Connected Line Identity Restr.)
- COLP (COnnected Line identity Presentation)
- CNIP (Calling Name Identity Presentation)
- CNIR (Calling/Connected Name Identity Restr.)
- CONP (COnnected Name Identity Presentation)

The maximum length of numbers in the private numbering plan is 8 digits and for numbers in the public numbering plan 20 digits.

#### Operation

##### CLIP/CNIP

Calling Line/Name Identity Presentation enables the called party to identify the calling party.

If the display is too small to display both, the full number and the full name, the number always takes priority over the name. Therefore the name will be truncated. The maximum number of characters for a Name is 20.

##### CLIR/CNIR

Calling Line/Name Identity Restriction enables the calling party to prevent the presentation of its number/name to the called party.

##### System telephones

There are two alternatives for outgoing calls to restrict the caller’s number/name at the called party (number/name secrecy).

##### Permanent mode

The extension is configured to always restrict presentation of the caller’s number/name. At call setup, CLIR / CNIR is included.

##### Temporary mode

A „number/name secrecy“ key can be programmed at system telephones, and the user himself/herself may decide whether or not to restrict the caller‘s number/name at the called party.

This key is at the same time used for the COLR/CONR function described in the following chapter. For caller’s number/name restriction at the called party, the key „number/name secrecy“ has to be activated before call setup. Restriction is activated until the key is pressed again.

##### LED-status of the key “number/name secrecy”

- Extinguished: Caller’s number/name can be presented to the called party.
- Steady light: Caller’s number/name is restricted to the called party.

Independent of which mode – temporary or permanent – is activated, a subscribed COLR/CONR function (see COLR/CONR) will be affected.

##### COLP/CONP

COnnected Line/Name identity Presentation enables the calling party to receive identification of the connected party.

If the display is too small to display both,the full number and the full name, the number always takes priority over the name. Therefore the name will be truncated.

##### COLR/CONR

COnnected Line/Name identity Restriction enables the connected party to prevent presentation of its number/name by using the “number secrecy” key.

The display shows an incoming call, where the caller has activated COLR/CONR:

#### Transfer of calling/connected party number through the network

For the transfer of the calling/connected numbers we distinguish between following traffic cases:

- CN-originated and CN-terminated calls
- CN-originated and non CN-terminated call *)
- Non CN-originated and CN-terminated call *)
- Non CN-originated and non CN-terminated *)

*)
For these traffic cases at least one conversation partner is located outside the CN network, and therefore the behaviour of calling/connected number transfer is dependent on the setting of the trunk command 1038 in the gateway node.

1038 |  | Forward CLI/COL

This command defines whether or not the received calling/connected number is to be forwarded in case of transit/gateway or external diverted calls.

##### CN-originated and CN-terminated calls

For CN originated and CN terminated calls the private calling/connected party numbers will always be transferred transparently through the network. The transfer is independent whether the network is based on proprietary or non proprietary nodes. Depending on the location of the calling/connected party (in the same or on a different regional level) the private number will be modified (e.g. prefixed with the Location Code in case of different regional levels) in order to present a correct calling/connected number for both conversation partners.

##### CN-originated and non CN-terminated calls

- Proprietary network
  Within a proprietary network the private and the public numbers of the caller will always be transferred through the network.
  In case of a break out to the public network, it depends on the settings of command 1038 in the gateway node whether the public calling number of the caller or the public calling number of the gateway node will be sent to the called party.
  If the called party answers the call, the connected number (if provided and subscribed) will be modified in the gateway node to a dialable number for the originator
  (e.g. prefixed with the country code, if the gateway and the originator’s node are located in different countries) before it is sent to the caller.
- Non-proprietary network
  Within a non proprietary network only the private number of the caller will be sent through the network. In case of a break out, only the public calling number of the gateway node will be sent to the called party. If the called party answers the call, the connected number (if provided and subscribed) will be modified in the gateway node to a dialable number for the originator, before it is sent to the caller.

##### Non CN-originated and CN-terminated call

In case of an incoming external call to a proprietary or non-proprietary network, the gateway node takes the responsibility to modify the calling number
(if provided and subscribed) to a dialable number for the terminating destination (e.g. prefixed with the country code, if the gateway and the terminator‘s node are located in different countries) before it is sent transparently through the network. According to the received TON of the calling number, the terminating node includes prefixes (see command 1936,1937) before it is displayed to the caller or stored in the ISDN caller list.

- Proprietary network
  If the CN extension answers the call, it depends on the settings of command 1038 in the gateway node whether the public number of the gateway node or the public number of CN extension will be returned as connected number.
- Non-proprietary network
  If the CN extension answers the call, the public number of the gateway node is returned as connected number.

##### Non CN-originated and non CN-terminated

An incoming call to the network is being diverted to an external destination outside the network.

The entry gateway node is responsible for modifying the calling number to a dialable number for the terminating destination (diverting CN extension node)
before it is sent transparently through the network.
Dependent on the settings of command 1038 in the exit gateway node, either the modified public calling number of the originator is sent to the called party, the public calling number of the exit gateway node or the public calling number of the diverting CN extension. If the external party answers the call, the connected number is modified in the exit gateway exchange to a dialable number for the originator, before it is sent to the entry gateway exchange. However it depends on the settings of command 1038 in the entry gateway whether the modified public number of the connected number or the public number of the entry gateway node is sent as connected number.

The following examples show the calling/connected number modifications and the necessary programming

##### Example 1:
CN-originated and CN-terminated calls

Extension 202 of System A calls Extension 404 in System B.

Settings:

SYSTEM A | command | SYSTEM B
Own location code | 890 | [cmd 5431] | Own location code | 860
PNR number | 860 | [cmd 5432] | PNR number | 890
Destination PBX | proprietary or non proprietary | [cmd 9102] | Destination PBX | proprietary or non proprietary
TON private calling | RL1 | [cmd 9103] | TON private calling | RL1

Calling /Connected line information
CLI2 | 202 | CIL3 | 890202 | CLI4 | 890202
COL2 | 860404 | COL3 | 860404 | COL4 | 404

##### Example 2:
CN originated and non CN terminated call

Extension 202 of System A initiates a break-out in Copenhagen, in order to call a local number

Settings:

SYSTEM A | command | SYSTEM B
Own country code | 43 | [cmd 2236] | Own country code | 45
Own area code | 1 | [cmd 2237] | Own area code | 5
Own subscriber no. | 181100-NAT *) | [cmd 2220] | Own subscriber no. | 592200-NAT *)
Own location code | 890 | [cmd 5431] | Own location code | 860
PNR number | 860 | [cmd 5432] | PNR number | 890
Destination PBX | case 1,2 :proprietary case 3: non proprietary | [cmd 9102] | Destination PBX | case 1,2 :proprietary case 3: non proprietary
TON private calling | RL1 | [cmd 9103] | TON private calling | RL1
TON public calling | international | [cmd 9105] | TON public calling | international
Int. prefix to be included | 00 **) | [cmd 1936] | Int. prefix to be included | 009 **)
|  | [cmd 1038] | CLI/COL handling (T-Interface) | case 1,3 : 1 case 2 : 0
|  | [cmd 1801] | Common number at outgoing/incoming traffic (T-Interface) | 0 ( only relevant for case 2 and 3)

*) Q and T interfaces should be in the same public number group, to provide also the public number transfer through the network, see CIL 3

**) has to be set on Q as well as on the T Interface.

Case 1: Proprietary network
The setting of command 1038 on the T-Interface in system B allows CLI/COL forwarding to the public net (value=1)

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI2 | 202 | CIL3 | 890202 | CLI5 | 43181100203 (TON=INT)
|  |  | 43181100203 (TON=INT) |  |
COL2 | 00455123456 | COL3 | 455123456 (TON=INT) | COL5 | 123456 (TON=SUBS)

Case 2: Proprietary network
The setting of Command 1038 on the T-Interface in system B does not allow CLI/COL forwarding to the
public net (value=0)

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI2 | 202 | CIL3 | 890202 | CLI5 | 5922000 (TON=NAT)
|  |  | 43181100203 (TON=INT) |  |
COL2 | 00455123456 | COL3 | 455123456 (TON=INT) | COL5 | 123456 (TON=SUBS)

Case 3: Non proprietary network

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI2 | 202 | CIL3 | 890202 | CLI5 | 5922000 (TON=NAT)
COL2 | 00455123456 | COL3 | 455123456 (TON=INT) | COL5 | 123456 (TON=SUBS)

##### Example 3:
Non CN-originated and CN-terminated call

An external caller located in Vienna, calls extension 860404.

Settings:

SYSTEM A | command | SYSTEM B
Own country code | 43 | [cmd 2236] | Own country code | 45
Own area code | 1 | [cmd 2237] | Own area code | 5
Own subscriber no. | 181100-NAT *) | [cmd 2220] | Own subscriber no. | 592200-NAT *)
Own location code | 890 | [cmd 5431] | Own location code | 860
PNR number | 860 | [cmd 5432] | PNR number | 890
Destination PBX | case 1,2 :proprietary case 3: non proprietary | [cmd 9102] | Destination PBX | case 1,2 :proprietary case 3: non proprietary
TON private calling | RL1 | [cmd 9103] | TON private calling | RL1
TON public calling | international | [cmd 9105] | TON public calling | international
Int. prefix to be included | 00 **) | [cmd 1936] | Int. prefix to be included | 009 **)
CLI/COL handling (T-Interface) | case 1,3 : 1 case 2 : 0 | [cmd 1038] |  |
Common number at outgoing/incoming traffic (T-Interface) | 0 ( only relevant for case 2 and 3) | [cmd 1801] |  |

*) Q and T interfaces should be in the same public number group, to provide also the public number transfer through the network, see CIL 3

**) has to be set on Q as well as on the T Interface.

Case 1: Proprietary network
The setting of command 1038 on the T-Interface in system A allows CLI/COL forwarding to the public net (value=1)

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI1 | 15236012 | CIL3 | 4315236012 (TON=INT) | CLI4 | 0094315236012
COL1 | 45592200404 (TON=INT) | COL3 | 860404 | COL4 | 404
|  |  | 45592200404 (TON=INT) |  |

Case 2: Proprietary network
The setting of command 1038 on the T-Interface in system A does not allow CLI/COL forwarding to the
public net (value=0)

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI1 | 15236012 (TON=NAT) | CIL3 | 4315236012 (TON=INT) | CLI4 | 0094315236012
COL1 | 1811000 (TON=NAT) | COL3 | 860404 | COL4 | 404
|  |  | 45592200404 (TON=INT) |  |

Case 3: Non proprietary network

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI1 | 15236012 (TON=NAT) | CIL3 | 4315236012 (TON=INT) | CLI4 | 0094315236012
COL1 | 1811000 (TON=NAT) | COL3 | 860404 | COL4 | 404

##### Example 4:
Non CN-originated and non-CN terminated call

An external caller located in Vienna calls extension 860404.
Extension 404 has activated the individual external diversion to a destination in Copenhagen

Settings:

SYSTEM A | command | SYSTEM B
Own country code | 43 | [cmd 2236] | Own country code | 45
Own area code | 1 | [cmd 2237] | Own area code | 5
Own subscriber no. | 181100-NAT *) | [cmd 2220] | Own subscriber no. | 592200-NAT *)
Own location code | 890 | [cmd 5431] | Own location code | 860
PNR number | 860 | [cmd 5432] | PNR number | 890
Destination PBX | proprietary or non proprietary | [cmd 9102] | Destination PBX | proprietary or non proprietary
TON private calling | RL1 | [cmd 9103] | TON private calling | RL1
TON public calling | international | [cmd 9105] | TON public calling | international
CLI/COL handling (T-Interface) | case 1: 1 case 2: 2 case 3: 0 | [cmd 1038] | CLI/COL handling (T-Interface) | case 1: 1 case 2: 2 case 3: 0

Case 1:
The setting of Command 1038 on the T-Interface in system A and B allows CLI/COL forwarding to the public net (value=1).

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI1 | 15236012 (TON=NAT) | CIL3 | 4315236012 (TON=INT) | CLI5 | 592200404 (TON=NAT)
COL1 | 455123456 (TON=INT) | COL3 | 455123456 (TON=INT) | COL5 | 123456 (TON=SUBS)

Case 2:
The setting of Command 1038 on the T-Interface in system A and B allows CLI/COL forwarding to the public net and supports the CLI/COL forwarding also for external diverted calls (value=2).

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI1 | 15236012 (TON=NAT) | CIL3 | 4315236012 (TON=INT) | CLI5 | 4315236012 (TON=INT)
COL1 | 455123456 (TON=INT) | COL3 | 455123456 (TON=INT) | COL5 | 123456 (TON=SUBS)

Case 3:
The setting of Command 1038 on the T-Interface in system A and B does not allow CLI/COL forwarding to the
public net (value=0).

SYSTEM A |  | SYSTEM B
Calling /Connected line information
CLI1 | 15236012 (TON=NAT) | CIL3 | 4315236012 (TON=INT) | CLI5 | 592200404 (TON=NAT)
COL1 | 1811000 (TON=NAT) | COL3 | 455123456 (TON=INT) | COL5 | 123456 (TON=SUBS)

### Supplementary service – Advice of charge

#### Definition

The QSIG-supplementary service Advice of Charge (AOC) in ASB150 02 provides the user with charging information, received from the public network, for calls that leave the private ISDN and enter the public network.

The charging information is transferred within a private network (QSIG) as cost information by the public gateway. This cost information includes also the national dependent currency units.

For more information regarding AOC, see ISDN Facilities (268/155 34-ASB 150 02 Uen).

#### Operation

##### ASB 150 02 as public gateway PBX

- Public network with ISDN signalling

- AOC is either provided for all calls or requested from the public network on a per call basis from the public-gateway exchange (command 1914, T-interface). AOC can be requested as AOC-D or AOC-E.

- Public network with ‘non-ISDN’ signalling

- Only if call metering is provided (command 1501: Yes) on outgoing BTU_, the gateway PBX sends a positive response to an AOC request which is received from the private network.
- The conversion from pulse to costs is always done in the gateway PBX.

##### ASB 150 02 as transit node

An AOC request received in a ASB 150 02 is transferred through transparently.

##### ASB 150 02 as end node

An AOC request, received in a terminating exchange within the private network, is rejected with the value ‘Free of Charge’.

##### Interaction with other features

- Transfer, call extending

- If the transferred-to party resides outside ASB 150 02 but within the private network, the transferred-to party will not have the AOC feature active.

- External call diversion

- The cost of an externaly diverted private network call is booked to the diverting extension in the public gateway exchange and is sent to the call originator for display purposes in the private network.

#### Limitation

S-terminals are not provided with the AOC information from the private network.

The charging information received from public net, is forwarded as cost (cost amount and currency) from the public gateway ASB 150 02 to the originating exchange in the private network. Only interim charging should be requested (programmed) in the originating exchange because the received AOC-information from the private network is only used for display purposes (the extension’s display is updated only during call). The received costs can not be read out by the CM function and are not applicable in the CIL function.

The charging is only stated in the CIL record of the gateway exchange.

### Supplementary service – User-to-User Signalling

#### Definition

In ASB 150 02, the request of the ISDN supplementary service UUS is supported at the T‑interface. At the Q‑interface it is used as a proprietary service.

The UUS supplementary service enables a user (A user within a CN can be a subscriber and/or a PBX in this context a PBX is meant) to send/receive a limited amount of information to/from another user via the signalling (D) channel in association with a call to the other user. This information is passed transparently through the network.

#### Use

The UUS supplementary service is used to transfer proprietary UUI (=User-to-User Information), according to the ASB 501 unique protocol via the public ISDN (VPN) or via a private QSIG network, to support additional CN (=Corporate Network) features and services between ASB 150 02 and
ASB 150 02 / ASB 501.

UUS will not be used at non-proprietary CN calls (=Call between CN users, where no proprietary services are supported).

#### Operation

There are three different UUS supplementary services:

- Service 1: User-to-User Information (UUI) can be sent and received during the setup and clearing phase of a call within call control messages.
- Service 2: User-to-User Information (UUI) can be sent and received during the alerting phase of a call within USER INFORMATION messages.
- Service 3: User-to-User Information (UUI) can be sent and received during the active phase of a call within USER INFORMATION messages.

For a proprietary call, UUS 1 must always be subscribed. The availability of UUS 2 and/or UUS 3 increases the number and functionality of services that can be offered.

#### Limitations

The UUS signalling is an ISDN supplementary service, which will also be used between ASB 150 02 and ASB 501 CN nodes as a proprietary service, although it is not defined by the QSIG standard.

This means that at the Q-reference point with leased lines between the private network nodes, the proprietary services UUS 1, 2, 3 will only be supported as far there is no equipment in between (e.g. a IP Gateway or a Router) which only supports the QSIG Standard.

In this specific case the Q-reference has to be programmed in that way (command 1949), that the the UUS Information elements (according to the ISDN Standard) are mapped to the Manufactur Specific Information elements (according to Q-SIG Standard and based on the GFP).

At the T-reference point, the support of UUS 1, 2, 3, which is dependent on the public ISDN, impacts availability of the proprietary CN services mentioned on the next page.

The following table shows support of UUS 1, 2, 3 in European markets (according to information by network operators, in 1998):

Country (Sheet 1 of 2) | UUS1 | UUS2 | UUS3
Albania |  |  |
Austria | X |  | X
Belgium | X | X | X
Bulgaria |  |  |
Croatia |  |  |
Cyprus | X | X | X
Czech Republic |  |  |
Denmark | X |  | X
Estonia |  |  |
Finland | X | X | X
France | X | X | X
Germany | X | X | X
Greece | X |  |
Hungary |  |  |
Iceland |  |  |
Ireland | X | X | X
Italia | X |  |
Latvia |  |  |
Lithuania |  |  |
Luxembourg | X | X | X
Macedonia |  |  |
Netherlands | X | X | X
Norway | X |  | X
Poland |  |  |
Portugal | X | X | X
Romania |  |  |
Slovak Republic |  |  |
Slovenia |  |  |
Spain | X | X | X
Sweden | X |  |
Switzerland | X |  |
Turkey |  |  |
United Kingdom | X | X | X

The UUS availability shown before, should be used as a first reference only – with ongoing privatisation and other impacts on different markets, the actual information on the supported UUS services should always be obtained from the local network operator.

### Needed UUS services for proprietary CN features

Feature | UUS1 | UUS1 | UUS2 | UUS3
Alerting message | with | w/out |  |
Account number |  | X |  |
Call back on busy | version 1 |  | X | X |
version 2 |  | X |  |
Call back on free | version 1 | X |  | X |
version 2 | X |  |  |
Camp on | X |  |  |
Day/night service | X |  |  |
Call forwarding | Diversion direct | X |  |  |
Diversion on busy | X |  |  |
Diversion on no reply |  | X | X |
Follow me | X |  |  |
Bypass diversion |  | X |  |
Intrusion | L | X | L | X
Message waiting indication |  | X |  |
Number and name transfer | L | X | L | L
Transfer/extending | before answer |  | X | L |
after answer |  | X |  | X
Rerouting | X |  | X |
Transit counter |  | X |  |
Travelling class mark |  | X |  |

Agenda:

X |  | service is required to use the CN feature

L |  | if service is not provided: CN feature is available with limitations

Note

If a feature works with “service 1 (without Alerting message)”, the feature is – of course – also automatically available with “service 1 (with Alerting message)”.

### Proprietary service – Account number

#### Definition

The proprietary service Account Code is based on the internal ASB 150 02 feature “Account code”, see Account Number (103/155 34-ASB 150 02 Uen).

#### Operation

##### Outgoing call via private network

It is possible but it is never mandatory to dial an Account Code to access a certain private trunk. If the call is a CN call, it is not checked whether the dialling of an Account number is required (no matter which trunk is accessed and no matter which Account number ACOS the trunk belongs to).

If it is a call to a proprietary PBX after an Account number was dialled and UUS service 1 is subscribed, the Account number will be sent to the private network.

The Account number is stored in the CIL-record.

##### Incoming and calls via private network

The Account number is stored in the CIL record.

##### Interaction with other features

Since it is never checked if an Account number is required when the call is a private network call, the features ‘Last Number Redial’, ‘CN Call Back’ and ‘CN Diversion’ (outgoing calls without manual dialling by the user) are not affected by the Account number feature.

#### Limitation

If ASB 150 02 acts as a stand alone system, the Account code can be inserted before the external number is dialled.

If ASB 150 02 acts as network node the Account can only be inserted before the external number is dialled.

### Proprietary service – Call Transfer

#### Definition

The existing “Call Transfer” (for detailed information regarding the function, see Facility Description Transfer, 485/155 34-ASB 150 02 Uen) has been modified to the network functionality to display the correct Calling/Connected Line/Name Indentity of the involved CN parties.

#### Operation

Since signalling during the alerting and active phase is required (sending of new number and name), UUS services 2 and 3 must be activated so that the proprietary CN Call Transfer can work with a full display support.

If one involved party cannot use UUS (e.g.: a user from the public ISDN), the Call Transfer is nevertheless carried out but this party is not provided with the new private number or name. That means it is possible to transfer all internal and external calls (private or public), but only external users in the private network who can use UUS 2 and/or UUS 3 are provided with the new private number and name by using the proprietary UUS protocol.

#### Example 1

Both connections before Call Transfer (A <-> B and C <-> B) are Regional calls (TON of Calling/Connected numbers = RL1). The new connected numbers, which are sent from the transferring exchange to the new originating and the new terminating exchange after CT, have the correct prefix for display presentation at the new originator/terminator.

##### Before Call Transfer

##### After Call Transfer

As the TONs of the received ‘new’ connected numbers are equal to the TONs of the already stored COL numbers, no further number conversion is required.

#### Example 2

One connection before Call Transfer (A <-> B) is a Regional call (TON of Calling/Connected numbers = RL1), the other connection before Call Transfer (B <-> C) is a Local Call (TON of Calling/Connected numbers = RL0).

##### Before Call Transfer

##### After Call Transfer

The TONs of the received new connected number in the new originating exchange A and the new terminating exchange C differs from the TON of the stored Calling/Connected number. This indicates that the received numbers are not correctly prefixed for display presentation. The new originator sends his/her own number with correct prefix to the new terminator, and the new terminator sends his/her own number with correct prefix to the new originator.

### Proprietary service – Centralised Operator

#### Definition

In a stand-alone system all incoming external calls which can not be answered, due to the fact that the desired destination is busy, does not answer, is blocked or not configured, will be routed to the operator position.

This function also exists in a private network and is called Centralised Operator (COP). All systems covered by the private network are configured to reroute an unsuccessful incoming external call to a defined COP position.

The COP can be located in any proprietary PBX in the private network, with the purpose to serve all network users in the same way as users in the own dedicated PBX.

#### Use

The aim of the Centralised Operator is to provide the internal operator features to all users in the private network, independent of whether the Centralised Operator is located in the own PBX or in any other proprietary PBX in the private network.

In a private network Centralised Operators are used especially for these kind of configurations where you have small systems included, which do not have a dedicated operator of their own.

#### Operation

The Operator functionality in a private network is built up via public ISDN (VPN: Virtual Private Network) and/or via leased lines using QSIG with proprietary signalling.

The following COP-features are supported:

- Bypass call forwarding
- Supervision of busy with recall at free (similar to the Call Back on busy function) *)
- Camp on *)
- Intrusion with forced release *)
- Night Service Notification (only supported when COP is located in ASB 501) see also Proprietary service – Rerouting.
- Recall at No Answer *)
- State Presentation
- Transfer

*) The features are supported by ASB 150 02 R11 or higher system releases.

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

For more information regarding Operator functionality and especially on the difference between internal and network behavior, see Operator (380/155 34-ASB 150 02 Uen).

#### Capacity

Apart from the maximum number of three operators which can be located in ASB 150 02, there is no limitation to the number of COPs in a private network. The number of required COPs is dependent on the complexity of the whole network e.g networks which are operating over several countries will most likely have a COP in each country.

#### Limitation

The behavior of some of the COP features differs from that of the internal operator functionality.

These functions are:

- The manual ringing function by using the right ’Speech’ button is not available for CN calls. The desired CN destination will be called immediately after all digits have been dialled.
- At calls to a busy CN destination, the identity of the C-party is not available in the calling PBX and cannot be displayed by pressing the ’info’ button.
- In case of serial calls, the COP will not be provided with the identity of the previously transfered CN destination. Only the trunk number (of the outgoing trunk) is available for display presentation.
- By using operator supervised calls it is not possible to register the costs to the CN caller’s individual call meter. To have nevertheless the possibillity to register the call to the calling party in the private network, the operator can register the call to a specified account code which is associated to the calling number.

Compared to the COP functions in ASB 501 following function is not supported in ASB 150 02:

- Night Service Notification (active)

### Proprietary service – Camp on

#### Definition

The proprietary service Camp on is based on the internal ASB 150 02 feature, see Camp On Internal Calls (148/155 34-ASB 150 02 Uen).

#### Operation

If the desired proprietary CN destination is busy, a CN user can request camp on, by dialling the facility digit defined for camp on or by pressing the appropriate menu key.

Camp on is accepted at the called user, if it permits a camp on request, otherwise the call is released.

### Proprietary service – Called party number transfer via UUS1

#### Definition

In some countries it is required that the DDI numbers used for automatic incoming calls to extensions within a PBX are subscribed to the public network. In order to reduce the number of subscriptions as well as the resulting subscription costs, especially for trunks reserved for CN VPN traffic, it is possible to use the feature “Called party number transfer via UUS1”.

#### Use

When using this feature, only one number – the national significant number to reach the PBX – has to be subscribed to the public network. The DDI numbers for reaching extensions within the system will be sent as embedded proprietary information between the CN PBXs.

#### Operation

In order to send the DDI numbers as proprietary information, the called CN party number sent between the PBXs has to be split into two parts:

- The most significant part of the number (national destination code + subscriber number without extension number) will be sent in the call set-up message as called party number IE. This number is used to reach the destination PBX.
- The least significant part of the number (B-party’s extension number part) will be sent as a proprietary called number IE in the UUI between the CN PBXs in the network. To be able to transfer the information, the UUS 1 service is required.

Due to the fact that the extension numbers are embedded as proprietary UUI in the call set-up message, they are not transparent to the public network and do not have to be subscribed.

Furthermore, the called number’s digits in the UUI can be more than only a ‘B-party extension number’; thus a call may continue as gateway/ call set- up to another network after the CN PBX which was first addressed has been reached.

At incoming proprietary CN calls, the called number received from the UUI will be treated as “extended” number part of the received information of the called party number IE. On the trunk line used both types of digits will be combined and stored for further number analysis in order to continue with an internal call set-up or in case of a gateway/ call to set-up a new CN call.

To guarantee the feature functionality, both calling and called PBX must support the feature.

- A continued gateway/ call set-up may further use this feature or continue as an ordinary call set-up, depending on the parameter settings at the outgoing side (PNR) and the interworking network.

- Both T and Q reference points, where the UUS1 service is available, can be used to carry the related information.

- Which of the dialled digits will be sent as called party number IE and/or as proprietary called number IE in the UUI will be defined in the PNR for each route choice by the number length control parameters. (Complete called party number length and Subscriber called party number length).

### Proprietary service – Intrusion

#### Definition

The feature CN ’Intrusion’ is based on the internal ASB 150 02 feature, see Intrusion (267/155 34-ASB 150 02 Uen).

#### Operation

If the desired proprietary CN destination is busy, a CN user can request intrusion, by dialling the facility digit defined for Intrusion or by pressing the appropriate soft key.

Intrusion is accepted at the called user, if it permits an intrusion request, otherwise the call is released.

#### Limitation

The operator is always allowed to initiate intrusion on a CN destination while the extension needs to have a separate permission (command 0182).

### Proprietary service – Message waiting indication

#### Definition

The feature CN ’Message waiting indication’ is based on the existing ’External voice mailbox’ feature, (see Voice Mailbox, External, 521/155 34-ASB 150 02 Uen) with the difference that the external voicemail system is not connect to one’s own system, it is connected to an ASB 501 node in the corporate network.

The usage of a centralised voice mailbox is based on the proprietary CN services line identification and call diversion.

#### Operation

Within a coporate network, the ASB 150 02 user is notified of a waiting message (as far as UUS1 is available) on the programmed ‘external voice message key’ and he/she can initiate a call to the mailbox by pressing the key.

#### Capacity

It is possible to use the ‘message waiting indication’ feature for just one external voice mailbox system which is connected to an CN ASB 501 node.

### Proprietary service – Rerouting

#### Definition

The CN rerouting feature offers the possibility for an ASB 150 02 system to reroute external calls preferably to one of three possible centralised answer positions located in another CN PBX in the private network.

The reason for CN rerouting can be that the CN PBX of one‘s own, is in night switched mode and/or does not have any position to serve rerouted calls (e.g. the PBX is too small to have a dedicated operator of its own).

The centralised answer position can be:

- any extension in another CN PBX
- a COP in an ASB 150 02 system
- a COP in an ASB 501 system

#### Use

The CN rerouting functionality is applicable for all ASB 150 02 systems in the network, independent of whether they act as:

- gateway CN PBX
- transit CN PBX
- terminating CN PBX

#### Operation

Routing principle

The external incoming trunk re-directs a call in accordance with its reroute conditions (no reply, busy, not available, vacant, etc..) and referenced central answer position(s). The information about the involved parties - calling, called and rerouted- to-party identities is carried in the network during the whole CN rerouting event between the concerned CN PBXs.

Not the terminating CN PBX but ASB 150 02 systems acting as a gateway will always take care of CN rerouting, in order to archive the best possible route.

For calls originated within the private network no rerouting will ever be performed so that it will not interfere with other CN features e.g. Call-Back. This rule is independent of the command 2084 (describing whether CN calls shall be treated as internal or external calls).

CN rerouting attempts to the three possible centralised answer positions take place according to a defined priority.

1. Local reroute position day,
   according to command 1103.
2. 1st CN reroute choice,
   according to command 1110.
3. 2nd CN reroute choice,
   according to command 1111.
4. 3rd CN reroute choice,
   according to command 1112.
5. Local reroute position night,
   according to command 1104.

The criteria for selection is relying on the day/night switched status of each choice.

An ASB 501 COP PBX informs, the whole network periodically about its day/night switched status (central operator present/absent). According to the received status of the COP, the ASB 150 02 system marks the CN reroute choice refering to the notifying COP as valid or invalid choice. Once marked invalid, the next CN reroute choice according to the priority will automatically be chosen.

The day/night status notification functionality is neither supported by an ASB 150 02 COP system nor by any other system offering a centralised answer position. The ASB 150 02 systems in the whole network will therefore mark these kinds of CN reroute choices always as valid.

#### Capacity

Up to three CN reroute positions can be defined per system.

#### Limitation

Only one performed CN rerouting is permitted per call in order to avoid possible ‘call loops’.

The programmed central answer position must be defined by a complete unique private network number if located in another CN PBX.

### Dependency of Facilities on Internal/External Handling of Private Network Calls

(see command 2084)

Feature (Sheet 1 of 4) | No influence or not applicable for network calls | CN call will be handled like a normal external call (as originally defined) | Programmable via system command (internal or external handling) | Separate CN feature | Comments
Abbreviated number dialling – common numbers | X |  |  |  |
Abbreviated number dialling – individual numbers | X |  |  |  |
Account number | X |  |  |  |
ACD-incoming call when all agents are logged out | X | X |  |  |
Alarm function | X |  |  |  |
Answer position for trunks | X |  |  |  |
Authorisation code | X |  |  |  |
Automated Attendant | X |  |  |  |
Automatic call back – busy / free extension |  |  |  | X |
Automatic callback - trunk / route | X |  |  |  |
Background music | X |  |  |  |
Bypass call diversion & follow- me |  |  |  | X |
Call-information logging (CIL) function |  |  |  |  | CIL3 to log network calls
Call Metering |  | X |  |  |
Call pick-up - common | X |  |  |  |
Call pick-up - extension group | X |  |  |  |
Call waiting indication | X |  |  |  |
Camp on - incoming external traffic |  | X |  |  |
Camp on - internal calls |  |  |  | X |
Categorisation | X |  |  |  |
Clock and diary | X |  |  |  |
Common Bell | X |  |  |  |
Computer Telephony Integration | X |  |  |  | adaptation to eight digit dir. numbers
Computer Telephony Integration for Automated Attendant | X |  |  |  |
Conference |  |  | X |  |
Connection state message | X |  |  |  |
Delayed automatic answer |  | X |  |  |
Desktop Manager | X |  |  |  |
DISA with password control | X |  |  |  |
Diversion direct |  |  |  | X |
Diversion on busy |  |  |  | X |
Diversion on no reply |  |  |  | X |
Doorphone | X |  |  |  |
External line key | X |  |  |  |
Fault indication | X |  |  |  |
Fictive number | X |  |  |  |
Follow me |  |  |  | X |
Hot line | X |  |  |  |
Hotel: -checked out guests -DID blocking |  | X |  |  |
Immediate answer |  |  | X |  |
Inc. calls via line 1 or line 2 | X |  |  |  |
Incoming external calls | X |  |  |  |
Information |  | X |  |  |
Inquiry | X |  |  |  |
Integrated Cordless | X |  |  |  |
Intercom | X |  |  |  |
Intrusion |  |  |  | X |
ISDN caller list | X |  |  |  |
ISDN facilities | X |  |  |  |
Key system function | X |  |  |  |
Last external number redial | X |  |  |  |
Least cost routing | X |  |  |  |
Loudspeaker paging | X |  |  |  |
Mailbox system - procedure for storing |  | X |  |  |
Message system | X |  |  |  |
Operator - Metering call | X |  |  |  |
Music-on-hold | X |  |  |  |
Name selection | X |  |  |  |
Night service | X |  |  |  |
Operator |  |  |  | X |
Outgoing external calls | X |  |  |  |
Paging |  | X |  |  |
Parking for common access | X |  |  |  |
Private trunk line | X |  |  |  |
Recall following parking, camp on and transfer before answer |  |  | X |  |
Refer-back | X |  |  |  |
Reminder service | X |  |  |  |
Ring signals |  |  | X |  |
Route selection | X |  |  |  |
Saved external number redial |  |  | X |  |
Secretary function | X |  |  |  |
Operator - Serial call | X |  |  |  |
Subsystem | X |  |  |  |
Supervision | X |  |  |  |
Tandem configuration | X |  |  |  |
Telephone directory |  |  |  |  | PNR numbers are stored in internal directory
Tenant function | X |  |  |  |
Traffic group matrix | X |  |  |  |
Transfer | X |  |  |  |
Trunk (rerouting) |  |  |  | X |
Trunk call discrimination | X |  |  |  |
Voice message before answering |  | X |  |  |

## Capacity/Limitations

On system telephones with a small display it is not possible to show the full (8-digit) private network number and the presently shown textual information. In such cases, always the text, not the number, is truncated.

The following scenarios apply depending on the type of the text shown on the display:

- If the text is a calling/called user name, the name is truncated.
- If the text is a system message to the ASB 150 02 user, the message is truncated.

## Programming

The following commands are only accessable via BMS:

### Q/T Link settings

1910 |  | Interface type

1911 |  | Network signalling protocol

1912 |  | Termination in ASB 150

1947 |  | Handling of call collisions

1913 |  | B-channel selection mode

1914 |  | Charging method

1915 |  | Provision of calling line identification

1916 |  | Overlap receiving of called party number

1917 |  | MCID activation request allowed

1918 |  | Provision of connected line identification

1919 |  | Assigned TEI value

1920 |  | CRC4 check

1921 |  | Ignore inband info at disconnection

1922 |  | Through connection after SETUP to net?

1930 |  | Pre-digit removal for private plan with unknown typ of number

1931 |  | Pre-digit removal for private plan with Level 1 regional type of number

1932 |  | Pre-digit removal for private plan with Level 2 regional type of number

1933 |  | Pre-digit removal for private plan with Level 3 regional type of number

1934 |  | Pre-digit removal for private plan with PTN specific type of number

1935 |  | Pre-digit removal for private plan with local type of number

2061 |  | First priority link for synchronisation

2062 |  | Second priority link for synchronisation

2063 |  | Third priority link for synchronisation

2064 |  | Fourth priority link for synchronisation

2065 |  | Fifth priority link for synchronisation

### General settings

2084 |  | Type of network call handling

2085 |  | PBX protocol identifier

### Programming of the “Own location code”

5431 |  | Create Own Location Code

5531 |  | Delete Own Location Code

5631 |  | Alter own location code

### Programming of the Private Network Router (PNR)

5432 |  | Create Private Network Access Code

5532 |  | Delete Private Network Access Code

5632 |  | Change of Private Network Access Code

9101 |  | Destination PBX

9102 |  | Call back allowed?

9103 |  | NPI for private calling/connected line identification

9104 |  | Call class

See also document Facility Description – National Specific Functions (363/155 34-ASB 150 02 Uen).

9105 |  | NPI for public calling/connected line identification

9110 |  | 1st-route choice

9111 |  | NPI for private/public called number 1

9112 |  | Remove digits choice 1

9113 |  | Predigits choice 1

9114 |  | Travelling Class Mark 1

9115 |  | Complete called party NL 1

9116 |  | Subscriber called party NL 1

9117 |  | Node reference 1

- (not relevant for circuit switched lines)

9120 |  | 2nd-route choice

9121 |  | NPI for private/public called number 2

9122 |  | Remove digits choice 2

9123 |  | Predigits choice 2

9124 |  | Travelling Class Mark 2

9125 |  | Complete called party NL 2

9126 |  | Subscriber called party NL 2

9127 |  | Node reference 2

- (not relevant for circuit switched lines)

9128 |  | Send expensive route warning tone 2

9130 |  | 3-rd route choice

9131 |  | NPI for private/public called number 3

9132 |  | Remove digits choice 3

9133 |  | Predigits choice 3

9134 |  | Travelling Class Mark 3

9135 |  | Complete called party NL 3

9136 |  | Subscriber called party NL 3

9137 |  | Node reference 3

- (not relevant for circuit-switched lines)

9138 |  | Send expensive route warning tone 3

9140 |  | 4-th route choice

9141 |  | NPI for private/public called number 4

9142 |  | Remove digits choice 4

9143 |  | Predigits choice 4

9144 |  | Travelling Class Mark 4

9145 |  | Complete called party NL 4

9146 |  | Subscriber called party NL 4

9147 |  | Node reference 4

- (not relevant for circuit-switched lines)

9148 |  | Send expensive route warning tone 4

### PNR alternative Routing

1037 |  | PNR routes at incoming proprietary call

### Basic call service – Travelling Class Mark

0171 |  | Travelling Class Mark

1035 |  | Travelling class mark (TCM)

### Basic call service – Transit counter

2087 |  | Transit counter

### Calling/Connected Line/Name identity

0170 |  | Number/name secrecy to corporate network?

1038 |  | Forward CLI/COL

- (only relevant for the gateway node)

1801 |  | Common number at automatic outgoing/incoming traffic

2220 |  | Public number

2236 |  | Own country code

2237 |  | Own area code

1936 |  | Prefix calling number for E.164 number plan with international type of number

1937 |  | Prefix calling number for E.164 number plan with national type of number

The following commands need to be set if the public exchange transmits leading zeros in the calling/connected number information. Leading unremoved zeros will automatically cause problems, if the gateway exchange has to modify the received number before it is sent to the network. The commands are also necessary if the connected network node transmits more predigits than necessary e.g. the trunk access code.

1960 |  | Predigits to be removed for calling/connected number if TON=Unknown

1961 |  | Predigits to be removed for calling/connected number if TON=International

1962 |  | Predigits to be removed for calling/connected number if TON=National

1963 |  | Predigits to be removed for calling/connected number if TON=Network specific

1964 |  | Predigits to be removed for calling/connected number if TON=Local directory

### Supplementary service UUS

2072 |  | MD110 release version of CN

1940 |  | UUS services activation request

1941 |  | Explicit UUS service 1 activation request

1942 |  | UU-information length for UUS service 1

1943 |  | UU-information in ALERT message

1944 |  | Explicit UUS service 2 activation request

1945 |  | Explicit UUS service 3 activation request

1949 |  | Carrier for proprietary services

### Proprietary service – Call back

0177 |  | Initiate callback in corporate network?

9001 |  | Call setup version at network CBack

9002 |  | Active time for ’CBack on busy’ initPBX

9003 |  | Active time for ’CBack on free’ initPBX

9004 |  | Active time for ’CBack on busy’ superPBX

9005 |  | Active time for ’CBack on free’ superPBX

9006 |  | Maxringtime at the init extension for CBack calls

### Proprietary service – Call diversion

0176 |  | Call diversion to corporate network allowed?

### Proprietary service – Camp on

0108 |  | Camp-on allowed?

### Proprietary service – Intrusion

0182 |  | Network intrusion?

### Proprietary service – Message Waiting Indication

2023 |  | External voice mail directory number

2071 |  | ISID of external voice mailbox

### Proprietary service – Rerouting

1110 |  | 1st, choice CN reroute position

1111 |  | 2nd, choice CN reroute position

1112 |  | 3rd, choice CN reroute position

2077 |  | First central answering position

2078 |  | Second central answering position

2079 |  | Third central answering position

### Extension settings

0187 |  | Expensive Route Warning Tone

### Tone settings

2650 |  | Expensive route warning tone

## Equipment

BTU-B_ or MFU or BTU-D with ISDN PROM set.

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

Revision: D © Ericsson Enterprise 2005