D Channel Signalling

D-Channel Signalling
DN98905095
Issue 7-0
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2011/2/23. All rights reserved
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.
The same text in German:
f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentations-
satzes.
2 DN98905095
Issue 7-0
Table of Contents
This document has 93 pages.
1 Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 D-channel signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 DPNSS1, DSS1 30B+D and 23B+D . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 DSS1 signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 Layer structure of OSI model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.2 LAPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.3 ISDN services of DSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3 DPNSS1 signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.1 Services of DPNSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4 Bearer service types supported by DPNSS1 and DSS1 . . . . . . . . . . . . 17
2.5 Supplementary services for D-channel . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.6 Capacity with D-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Planning D-channel configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4 Configuring the DSS1 30B+D interface . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.1 Creating a semipermanent cross connection in MGW. . . . . . . . . . . . . . 22
4.2 Creating and configuring the exchange terminal (ET) unit(s) . . . . . . . . 22
4.3 Creating and configuring an echo canceller unit (ECU). . . . . . . . . . . . . 23
4.4 Creating an LAPD signalling link and circuit group . . . . . . . . . . . . . . . . 23
4.5 Creating and modifying a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6 Creating digit analysis components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.7 Creating a Call Number and Routing Zone Index based on Circuit Group
24
4.8 Defining services for PBX calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.9 Changing the state of the ET, ECU, link, circuit group, and circuits to WO-
EX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.10 Creating/modifying the End-of-Selection (EOS) analysis for incoming sig-
nalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.11 Example of creating a DSS1 30B+D interface . . . . . . . . . . . . . . . . . . . . 26
5 Configuring the DSS1 23B+D interface . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1 Creating a semipermanent cross connection in MGW. . . . . . . . . . . . . . 30
5.2 Creating and configuring the exchange terminal (ET) unit(s) . . . . . . . . 30
5.3 Creating a 23B+D signalling link and circuit group . . . . . . . . . . . . . . . . 31
5.4 Adding and modifying circuits in a circuit group, adding a charging case .
31
5.5 Creating and modifying a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.6 Creating digit analysis and digit analysis components. . . . . . . . . . . . . . 32
5.7 Creating a Call Number and Routing Zone Index based on Circuit Group
32
5.8 Creating an Extended Preanalysis Result and subanalysis. . . . . . . . . . 33
5.9 Modifying the originating line identifier and the charge number indicator 33
5.10 Defining services for PBX calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.11 Changing the state of the ET, ECU, link, circuit group, and circuits to WO-
EX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DN98905095 Id:0900d80580637e37 3
Issue 7-0
5.12 Creating/modifying the End-of-Selection (EOS) analysis for incoming sig-

nalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.13 Example of creating a DSS1 23B+D interface . . . . . . . . . . . . . . . . . . . . 35
6 Configuring a DPNSS1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6.1 Creating a semipermanent cross connection in MGW . . . . . . . . . . . . . . 39
6.2 Creating and configuring ET unit(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.3 Creating a DPNSS1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.4 Creating a circuit group and adding circuits . . . . . . . . . . . . . . . . . . . . . . 40
6.5 Creating a route and analysis components. . . . . . . . . . . . . . . . . . . . . . . 41
6.6 Creating a digit analysis and a charging component . . . . . . . . . . . . . . . 41
6.7 Creating a Call Number and Routing Zone Index . . . . . . . . . . . . . . . . . . 42
6.8 Defining PBX services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.9 Changing the state of the ET, ECU, link, the circuit group, and the circuits
to WO-EX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.10 Creating and modifying End-of-Selection (EOS) analysis . . . . . . . . . . . 43
6.11 Example of configuring DPNSS1 interface . . . . . . . . . . . . . . . . . . . . . . . 43
7 Controlling the D-channel interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7.1 Checking configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.2 Checking the state of the interface elements . . . . . . . . . . . . . . . . . . . . . 48
7.3 Changing the state of the interface elements and configuration. . . . . . . 53
7.4 Changing the parameters of interface elements . . . . . . . . . . . . . . . . . . . 54
8 Deleting the D-channel interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8.1 Deactivating the links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.2 Deleting digit analysis and digit analysis components . . . . . . . . . . . . . . 59
8.3 Deleting the route and link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.4 Deleting the call number and supplementary services . . . . . . . . . . . . . . 60
8.5 Deleting the circuit group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.6 Example of deleting an interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9 Configuring supplementary services with D-channel signalling . . . . . . . 66

9.1 Configuring Advice of Charge (AOC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.2 Configuring Call Completion to Busy Subscriber (CCBS). . . . . . . . . . . . 70
9.2.1 Configuring CCBS in the HLR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
9.2.2 Activating the CCBS in the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
9.3 Configuring user-to-user signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
9.3.1 Configuring UUS in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.3.2 Configuring UUS in the MSC/VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
9.4 Configuring calling line identification (CLI) . . . . . . . . . . . . . . . . . . . . . . . 76
9.4.1 CLI screening in the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
9.4.2 Configuring CLI screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
9.4.3 Modifying CLI screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
9.4.4 Configuring CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
9.4.5 Configuring CLIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
9.4.6 Configuring CLIR override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9.5 Configuring direct dialling-in (DDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
9.6 Configuring call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.7 Defining tones with D-channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4 Id:0900d80580637e37 DN98905095
Issue 7-0
9.8 Configuring charging based on distance . . . . . . . . . . . . . . . . . . . . . . . . 87
10 Configuring an emergency/service call with D-channel signalling . . . . . 89
11 Configuring IN services with D-channel signalling . . . . . . . . . . . . . . . . . 91
12 Values of the LSI parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
DN98905095 Id:0900d80580637e37 5
Issue 7-0
List of Figures
Figure 1 Successful call/DSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 2 Layering of DSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 3 Layering of DPNSS1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 4 Successful call/DPNSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 5 D-channel configuration diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 6 D-channel configuration diagram when the PBX is connected to the MGW
21
Figure 7 DSS1 30B+D example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 8 DSS1 23B+D example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 9 DPNSS1 example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 10 AOC-E, A releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 11 AOC-E, B releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 12 AOC-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 13 Call completion supplementary services architecture . . . . . . . . . . . . . . 71
Figure 14 Calling Line Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 15 CLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 16 DDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 17 Charging based on distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6 Id:0900d80580637e37 DN98905095
Issue 7-0
List of Tables
Table 1 Summary of the main properties of the three signalling systems . . . . . 11
Table 2 Capacity with D-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 3 Man-Machine Interface for the MS Subscriber . . . . . . . . . . . . . . . . . . . 76
Table 4 CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 5 Possible call forwarding reasons in the call forwarding request and the cor-
responding event code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 6 Call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 7 Additional information on the values of the LSI parameter . . . . . . . . . . 92
DN98905095 Id:0900d80580637e37 7
Issue 7-0
8 Id:0900d80580637e37 DN98905095
Issue 7-0
D-Channel Signalling Summary of changes
1 Summary of changes
Changes made between issues 7-0 and 6-0
Troubleshooting information has been transferred to Troubleshooting DX MSC/MSS/DX
HLR.
Changes made between issues 6-0 and 5-0

The company and product names have been changed according to the official Nokia
Siemens Networks portfolio naming.
Changes made between issues 50 and 40

Information added on the case when PBX is connected to MGW while PBX signalling is
handled in the MSS.
D-channel configuration diagram when the PBX is connected to the MGW added to
Chapter Planning D-channel configuration.
Alternative steps on creating a semipermanent cross connection in MGW and on
creating an EDCS circuit group added to Chapters Configuring the DSS1 30B+D inter-
face, Configuring the DSS1 23B+D interface, and Configuring a DPNSS1 interface.

New values of the LSI parameter were added to section Additional information on the
values of the LSI parameter.

No content changes. The changes made were caused by migration into online environ-
ment.
DN98905095 Id:0900d8058063c1ea 9
Issue 7-0
D-channel signalling D-Channel Signalling
2 D-channel signalling
Use of signalling
Signalling refers to any transfer of data that enables speech and data connections
between users. In the Public Switched Telephone Network (PSTN) signalling is needed
for call establishing, call release, and call maintaining. In the GSM system signalling can
also happen independently of speech. The different functions of signalling are:
call control
control of services
charging control
Mobile networks have some special functions, for example:
location update
handover
subscriber administration
short message service
D-channel
D-channel is a communication channel used for signalling and other message-based
data transmission. Originally, D-channel is one of the channel types defined for the ISDN
user-network interfaces. In addition to D-channel, there is another channel type called
B-channel. B-channel is a 64 kbit/s channel intended to carry a variety of user informa-
tion streams, for example, voice, circuit-, or packet-switching data information.
For further information on D-channels, see D-channels and LAPD protocol.
For further information on D-channels, see D-channel Services, section D-channels and
LAPD protocol.
2.1 DPNSS1, DSS1 30B+D and 23B+D

The signalling systems described here are the Digital Private Network Signalling System
No 1 (DPNSS1) and the Digital Subscriber Signalling System No 1 (DSS1). The latter
includes the physical structures 30B+D, used mainly in Europe, and 23B+D used mainly
in the USA.
The DPNSS1 and DSS1 can be used when a PBX or a PBX network is connected to a
PSTN or a Public Land Mobile Network (PLMN), even though the DPNSS1 was origi-
nally designed to be used within a PBX network. The DSS1 can also be used in creating
a connection to a PSTN or to a PLMN for data access. In this case, the other part is not
a PBX but an ISDN router. Additionally, there are voice mail systems (VMS) supporting
the DSS1.
The primary rate access structure is composed of B-channels and one D-channel. In the
2048 kbit/s primary rate access the interface structure is 30B+D and in the 1544 kbit/s
primary rate access it is 23B+D. The bit rate of the D-channel is 64 kbit/s in the primary
rate accesses. The same interface structure also applies to the D-channels of the
DPNSS1 interface but the D-channel protocol is different.
The DPNSS1 and DSS1 are implemented in the Primary Rate Access Units (PAU) or in
General purpose Signalling Units (GSU). The DPNSS1 and DSS1 are both 2 Mbit/s
accesses that exchange signalling information via a signalling link, which may contain
up to 30 channels in one PCM. In a 2 Mbit/s PCM line there are 30*64 kbit/s channels
10 Id:0900d80580570d29 DN98905095
Issue 7-0
D-Channel Signalling D-channel signalling
for speech or data, the timeslot 16 is reserved for signalling and the TSL 0 for synchro-
nisation. 23B+D is a 1.544 Mbit/s access containing up to 23 channels in one PCM. In
one 1.544 Mbit/s PCM line there are 23*64 kbit/s channels for speech or data, whereas
one channel, the timeslot 24, is reserved for signalling information. Synchronisation is
performed on the frame level.
DPNSS DSS1 30 B+D 23B +D

In PAU or GSU in PAU or GSU in PAU or GSU
2 Mbit access 2 Mbit access 1.544 Mbit access
30 channels per PCM 30 channels per PCM 23 channels per PCM
30 x 64 kbit channels 30 x 64 kbit channels 23 x 64 kbit channels
TSL 16 for signalling TSL 16 for signalling TSL 24 for signalling
TSL 0 for synchronisation TSL 0 for synchronisation Synchronisation per-
formed on frame level
Table 1 Summary of the main properties of the three signalling systems
Connecting a PBX to the network

A PBX is connected to the switching network of the DX 200 exchange with an external
PCM circuit. An Exchange Terminal (ET) connection is established for the external PCM
circuit to that user part which controls the signalling system used by the PBX. These
user parts include, for example, the DPNSS1 and DSS1. In the DSS1 PBX, the PCM
circuits are supervised by the Signalling Services of Primary Access (SI1PRB) and in
the DPNSS, by the DPNSS No 1 Signalling Program Block (DPNPRB).
A connection to the PBX is created by using the routing and digit analysis commands
and specific commands used only when a PBX is created. For information on creating
a DPNSS1, DSS1 23B+D or 30B+D interface between an MSC and a PBX or another
equipment that supports the interface, see Configuring the DSS1 30B+D interface, Con-
figuring the DSS1 23B+D interface and Configuring a DPNSS1 interface on configuring
interfaces.
A digital PBX access is a common channel signalling in the sense that one signalling
link can handle several logical connections. Although the speech channels (B-channels)
used by the connections must reside in the same PCM where the signalling link (D-
channel) is, there can be several PCMs leading to the same PBX.
It is possible to connect the PBX to the MGW while PBX signalling is still handled in the
MSS. The PBX can be connected to the MGW in either of the following ways:
The D-channels are cross-connected in the MGW to the PCM/TSLs which are con-
nected to the MSS. This solution supports both DSS1 and DPNSS1 signalling.
The D-channels are terminated in the MGW and the signalling information is trans-
ferred to the MSS by using the IUA protocol. In this solution only DSS1 signalling is
supported due to that IUA is limited only to DSS1.
When semipermanent cross connection is used to connect the signalling link to the
MSS, the configuration of the interface follows the standard PBX configuration proce-
dure with two exceptions:
A new circuit group (CGR) type is used.
Semipermanent cross connection has to be created before configuration.
DN98905095 Id:0900d80580570d29 11
Issue 7-0
The MGW only terminates the user plane channels (B-channel), the signalling informa-
tion (D-channel) is cross-connected to the MSS. The PBX can also be connected to the
MGW in case of integrated MSS. However, it is not handled as a separate case because
the functionality is the same, and because in case of integrated MSS the PBX can be
connected also to the MSS.
E1 vs. T1 channel structure

The channel structure is different for the DSS1 E1, which is mostly used in Europe, and
DSS1 T1, which is mostly used in the USA. In E1 the ISDN version 30B+D is used,
whereas in the T1 version 23B+D is used. E1 for D-channel is in the timeslot 16 and T1
for D-channel in the timeslot 24. The system is called Primary Rate Access (PRA) in
Europe and Primary Rate Interface (PRI) in the USA. The bit rate is 2048 kbit/s in
Europe and 1544 kbit/s in the USA.
2.2 DSS1 signalling

The Digital Subscriber Signalling No 1 (DSS1) is a D-channel signalling system with a
common signalling channel, used for enabling the access of PBXs to Integrated
Services Digital Network (ISDN) service capabilities. It is also used in, for example:
Local Area Network (LAN) connections
videoconferencing
remote access
The DSS1 is used when it is necessary to connect higher capacities to the ISDN network
than what can be attained by using the Basic Access.
The channel structure for DSS1 signalling is 30B+D for E1, specified by the European
Telecommunication Standards Institute (ETSI), and 23B+D for T1, specified by the
American National Standards Institute (ANSI). According to the DSS1 specification, the
30*64 kbit/s B-channels are used for speech and data and the D-channel (TSL 16) is
used for signalling. One channel is reserved for frame synchronisation (TSL 0). Layer 2
is specified by ITU-T Recommendations, Q.920 and Q.921, and corresponding ETSI
Recommendation - ETS 300 125. Layer 3 is specified in the ITU-T Recommendation
Q.931 and ETS 300 102 and ETS 300 403 for 30B+D and ANSI T1.607 for 23B+D.
According to DSS1 23B+D specification, there are 23*64 kbit/s B-channels for speech
or data, the D-channel, timeslot 24, is reserved for signalling, and synchronisation is per-
formed on the frame level. The interface is defined in ANSI T1.607.
The data link protocol of D-channel is called LAPD. The LAPD contains procedures for
the establishment of a D-channel connection, delivery of signalling messages and the
supervision and release of the connection. The connection has two communicating
entities at both ends of the D-channel, the Network side and the User side.
DSS1 is a protocol which provides the procedures for establishing, maintaining, and
clearing network connections at the ISDN user-network interface. These procedures are
defined in terms of messages exchanged over the D-channel of primary rate interface
structures.
In the 30B+D and 23 B+D interface, the user establishes a D-channel connection with
an MML command, and the connection is maintained until the user deactivates it. No
call-related actions are made as far as the state of the D-channel is concerned.
The following figure illustrates a successful call with the connection from a PBX to an
MSC using the DSS1 signalling system.
12 Id:0900d80580570d29 DN98905095
Issue 7-0
Figure 1 Successful call/DSS1
2.2.1 Layer structure of OSI model

The DSS1 is based on the layered structure of the OSI model. The three lowest layers
of the OSI model are shown below.
Layer 1 requirements for the DSS1:
The layer 1 requirements for the 2.048 Mbit/s Primary Rate Access have been spec-
ified in the ITU-T Recommendation I.431 (Blue Book).
The layer 1 requirements for the 1.544 Mbit/s Primary Rate Access have been spec-
ified in the ANSI T1 408 (1990).
The equipment must extract the synchronisation from the Primary Rate Access.
Layer 1 is always in active state and no activation/deactivation procedures are
required.
Layer 2 requirements:
The practical requirements of layer 2 have been specified in the ITU-T Require-
ments Q.920 and Q.921 (Blue Book).
Layer 2 is always in the 'link connection established' state, and therefore Layer 3
messages are always sent in the I frames.
Layer 2 will only support one connection per one SAPI value, and 0 is given as the
TEI value. The distribution procedures of the TEI values are not in use.
Layer 3 requirements:
The requirements for Layer 3 have been specified in the ITU-T Recommendations
Q.930 and Q.931 (Blue Book). The corresponding ETSI standards, ETS 300 1021
and 300 4031, list the options selected to be used in Europe.
The requirements for Layer 3 in the US have been specified in ANSI T1.607.
The figure below illustrates this structure as well as the computer units in DX 200 in
which the layers 2 and 3 are situated.
DN98905095 Id:0900d80580570d29 13
Issue 7-0
Figure 2 Layering of DSS1
2.2.2 LAPD
The LAPD conveys information between layer 3 entities across the interface using the
D-channel. A single physical link may provide logical channels for several layer 3 enti-
ties. Layer 3 includes the application-specific signalling functions, such as: basic call
control procedures for establishing, maintaining, and clearing of connections, proce-
dures for various supplementary services, user-to-user signalling and maintenance
functions.
The following LAPD features are not required in the 30B+D interface and they are not
implemented in the DX 200 system:
TEI management procedures (TEI value 0 assigned internally)
broadcast data link
The following LAPD features are not supported in the 30B+D interface of the DX 200
system:
packet data with SAPI value 16
For further information on the protocols, see D-channels and LAPD protocol.
For further information on the protocols, see D-channel services.
2.2.3 ISDN services of DSS1

The ISDN services of the DSS1 can be divided into bearer services, teleservices, and
supplementary services.
The bearer services form the three lowest layers of the OSI model (X.200). In the ISDN
subscriber signalling the interface transmits the following bearer service definitions in
accordance with Recommendation I.231, and can route the connection as required by
the definitions:
speech
64 kbit/s, 8 kHz octet structure, unrestricted digital information
64 kbit/s, 8 kHz octet structure, 3.1 kHz audio
14 Id:0900d80580570d29 DN98905095
Issue 7-0
The DSS1 must be capable of transparent transformation of an information element

which indicates the teleservice. A high layer compatibility information element is trans-
ported between terminals and it indicates the teleservice in question.
2.3 DPNSS1 signalling

Digital Private Network Signalling System (DPNSS1) is a common channel signalling
system with a signalling channel called the D-channel. It was primarily intended to be
used between PBXs to build private networks. It can, however, also be used between
MSCs and PBXs to support calls between the following:
PBX subscribers and MS subscribers
PBX subscribers and other PBX subscribers
PBX subscribers and PSTN network subscribers
The DPNSS1 supports simple telephone calls and numerous supplementary services.
The basic principle of the DPNSS1 is the functional distribution between the data link
layer (level 2) common to all services of the DPNSS1, the signalling service, and call
control layers (level 3) containing different services. The physical layer (level 1) contains
the physical transmission system interface between an MSC and PBXs.
The task of the data link layer is to transfer the signalling messages reliably between the
communicating call control parts.
The DPNSS1 level 2 interface offers the common D-channel signalling access to the
physical D-channel, providing error-free sequential transmission for DPNSS 1 level 3
signalling information. Level 2 specifies the structure of the flag-delimited frames and
the format of fields, elements and procedures which include transmission error and form
and function error checking and recovery functions after errors by retransmission of
frames.
The DPNSS1 level 3 interface offers the common D-channel signalling access between
the adjacent MSCs and PBX DPNSS1 levels 3. Level 3 specifies the contents, forms,
and sequences of the call setup and control signalling and notifications of the supple-
mentary services between the MSC and PBXs.
The layered structure is presented below. The same figure shows the computer units in
the DX 200 in which the layers are situated.
DN98905095 Id:0900d80580570d29 15
Issue 7-0
Figure 3 Layering of DPNSS1

The DPNSS1 level 3 controls the simple telephone calls, virtual calls (during some sup-
plementary services), and some supplementary services (call forwarding and call trans-
fer) of the MSC switching node. It performs the necessary control functions of the D-
channel signalling using circuits to PBXs (real and virtual) according to the DPNSS1 sig-
nalling and the internal actions of the exchange. It also supervises the states of the PBX
circuits.
The DPNSS1 signalling system is based on the British Telecommunications Network
Requirement specification document, BTNR 188.
The following figure illustrates a successful call with the connection from a PBX to an
MSC using DPNSS1 signalling system.
Figure 4 Successful call/DPNSS1

Each of the up to 30 traffic channels of the 2048 kbit/s PCM system is supported by a
Link Access Protocol (LAP) on a signalling channel. Frames for each LAP are inter-
leaved on the timeslot 16 of the same PCM. The address field of each frame indicates
the LAP and channel to which the message relates. DPNSS1 also supports virtual
channels in addition to normal traffic channels (referred as Real channels) which is also
indicated in the address field. Each LAP operates independently without explicit interac-
tion. The logical signalling channel of the timeslot 16 is called a D-channel.
16 Id:0900d80580570d29 DN98905095
Issue 7-0
2.3.1 Services of DPNSS1

This section describes the services of the DPNSS1.
Real call signalling services of DPNSS1

The real call signalling services of the DPNSS1 signalling include:
simple telephone call
circuit-switched data call
end function supplementary services
numerous transit function supplementary services, such as:
diversion
hold
three party
night service
overload control for incoming calls
The supplementary services that can be used depend on the other equipment used, not
on the DX 200 MSC. Transit function requires a Private Numbering Plan (PNP) to be
used. It only functions between two exchanges belonging to the same PNP.
Virtual call signalling service with DPNSS1

There is one virtual call signalling service supported by DPNSS1: call diversion valida-
tion.
2.4 Bearer service types supported by DPNSS1 and DSS1

The following bearer services are supported by DPNSS1 and DSS1 interfaces
Single octet SIC indicating 'speech' by DPNSS1
Two octet SIC indicating 'data' by DPNSS1
Circuit-mode - 64 kbit/s unrestricted bearer service by DSS1
Circuit-mode - 64 kbit/s restricted bearer service by DSS1
Circuit-mode - 3.1 kHz audio bearer service by DSS1 Circuit-mode - speech by
DSS1
2.5 Supplementary services for D-channel

The supplementary services are extensions to the basic bearer services and teleser-
vices. They are created for PBX circuit groups. They are supported in the stimulus mode
except for call forwarding. The supplementary services for the D-channel signallings
include:
Direct Dialling In (DDI)
Calling Line Identification Presentation (CLIP)
Calling Line Identification Restriction (CLIR)
Calling Line Identification Screening (CLIS)
Advice of Charge at the End of the Call (AOC-E), not supported by 23B+D, or by
DPNSS1
Closed User Group (CUG), optional, not supported by 23B+D
Call Forwarding (CF), optional in 30B+D, not supported by 23B+D
Private Numbering Plan (PNP), optional, not supported by 23B+D
DN98905095 Id:0900d80580570d29 17
Issue 7-0
Charging based on distance (optional)

Call Completion to Busy Subscriber (CCBS) and Call Completion on No Reply
(CCNR), optional, not supported by 23B+D
User-to-User Signalling (UUS), optional, not supported by 23B+D
For a more detailed description, see Configuring supplementary services with D-
channel signalling.
2.6 Capacity with D-channel

The maximum number of D-channels in a computer varies. The number is limited by the
number of LAPD or DPNSS1 signalling terminals that can be equipped in the unit, as
well as the internal PCM equipment of the unit.
The capacity of each switching centre type is presented in the following table.
MSC Transit MSC Compact MSC

PAUs max 13 + 1* max 32 + 1* -
GSUs - - 2+1
links/unit max 64 max 64 max 64**
PCMs/unit 64 64 max 64
AS7-U - - -
AS7-A 2 (+ 1) 2 (+ 1) max 32 (DPNSS1),
64 (DSS1)
ET1E - - -
ET2E max 32/PAU max 32/PAU max 32/GSU
EC2ET max 32/PAU max 32/PAU max 32/GSU
Table 2 Capacity with D-channel
=not applicable in this case

* = dynamic
**= depends on the configuration
***= recommendation for DPNSS1 is 8
All switching centre types, except for the Compact MSC, use PAU computer units. The
Compact MSC uses GSUs. The maximum amount of links per unit is 64, which also
applies to the PCMs per unit. The MSC uses AS7A and ET2E or EC2ET.
18 Id:0900d80580570d29 DN98905095
Issue 7-0
D-Channel Signalling Planning D-channel configuration
3 Planning D-channel configuration

The planning of the interface is described here with issues that have to be considered
before the configuration. Each signalling type is presented with configuration instruc-
tions and examples.
Planning the interface

The following issues need to be taken into account when planning an interface:
What kind of traffic will be carried in the interface. In typical corporate use, there will
be incoming and outgoing traffic. In such a case, the typical traffic generated by an
extension is about 250 mErl. There are, however, other types of services like
customer service and data access, which are special cases and do not conform to
the normal rules. In these cases, most of the traffic will be terminating.
What will be the amount of traffic. This depends on what kind of traffic (incoming
and/or outgoing) will be carried in the interface. The number of extensions must also
be taken into account. The load of the signalling link is not a crucial point because
every PCM must have a signalling link in it.
How the redundancy and the reliability of the interface will be implemented. The PBX
signallings are not complete signalling systems compared to the Common Channel
Signalling system. For example, if the link goes down, the traffic will not be directed
to other links automatically. This can be achieved by using alternative routing. If load
sharing is needed, the solution is the percentage call distribution.
What type of signalling will be used. This depends on the capabilities of the equip-
ment to be connected, or what kind of supplementary services are needed.
Before configuring the interface

Before configuring the signalling interface, the following issues have to be defined:
The number of PCMs and the hardware related to them (ETs, ECUs). The related
parameters for the transmission, which is:
the line coding used (HDB3 in MSC)
whether the CRC4 procedure is used or not
The impedance of the interface must also be defined.
The signalling used and the number of links. The WTI command can be used to
interrogate whether the required signalling hardware is available. The role of the link
must also be determined. In DPNSS1, one end must be configured as A and the
other end as B. In DSS1 the corresponding definition is User and Network (the latter
is the default in the MSC).
The circuit group and route-related parameters like CTRL, LSI, INR and OUTR,
some of which are customer-specific and can be found in the customer-specific
document sets. The LSIs for DSS1 are explained in Values of the LSI parameter.
The CTRL parameter has significance only in DPNSS1. It defines the handling of the
call collision (also known as dual seizure). When the CTRL=X , the incoming call is
ignored and the outgoing call has precedence over the incoming call. When the
CTRL=Y, the MSC accepts the incoming call and the handling of the outgoing call
depends on the end-of-selection (EOS) analysis for clear code dual seizure from a
bidirectional circuit (0B23H).
There are some parameters specifically related to 23B+D signalling. For instance,
there is the charging number, PLOCK, which is related to Equal Access. With
DN98905095 Id:0900d80580570d30 19
Issue 7-0
Planning D-channel configuration D-Channel Signalling
23B+D, you also need to use the CW command group to configure the switch to
determine the type of number of the called party.
The call number of the interface (typically the number of the attendant), the exten-
sion number range, and whether the calling line identification screening is to be used
or not.
The digit sequence to be used in the number analysis leading to the interface, and
all the analysis trees in which the analysis is needed.
Charging case to be used.
Whether the PBX is capable of generating tones or not.
What supplementary services must be configured.
The following figure presents the process of how to create an interface.
Figure 5 D-channel configuration diagram

The following figure presents the process of how to create an interface when the PBX is
connected to the MGW.
20 Id:0900d80580570d30 DN98905095
Issue 7-0
D-Channel Signalling Planning D-channel configuration
Figure 6 D-channel configuration diagram when the PBX is connected to the MGW
DN98905095 Id:0900d80580570d30 21
Issue 7-0
Configuring the DSS1 30B+D interface D-Channel Signalling
4 Configuring the DSS1 30B+D interface

Purpose
The process of configuring the DSS1 30B+D interface is described in the following sec-
tions.
Before you start

Before creating a DSS1 interface between an MSC and a PBX, check whether the
required hardware is available in the MSC using the WTI command.
For further information before configuration, see Planning D-channel configuration.
If the PBX is connected to the MGW, a semipermanent cross connection has to be
created in the MGW before creating and configuring the exchange terminal units. To
create a semipermanent cross connection in the MGW, use the RSC MML command.
4.1 Creating a semipermanent cross connection in MGW
g These steps only apply to those cases when the PBX is connected to the MGW.
If the PBX is connected to the MGW, a semipermanent TDM cross connection has to be
created in the MGW to route the D-channel from the MGW to the MSS.
Steps
1 Create semipermanent cross connection (RSC).
ZRSC:CRCT=<PCM-TSL>:CRCT<PCM-TSL>;
2 Interrogate the semipermanent cross connection (RST).
ZRSI:CRCT=<PCM-TSL>:CRCT<PCM-TSL>;
3 Modify the semipermanent cross connection (RSI).
ZRSX:CRCT=<PCM-TSL>:CRCT<PCM-TSL>;
4.2 Creating and configuring the exchange terminal (ET)

unit(s)
Steps
1 Create the required ET unit(s) (WTU).
ZWTU:ET,<pcm>:<coordinate>;
2 Create the required plug-in unit(s) (WTP).
ZWTP:ET,<unit index>:<piu>,<piu
index>,<track>::<function>,<4M-pcm>,<pcm>,TSL,0;
3 Connect the ET units (WUC).
ZWUC:ET,<pcm>:<piu>,<piu index>:UPART=30B+D:PAU,<unit
index>:;
Further information
An example of creating and configuring the ET units can be found in Example of creating
a DSS1 30B+D interface.
22 Id:0900d80580570d35 DN98905095
Issue 7-0
D-Channel Signalling Configuring the DSS1 30B+D interface
4.3 Creating and configuring an echo canceller unit (ECU)

Steps
1 Create the unit (WTU).
ZWTU:ECU,<unit index>:<coordinate>;
g You do not need to create an ECU when the interface is towards an Access Router.
2 Create the plug-in unit (WTP).

ZWTP:ECU,<unit index>:<piu>,<piu index>,<track>::GENERAL,<2m-
pcm>,<int pcm of ecu>,TSL,<timeslot>;
3 Connect the unit (WUC).
ZWUC:ECU,<unit index>:<piu>,<piu index>::IWCU,<unit index>;
4.4 Creating an LAPD signalling link and circuit group

Steps
1 Create an LAPD signalling link (DSC).
ZDSC:<link name>:PAU,<unit index>:<external PCM-
TSL>:<interface side>;
2 Create a circuit group (RCC).
ZRCC:TYPE=<circuit group type>,NCGR=<circuit group
name>,CGR=<circuit group number>:LSI=<line
signalling>:INR=<incoming register signalling>,TREE=<analysis
tree>,NCCP=<call control parameter set>;
Create an EDCS circuit group (RCC).
This step applies to the case when the PBX is connected to the MGW.
ZRCC:TYPE=EDCS,<circuit group name>,NCGR=<circuit group
tree>,NCCP=<call control parameter
set>:UPART=<6:DSS1,7:DPNSS>:MGW=<mgw>;
3 Add circuits to circuit group (RCA).
ZRCA:NCGR=<circuit group name>:CRCT=<circuit>,DCS=<name of
signalling link>;
Further information
An example of creating an LAPD signalling link and circuit groups can be found in
Example of creating a DSS1 30B+D interface.
4.5 Creating and modifying a route

Before you start
For a suitable OUTR parameter for the PBX interface, see the customer-specific
document sets.
DN98905095 Id:0900d80580570d35 23
Issue 7-0
Steps
1 Create the route (RRC).
ZRRC:EXT:ROU=<external route number>,NCGR=<circuit group
name>,STP=<starting point for outgoing
dialling>,OUTR=<outgoing register signalling>,NCCP=<name of
call control parameter set>,TON=<type of number>;
2 Modify the route (RRM).
ZRRM:ROU=<external route number>,NCLISET=<existing cli
formatting set name>;
Futher information
An example of creating a route can be found in Example of creating a DSS1 30B+D
interface.
4.6 Creating digit analysis components

Steps
1 Create a charging case (RDE).
ZRDE:NCHA=<name of charging case>:CP=<charging
point>,MCZ=<main charging zone>;
2 Create the subdestination (RDE).
ZRDE:NSDEST=<name of subdestination>:ROU=<outgoing
route>,SP=<seizure point>,CT=<call type>;
3 Create the destination (RDE).
ZRDE:NDEST=<name of destination>:NSDEST=<name of
subdestination>:CORG=<number of charging origin>,NCHA=<name
of charging case>;
4 Add a charging case (RDG).
ZRDG:NDEST=<name of destination>,CORG=<corg>:NCHA=<ncha>;
5 Create the digit analysis (RDC).
ZRDC:TREE=<analysis tree>,DIG=<digits>,TON=<type of
number>:NDEST=<name of destination>;
Further information
An example of creating digit analysis components can be found in Example of creating
4.7 Creating a Call Number and Routing Zone Index based on

Circuit Group
Before you start
The call number of the PBX is used as the default Calling Line Identity in a situation
where Calling Line Identity has not been received from the PBX, and outgoing signalling
is asking for it. For further information, see Configuring calling line identification.
24 Id:0900d80580570d35 DN98905095
Issue 7-0
g Routing Zone Index is used for a PBX-originated emergency call.
Steps
1 Create a Call Number and Routing Zone Index based on Circuit Group (SDC).
ZSDC:NCGR=<circuit group name>,AREA=<area code>,CALL=<call
number>,SID=<number of significant digits>,RZI=<routing zone
index>;
Further information
An example of creating Call Number and Routing Zone Index based on Circuit Group
can be found in Example of creating a DSS1 30B+D interface.
4.8 Defining services for PBX calls

Steps
1 Define services for PBX-originated calls (SAC).
ZSAC:NCGR=<circuit group name>:FIS=<first
subnumber>,LAS=<last
subnumber>,COTO=Y/N,CLIR=O/1/2/3,ACE=<ace>,PNI=<pni>;
2 Define services for PBX-terminated calls.
Steps
1. Define DDI and CLIP for the PBX interface (SAC).
ZSAC:PBXI=<private branch exchange interface
name>:DDI=Y/N,CLIP=Y/N;
2. Link the service which was allocated to the destination for a PBX customer
(RMM).
ZRMM:NDEST=<destination name>:PBX=<service index>;
You can see the service index on the screen when the SAC command is executed;
you can also interrogate it with the SAI command.
Further information
An example of defining services for PBX calls can be found in Example of creating a
DSS1 30B+D interface.
4.9 Changing the state of the ET, ECU, link, circuit group, and
circuits to WO-EX
Steps
1 Change the state of ET and ECU (USC).
ZUSC:<unit type>,<unit index>:<working state>;
2 Change the state of LAPD link (DTC).
ZDTC:<name of link>:<D-channel state change>;
3 Change the state of the circuit group by name (CRM).
ZCRM:NCGR=<circuit group name>:<circuit group state>;
DN98905095 Id:0900d80580570d35 25
Issue 7-0
Alternatively, you can change the state of the circuit group by number.
4 Change the state of circuit group by number (CRM).
ZCRM:CGR=<circuit group number>:<circuit group state>;
5 Change the state of speech circuits (CEC).
ZCEC:CRCT=<circuit>...:<state>;
Further information
An example of changing the state of the ET, ECU, link, circuit group, and circuits to WO-
EX can be found in Example of creating a DSS1 30B+D interface.
4.10 Creating/modifying the End-of-Selection (EOS) analysis

for incoming signalling
Steps
1 Create the EOS analysis for incoming signalling (RXC).
ZRXC:<cause code>:<result group>,<analysis result
identifier>:;
2 Modify the EOS analysis for incoming signalling (RXM).
ZRXM:<result group>:<cause code>:<analysis result
identifier>:;
Further information
An example of creating/modifying the End-of-Selection (EOS) analysis for incoming sig-
nalling can be found in Example of creating a DSS1 30B+D interface.
4.11 Example of creating a DSS1 30B+D interface

Purpose
This example describes how to create a DSS1 30B+D interface between an MSC and
an Access Router. The purpose of the interface is data access. The following figure
shows the system as a whole, including MSC2, which is configured with the same
commands as MSC1.
26 Id:0900d80580570d35 DN98905095
Issue 7-0
Figure 7 DSS1 30B+D example
Steps
1 Check the hardware configuration (WTI).
ZWTI:P;
2 Create and configure the ET units.
The units are created in two separate cards as a redundancy for the connection.
Steps
a. Create the ET units (WTU).
ZWTU:ET,472:2C1-7:;
ZWTU:ET,474:2C1-7:;
b. Create the plug-in units (WTP).
ZWTP:ET,472:ET2E,0,0::ETT00,4,472,TSL,0:;
ZWTP:ET,474:ET2E,0,0::ETT00,4,474,TSL,0:;
c. Connect the ET units (WUC).
ZWUC:ET,472:ET2E,0:UPART=30B+D:PAU,0:;
ZWUC:ET,474:ET2E,0:UPART=30B+D:PAU,1:;
3 Creating an ECU.
You do not need to create an ECU when the interface is towards an Access Router.
4 Create a 30 B+D signalling link (DSC).
Links are created for two separate units in order to secure the connection.
ZDSC:PRA01:PAU,0:472-16:N;
DN98905095 Id:0900d80580570d35 27
Issue 7-0
ZRCC:TYPE=DCS,NCGR=AR01,CGR=1008:LSI=PRA01:INR=IMPF0,TREE=11
0,NCCP=BASICINPSTNPBX;
ZRCC:TYPE=DCS,NCGR=AR02,CGR=1009:LSI=PRA01:INR=IMPF0,TREE=11
0,NCCP=BASICINPSTNPBX;
ZRCA:NCGR=AR01:CRCT=4721&&-15,DCS=PRA01;
ZRCA:NCGR=AR02:CRCT=4741&&-15,DCS=PRA02;
7 Create a route (RRC).
ZRRC:EXT:ROU=1008,OUTR=OMPF0,STP=4,NCGR=AR01,TON=NOE,NCCP=BA
SICOUTPSTNPBX;
ZRRC:EXT:ROU=1009,OUTR=OMPF0,STP=4,NCGR=AR02,TON=NOE,NCCP=BA
SICOUTPSTNPBX;
8 Create analysis components (RDE).
a) Charging case
ZRDE:NCHA=COSTLY:CP=OE,MCZ=3;
b) Subdestinations
ZRDE:NSDEST=AR01:ROU=1008,SP=10,CT=NC;
ZRDE:NSDEST=AR02:ROU=1009,SP=10,CT=NC;
c) Destination
ZRDE:NDEST=ACCESSROUTER:NSDEST=AR01:NCHA=COSTLY:;
ZRDE:NDEST=ACCESSROUTER,ALT=1:NSDEST=AR02: NCHA=COSTLY:;
9 Add a charging case (only if needed) (RDG).
ZRDG:NDEST=ACCESSROUTER,CORG=0:NCHA=CHA1;
ZRDG:NDEST=ACCESSROUTER,CORG=0:NCHA=CHA1;
10 Create the digit analysis for mobile-originated calls (RDC).
ZRDC:TREE=2,DIG=805,TON=NAT:NDEST=ACCESSROUTER;
11 Create a Call Number and Routing Zone Index (SDC).
ZSDC:NCGR=AR01,AREA=0177,CALL=1200,SID=4,RZI=1;
ZSDC:NCGR=AR02,AREA=0177,CALL=1200,SID=4,RZI=1;
12 Define supplementary services for the interface (SAC, RMM).
a) For PBX-originated calls:
ZSAC:NCGR=AR01:FIS=0000,LAS=5000,CLIR=0,COTO=N;
ZSAC:NCGR=AR02:FIS=0000,LAS=5000,CLIR=0,COTO=N;
b) For PBX-terminated calls:
ZSAC:PBXI=ACCESSROUTER:DDI=Y,CLIP=Y;
ZRMM:NDEST=ACCESSROUTER:PBX=2;
13 Define incoming services
Incoming services for a PBX customer were defined already in the previous step.
28 Id:0900d80580570d35 DN98905095
Issue 7-0
14 Change the states of the ET, link, the circuit group, and the circuits to WO-EX (USC,
CRM, CEC, DTC).
a) ETs
ZUSC:ET,472:SE;
ZUSC:ET,472:TE;
ZUSC:ET,472:WO;
ZUSC:ET,474:SE;
ZUSC:ET,474:TE;
ZUSC:ET,474:WO;
b) Circuit group
ZCRM:NCGR=AR01:WO;
ZCRM:NCGR=AR02:WO;
c) Circuits
ZCEC:CRCT=472-1&&-15:BA;
ZCEC:CRCT=472-1&&-15:WO;
Circuits will be in BA-SY state because the link has not been activated.
d) Links
ZDTC:PRA01:AL;
ZDTC:PRA01:WO;
ZDTC:PRA02:AL;
ZDTC:PRA02:WO;
Circuits will be in WO-EX now if the link comes up. Remember to activate the
links from the other end as well.
DN98905095 Id:0900d80580570d35 29
Issue 7-0
5 Configuring the DSS1 23B+D interface

Purpose
The process of creating a DSS1 23 B+D interface between an MSC and a PBX or any
other piece of equipment using DSS1 signalling system is described in the following sec-
tions.
Before you start

Before creating a DSS1 interface between an MSC and a PBX, check whether the
required hardware is available in the MSC with the WTI command. An example of
checking hardware configuration is presented in Check the hardware configuration.
For further information before configuration, see Planning D-channel configuration.

Purpose
Steps
ZRST:CRCT=<PCM-TSL>:CRCT<PCM-TSL>;
5.2 Creating and configuring the exchange terminal (ET)

unit(s)
Steps
1 Create the ET unit(s) (WTU).
2 Create the plug-in unit(s) (WTP).
ZWTP:ET,<unit index>:<piu>,<piu index>,<track>::<function>,<2
or 4-pcm>,<pcm>, TSL, <timeslot>;
ZWUC:ET,<pcm>:<piu>,<piu index>:UPART=30B+D:PAU,<unit
index>:;
30 Id:0900d80580570d3a DN98905095
Issue 7-0
Further information
An example of creating and configuring the ET units can be found in Example of creating
5.3 Creating a 23B+D signalling link and circuit group

Steps
1 Create a 23B +D signalling link (DSC).
ZDSC:<link name>:PAU,<unit index>:<external PCM-
TSL>:<interface side>;
Further information
An example of creating a 23B+D signalling link and circuit group can be found in
5.4 Adding and modifying circuits in a circuit group, adding a

charging case
Steps
1 Add circuits to the circuit group (RCA).
ZRCA:NCGR=<circuit group name>:CRCT=<circuit>,DCS=<name of
signalling link>;
2 Modify the circuit group (RCM).
ZRCM:NCGR=<circuit group name>:PLOCK=<preferred interexchange
carrier lock>,CHRN=<charge number for the circuit group>;
ZRDG:NDEST=<name of destination>,CORG=<corg>:NCHA=<ncha>;
Further information
An example of adding and modifying circuits in a circuit group, and adding a charging
case can be found in Example of creating a DSS1 23B+D interface.
DN98905095 Id:0900d80580570d3a 31
Issue 7-0
5.5 Creating and modifying a route

Before you start
For a suitable OUTR parameter for the PBX interface, refer to the customer-specific
document sets.
Steps
1 Create the route (RRC).
ZRRC:EXT:ROU=<external route number>,NCGR=<circuit group
name>,STP=<starting point for outgoing
dialling>,OUTR=<outgoing register signalling>,NCCP=<name of
call control parameter set>,TON=<type of number>;
2 Modify the route (RRM).
ZRRM:ROU=<external route number>,NCLISET=<existing cli
formatting set name>;
Further information
An example of creating and modifying a route can be found in Example of creating a
5.6 Creating digit analysis and digit analysis components

Steps
2 Create the subdestination (RDE).
3 Create the destination (RDE).
subdestination>:CORG=<number of charging origin>,NCHA=<name
of charging case>;
Further information
An example of creating digit analysis and digit analysis components can be found in
5.7 Creating a Call Number and Routing Zone Index based on

Circuit Group
Before you start
The call number of the PBX is used as a default CLI in a situation where CLI has not
been received from the PBX, and outgoing signalling is asking for it. For further informa-
tion on calling line identification, see Configuring calling line identification.
32 Id:0900d80580570d3a DN98905095
Issue 7-0
Steps
index>;
Further information
An example of creating a Call Number and Routing Zone Index based on Circuit Group
can be found in Example of creating a DSS1 23B+D interface.
5.8 Creating an Extended Preanalysis Result and subanalysis

Steps
1 Create an Extended Preanalysis Result to determine the type of number (CWR).
ZCWR:<name of final result>:ODC=<original dialling
class>,CON=<characteristics of number>;
2 Create a subanalysis (CWC).
ZCWC:<name of subanalysis>,START/CONT:NBR=<number origin or
destination>,DIG=<digits>,TON=<type of number>:RES=<final
result when attribute is matched>/ANA=<next subanalysis when
attribute is matched>,DEFRES=<final result when attribute is
not matched>/DEFANA=<next subanalysis when attribute is not
matched>;
Further information
An example of creating an Extended Preanalysis Result and subanalysis can be found
in Example of creating a DSS1 23B+D interface.
5.9 Modifying the originating line identifier and the charge

number indicator
Steps
1 Modify the originating line identifier and the charge number indicator (CPM).
ZCPM:NCCP=<nccp>::::OLI=<oli>,CHRNI=<chrni>;
g Perform this action only if required.
Further information
An example of creating an Extended Preanalysis Result and subanalysis can be found
in Example of creating a DSS1 23B+D interface. F
For more information on modifying CLI screening, see Supplementary services, Config-
uring CLR screening.
DN98905095 Id:0900d80580570d3a 33
Issue 7-0
5.10 Defining services for PBX calls

Steps
subnumber>,LAS=<last subnumber>,COTO=Y/N,CLIR=O/1/2/3;
2 Define services for PBX-terminated calls (SAC, RMM).
1. Define DDI and CLIP for the PBX interface.
ZSAC:PBXI=<pbxi>:DDI=Y/N,CLIP=Y/N;
2. Link the service which was allocated to the destination for a PBX customer.
g You can see the service index on the screen when the SAC command is exe-
cuted; you can also interrogate it with the SAI command.
ZRMM:NDEST=<ndest>:PBX=<service index>;
Further information
An example of defining services for PBX calls can be found in Example of creating a
5.11 Changing the state of the ET, ECU, link, circuit group, and
circuits to WO-EX
Steps
1 Change the state of ET and ECU (USC).
ZUSC:<unit type>,<unit index>:<working state>;
2 Change the state of LAPD link (DTC).
3 Change the state of the circuit group by name (CRM).
Alternatively, you can change the circuit group state by number.
5 Change the state of speech circuits (CEC).
Further information
An example of changing the state of the ET, ECU, link, circuit group, and circuits to WO-
EX can be found in Example of creating a DSS1 23B+D interface.
34 Id:0900d80580570d3a DN98905095
Issue 7-0
5.12 Creating/modifying the End-of-Selection (EOS) analysis

for incoming signalling
Steps
1 Create the EOS analysis for incoming signalling (RXC).
ZRXC:<cause code>:<result group>,<analysis result
identifier>,<analysis tree>,<charging
origin>,<notigication>,<timeslot of signal
tone>,<announcement number>,<announcement charging>,<forward
release>,<new cause code>;
2 Modify the EOS analysis for incoming signalling (RXM).
ZRXM:<result group>:<cause code>:<analysis result
identifier>,<cm analysis tree>,<charging
origin>,<notification>,<timeslot of signal
tone>,<announcement number>,<announcement charging>,<foreward
Further information
An example of creating/modifying the End-of-Selection (EOS) analysis for incoming sig-
nalling can be found in Example of creating a DSS1 23B+D interface.
5.13 Example of creating a DSS1 23B+D interface

Purpose
This example explains how to create a DSS1 23B+D interface between an MSC and
PBX. The purpose is normal speech transmission.
DN98905095 Id:0900d80580570d3a 35
Issue 7-0
Figure 8 DSS1 23B+D example
Steps
ZWTI:P;
2 Create and configure the ET units (WTU, WTP, WUC).
The units are created in two separate cards as a redundancy for the connection.
If echo cancelling is needed, use EC2ET_A instead of ET2A.
1. Create the ET units.
ZWTU:ET,436:2C2-7:;
ZWTU:ET,437:2C2-7:;
2. Create the plug-in units.
ZWTP:ET,436:ET2A,0,5::ETT00,4,436,TSL,0:;
ZWTP:ET,437:ET2A,0,5::ETT00,4,437,TSL,0:;
3. Connect the ET units.
ZWUC:ET,436:ET2A,0:UPART=30B+D:PAU,0:;
ZWUC:ET,437:ET2A,0:UPART=30B+D:PAU,1:;
3 Create a 23 B+D signalling link (DSC).
Links are created for two separate units as a redundancy for the connection.
4 Create and modify a circuit group (RCC, RCA, RCM).
36 Id:0900d80580570d3a DN98905095
Issue 7-0
1. Create a circuit group.

ZRCC:TYPE=DCS,NCGR=PBX436,CGR=2008:LSI=PRA06:INR=INHF0,TRE
E=70,NCCP=BASICINPSTNPBX;
ZRCC:TYPE=DCS,NCGR=PBX437,CGR=2009:LSI=PRA06:INR=INHF0,TRE
E=70,NCCP=BASICINPSTNPBX;
2. Add circuits to circuit group.
ZRCA:NCGR=PBX436:CRCT=4361&&-23,DCS=PRA1;
ZRCA:NCGR=PBX437:CRCT=4741&&-23,DCS=PRA2;
3. Modify the circuit group.
ZRCM:NCGR=PBX436:PLOCK=Y,CHRN=8940050;
ZRCM:NCGR=PBX437:PLOCK=Y,CHRN=8940050;
5 Create and modify a route (RRC).
ZRRC:EXT:ROU=2008,NCGR=PBX436,STP=4,OUTR=ONHF0,
NCCP=BASICOUPSTNPBX,TON=NOE;
ZRRC:EXT:ROU=2009,NCGR=PBX437,STP=4,OUTR=0NHF0,
NCCP=BASICOUTPSNTPBX,TON=NOE;
1. Subdestinations
ZRDE:NSDEST=PBX436:ROU=2008,SP=1,CT=NC;
ZRDE:NSDEST=PBX437:ROU=2009,SP=1,CT=NC;
2. Destination
ZRDE:NDEST=DEST23:NSDEST=PBX436:NCHA=CHA1:;
ZRDE:NDEST=DEST24:NSDEST=PBX437:NCHA=CHA1:;
7 Add a charging case, when needed (RDG).
ZRDG:NDEST=DEST23,CORG=0:NCHA=CHA1;
ZRDG:NDEST=DEST24,CORG=0:NCHA=CHA1;
8 Create the digit analysis for mobile and PBX-originated calls (RDC).
ZRDC:TREE=2,DIG=894,TON=NAT:NDEST=DEST23;
9 Create an extended preanalysis to determine the type of number (CWR, CWC).
ZCWR:RES1:CON=NAT;
ZCWR:RES2:CON=LOC;
ZCWR:RES3,STOP:ANNUM=069;
ZCWC:N40R7,CONT:NBR=CDNBR,DIG=%%%%%%%%%%S,TON=NAT:RES=RES1,
DEFRES=RES2;
ZCWC:N40R8,CONT:NBR=CDNBR,DIG=%%%%%%%S,TON=LOC:RES=RES1,
DEFRES=RES3;
ZCWC:NUMTYPE,START,8:NBR=CDNBR,TON=NAT,:ANA=N40R7,DEFANA=N40
R8;
10 Modify CLI screening and the charge number indicator (CPM).
ZCPM:NCCP=BASICINPSTNPBX:::CLIS=Y,;
DN98905095 Id:0900d80580570d3a 37
Issue 7-0
ZCPM:NCCP=BASICINPSTNPBX:::CLIT=N,;
ZCPM:NCCP=BASICINPSTNPBX:::CALLNS=N,;
ZCPM:NCCP=BASICINPSTNPBX::::OLI=POTS,CHRNI=N,;
11 Create a Call Number and Routing Zone Index (SDC).
ZSDC:NCGR=PBX436,AREA=972,CALL=8945000,SID=3,RZI=0;
ZSDC:NCGR=PBX437,AREA=972,CALL=8945000,SID=3,RZI=0;
ZSAC:NCGR=PBX436:FIS=2000,LAS=5000,CLIR=0,COTO=Y;
ZSAC:NCGR=PBX437:FIS=2000,LAS=5000,CLIR=0,COTO=Y;
13 Define services for PBX-terminated calls (SAC, RMM, WWS).
1. Define DDI and CLIP for the PBX interface.
ZSAC:PBXI=NOKIA7:DDI=Y,CLIP=Y;
ZRMM:NDEST=DEST23:PBX=3;
ZRMM:NDEST=DEST24:PBX=4;
(PBX=<service index>) This number is displayed on the screen when the
previous command (SAC) is executed.
2. Define a default carrier for a circuit group.
ZWWS:CC:NP=10666;
14 Change the states of the ET, link, the circuit group, and the circuits to WO-EX (USC,
CRM, CEC, DTC).
1. ETs
ZUSC:ET,436:SE;
ZUSC:ET,436:TE;
ZUSC:ET,436:WO;
ZUSC:ET,437:SE;
ZUSC:ET,437:TE;
ZUSC:ET,437:WO;
2. Circuit group
ZCRM:NCGR=PBX436:WO;
ZCRM:NCGR=PBX437:WO;
3. Circuits
Circuits will be in BA-SY state because the link has not been activated.
4. Links
ZDTC:PRA1:WO;
Circuits will be in WO-EX now if the link comes up. Remember to activate the
links from the other end as well.
15 Create/modify the EOS analysis for incoming signalling (RXM).
Modify the EOS analysis for incoming signalling.
ZRXM:1:1009:CMANAL,50,0,,,:;
38 Id:0900d80580570d3a DN98905095
Issue 7-0
D-Channel Signalling Configuring a DPNSS1 interface
6 Configuring a DPNSS1 interface

Purpose
The process of configuring a DPNSS1 interface is described in the following sections.
The steps are explained with syntax and parameters, and an example is presented for
the configuration of a DPNSS1 interface between a DX MSC and a PBX.
Before you start

Before creating a DPNSS1 interface between an MSC and a PBX or another piece of
equipment, it can be checked whether the required hardware is available with the WTI
command.
For further information before configuration, see Checking configuration.

Purpose
Steps
ZRST:CRCT=<PCM-TSL>:CRCT<PCM-TSL>;
6.2 Creating and configuring ET unit(s)

Steps
1 Create the required ET unit(s) (WTU).
2 Create the required plug-in unit(s) (WTP).
ZWTP:ET,<unit index>:<piu>,<piu
index>,<track>::<function>,<2M-pcm>,<pcm>,TSL,0;
ZWUC:ET,<pcm>:<piu>,<piu index>:UPART=DPNSS:PAU,<unit
index>:;
DN98905095 Id:0900d80580570d3f 39
Issue 7-0
Configuring a DPNSS1 interface D-Channel Signalling
Further information
An example of creating and configuring the ET units can be found in Example of config-
uring DPNSS1 interface.If you need to create an Echo Canceller Unit (ECU), see
Creating and configuring an echo canceller unit (ECU).
6.3 Creating a DPNSS1 link

Purpose
Create a D-channel for data link connections.
Before you start

The signalling channel for DPNSS PCM is timeslot 16. The PBX types must be deter-
mined so that one end of the DPNSS link is of type A and the other is of type B. When
creating a DPNSS link, the range of DLCs (real/virtual) must also be defined; otherwise
the whole set of DLCs is configured for the DPNSS link, as this is the default.
Steps
1 Create a DPNSS1 link (DNC).
ZDNC:<link name>:PAU,<unit index>:<external PCM-
TSL>:<protocol>,<pbx type>:<real dlc range>,<virtual dlc
range>;
Further information
An example of creating a DPNSS1 link can be found in Example of configuring DPNSS1
interface.
6.4 Creating a circuit group and adding circuits

Before you start
For suitable LSI and INR parameters for the PBX interface, see the customer-specific
document sets.
The Circuit CTRL parameter should be defined as X (the circuit in home exchange's
handle) or Y (the circuit in partner PBX's handle) for call collisions.
Steps
40 Id:0900d80580570d3f DN98905095
Issue 7-0

ZRCA:NCGR=<circuit group name>:CRCT=<PCM-TSLS>,DCS=<name of
d-channel system>;
Further information
An example of creating a circuit group and adding circuits can be found in Example of
configuring DPNSS1 interface.
6.5 Creating a route and analysis components

Before you start
For a suitable OUTR parameter for the PBX interface, see the customer-specific
document sets.
Steps
1 Create a route (RRC).
ZRRC:EXT:NCCP=<nccp>,ROU=<rou>,NCGR=<ncgr>,STP=<stp>,OUTR=<o
utr>,TON=<ton>;
2 Create the analysis components (charging case, subdestination, and destination).
1. Create a charging case.
ZRDE:NCHA=<name of charging casen>:CP=<charging
point>,MCZ=<main charging zone>;
2. Create the subdestination.
3. Create the destination.
subdestination>:CORG=<number of charging
origin>,NCHA=<name of charging case>;
Further information
An example of creating a route and analysis components can be found in Example of
configuring DPNSS1 interface.
6.6 Creating a digit analysis and a charging component

Steps
1 Create a digit analysis (RDC).
2 Create a charging component (RDG).
ZRDG:NDEST=<name of destination>,CORG=<charging
origin>:NCHA=<name of charging case>;
Further information
An example of creating a digit analysis and a charging component can be found in
Example of configuring DPNSS1 interface.
DN98905095 Id:0900d80580570d3f 41
Issue 7-0
6.7 Creating a Call Number and Routing Zone Index

Before you start
The call number of the PBX is used as a default Calling Line Identity (CLI) in a situation
where CLI has not been received from the PBX, and outgoing signalling is asking for it.
Steps
index>;
Further information
An example of creating a Call Number and Routing Zone Index can be found in Example
of configuring DPNSS1 interface.
6.8 Defining PBX services

Steps
1 Define PBX-originated services (SAC).
subnumber>,LAS=<last
subnumber>,COTO=Y/N,CLIR=O/1/2/3,PNI=<pni>;
2 Define PBX-terminated services (SAC, RMM).
1. Define DDI and CLIP.
Define DDI and CLIP for the PBX interface.
ZSAC:PBXI=<private branch exchange interface
name>:DDI=Y/N,CLIP=Y/N;
2. Link the service.
Link the service which was allocated to the destination for a PBX customer. You
can see the service index on the screen when the SAC command is executed;
you can also interrogate it with the SAI command.
ZRMM:NDEST=<destination name>:PBX=<service index>;
Further information
An example of PBX services can be found in Example of configuring DPNSS1 interface.
6.9 Changing the state of the ET, ECU, link, the circuit group,
and the circuits to WO-EX
Purpose
Change the states of the link, the circuit group, the route and the circuits to WO-EX.
42 Id:0900d80580570d3f DN98905095
Issue 7-0
Steps
1 Change the state of circuit group by name (CRM).
Alternatively, you can change circuit group state by number.
3 Change state of speech circuits (CEC).
4 Change state of link (DNS).
ZDNS:<DLC D-channel name>;
Further information
An example of changing the state of the ET, ECU, link, the circuit group and the circuits
to WO-EX can be found in Example of configuring DPNSS1 interface.
6.10 Creating and modifying End-of-Selection (EOS) analysis

Steps
1 Create the EOS analysis (RXC).
ZRXC:<cause code>:<incoming signalling>,<analysis result
2 Modify the EOS analysis (RXM).
ZRXM:<incoming signalling>:<cause code>:<analysis result
release>:INOP=<core inap detection point>;
Further information
An example of creating and modifying End-of-Selection (EOS) analysis can be found in
Example of configuring DPNSS1 interface.
6.11 Example of configuring DPNSS1 interface

Purpose
This example shows how to create a DPNSS1 interface between a DX 200 MSC and a
PBX with multiple PCMs.
DN98905095 Id:0900d80580570d3f 43
Issue 7-0
Figure 9 DPNSS1 example
Steps
ZWTI:P;
2 Create and configure the ET units (WTU, WTP, WUC).
1. Create the ET units.
ZWTU:ET,90:2E160-7;
ZWTU:ET,91:2E160-7;
ZWTU:ET,92:2E160-7;
ZWTU:ET,93:2E160-7;
2. Create the plug-in units.
ZWTP:ET,90:ET1E,0,22::ETT00,2,90,TSL,0;
3. Connect the ET units.
ZWUC:ET,90:ET1E,0:UPART=DPNSS:PAU,0;
3 Create and configure an ECU (WTU, WTP, WUC).
1. Create the unit.
ZWTU:ECU,90:2B133-0;
2. Create the plug-in unit.
ZWTP:ECU,90:EC1P,0,26::GENERAL,2,90,TSL,0;
3. Connect the unit.
ZWUC:ECU,90:EC1P,0::IWCU,0;
4 Create DPNSS1 signalling links (DNC).
ZDNC:DPNS1:PAU,0:90-16:1,A;
44 Id:0900d80580570d3f DN98905095
Issue 7-0
5 Create a circuit group and add circuits (RCC, RCA).
1. Create a circuit group.
ZRCC:TYPE=DCS,NCGR=CALLCENTER,CGR=1004:LSI=DPN01:INR=IMPM0
,TREE=110,NCCP=BASICINPSTNPBX;
2. Add circuits to the circuit group.
ZRCA:NCGR=CALLCENTER:CRCT=90-1&&-15&-17&&-31,DCS=DPNS1;
3. Add circuits from other PCMs to the same circuit group, if required.
6 Create and modify a route (RRC).
ZRRC:EXT:ROU=2000,OUTR=OMPM0,STP=4,NCGR=CALLCENTER,TON=NOE,N
CCP=BASICOUTPSTNPBX;
1. Charging case
ZRDE:NCHA=CALLCENTER:CP=OE,MCZ=25;
2. Subdestination
ZRDE:NSDEST=CALLCENTER:ROU=2000,SP=10,CT=NC;
3. Destination
ZRDE:NDEST=CALLCENTER:NSDEST=CALLCENTER:NCHA=CALLCENTER:;
ZRDG:NDEST=CALLCENTER,CORG=10:NCHA=CALLCENTER;
ZRDC:TREE=2,DIG=511,TON=NAT:NDEST=CALLCENTER;
10 Create a Call Number and Routing Zone Index based on the circuit group (SDC).
ZSDC:NCGR=CALLCENTER,AREA=09,CALL=51121,SID=3,RZI=1;
11 Define supplementary services for a PBX customer (SAC, RMM).
ZSAC:NCGR=CALLCENTER:FIS=2000,LAS=6999,COTO=Y;
ZSAC:PBXI=CALLCENTER:DDI=Y,CLIP=Y;
ZRMM:NDEST=CALLCENTER:PBX=5;
12 Change the state of the ET, ECU, link, the circuit group, and the circuits to WO-EX
(USC, CRM, CEC).
DN98905095 Id:0900d80580570d3f 45
Issue 7-0
1. ETs
ZUSC:ET,90:SE;
ZUSC:ET,90:TE;
ZUSC:ET,90:WO;
ZUSC:ET,91:SE;
ZUSC:ET,91:TE;
ZUSC:ET,91:WO;
ZUSC:ET,92:SE;
ZUSC:ET,92:TE;
ZUSC:ET,92:WO;
ZUSC:ET,93:SE;
ZUSC:ET,93:TE;
ZUSC:ET,93:WO;
2. Circuit group
ZCRM:NCGR=CALLCENTER:WO;
3. Links
ZDNS:DPNS1; ZDNS:DPNS2; ZDNS:DPNS3; ZDNS:DPNS4;
4. Circuits
ZCEC:CRCT=90-1&&-15&-17&&-31:BA;
ZCEC:CRCT=91-1&&-15&-17&&-31:BA;
ZCEC:CRCT=92-1&&-15&-17&&-31:BA;
ZCEC:CRCT=93-1&&-15&-17&&-31:BA;
ZCEC:CRCT=90-1&&-15&-17&&-31:WO;
ZCEC:CRCT=91-1&&-15&-17&&-31:WO;
ZCEC:CRCT=92-1&&-15&-17&&-31:WO;
ZCEC:CRCT=93-1&&-15&-17&&-31:WO;
13 Create/modify the EOS analysis for incoming signalling (RXC).
1. For mobile-terminated calls originated from the PBX.
ZRXC:1009:1,CMANAL,50,0,,,;
2. ZRXC:100E:1,CMANAL,20,0,NOTIF,,:;
46 Id:0900d80580570d3f DN98905095
Issue 7-0
D-Channel Signalling Controlling the D-channel interfaces
7 Controlling the D-channel interfaces

Purpose
Controlling the interface includes checking and modifying the configuration. All the
commands in this section are applicable to all three signalling types.
The commands described in this section can be used separately and specific task-
sequences are not presented. Therefore, examples are presented within the subsec-
tions, if possible, and not in a separate section. Execution outputs are also presented.
7.1 Checking configuration

Purpose
The process of checking hardware- and link configuration and checking the state of the
unit is described in this section.
Steps
ZWTI:<information type>:<unit type>;
Example
Check the plug-in configuration of PAU (WTI)
ZWTI:P:PAU;
Here is a typical execution output:
EXECUTION STARTED
READING DATA FROM DATABASE ...
PAU-0 IN LOC 1G109-00
AFS_S 0 TRACK: 7
MS: ME: IS:FF80 IE:FF8F
INT: SW:
TSLS 30 20 10 0
GENERAL 2M PCM: 20 B 11111111111111110000000000000000
R 11111111111111110000000000000000
MBIF_U 1 TRACK: 87
MS: ME: IS: 40 IE: 7F
INT: SW:
and an example of a typical end of output:
TOTAL OF 3 UNITS, 18 PLUG-

IN UNITS AND 9 FUNCTIONS
COMMAND EXECUTED
2 Check the unit state (USI).

ZUSI:<unit type>;
Example
Check the state of the PAUs
DN98905095 Id:0900d80580570d42 47
Issue 7-0
Controlling the D-channel interfaces D-Channel Signalling
ZUSI:PAU;
EXECUTION STARTED
DX 200 LAB 1998-12-12 13:11:18
WORKING STATE OF UNITS

UNIT MB STATE LOCATION INFO
PAU-0 6A WO-EX -
PAU-1 6B WO-EX -
PAU-2 6C SP-EX IDLE
TOTAL OF 3 UNITS
COMMAND EXECUTED
3 Check the link configuration (DSI, DNI).

Use the following commands to check the link configuration:
DSI for DSS1
DNI for DPNSS1
These commands used without specifying any parameters show all the link con-
figurations.
ZDSI:<D-channel link set name>;
Example
Check the link configuration of the LAPD link called PRA01
ZDSI:NAME=PRA01;
DX 200 LAB 1998-12-12 13:11:20
INTERROGATING D-CHANNEL LINK SET LINK DATA
EXT SUB TERM LOG LOG INT

NAME NUM D-CHANN PCM-TSL-TSL UNIT TERM FUNC UNIT TERM PCM-TSL
----- --- ------- ----------- --------------- ---------- -------
PRA01 19 P NETW 92-16 PAU-0 1 0 4038H 64 20-08
COMMAND EXECUTED
7.2 Checking the state of the interface elements

Purpose
The following section explains how to check the state of the various interface elements.
Steps
1 Check the link state (DTI, DNP).
Use the following commands to check the state of the links:
DTI for DSS1
DNP for DPNSS1
These commands used without any parameters show the states of all the links.
48 Id:0900d80580570d42 DN98905095
Issue 7-0
ZDTI:<D-channel link name>;

Example
Check the state of the LAPD link called PRA01
ZDTI:PRA01;
DX 200 LAB 1998-12-12 13:11:19

INTERROGATING D-CHANNEL WORKING STATE
EXT WORKING
NAME NUM D-CHANN PCM-TSL STATE
----- --- ------- ----------- -------
PRA01 19 P 92-16 WO-EX
COMMAND EXECUTED
2 Check the state of circuit groups and circuits (RCI).

Use the RCI command to check the state of the circuit groups and circuits.
ZRCI:SEA=3:NCGR=<circuit group names>;
Example
Check the state of the circuit group AR01
ZRCI:SEA=3:NCGR=AR01:PRINT=4;
DN98905095 Id:0900d80580570d42 49
Issue 7-0
50 Id:0900d80580570d42 DN98905095
Issue 7-0
RCI:SEA=3:NCGR=ISUPLOOP:PRINT=5;
LOADING PROGRAM VERSION 7.20-0
CIRCUIT GROUP(S) (GSW)
CGR : 1000 NCGR : ISUPLOOP
TYPE : CCS STATE : WO-EX HUNTED : YES

FORMAT : PCM-TSL HM1 : FF HM2 : LF
NBCRCT : 30 TREE : 100 DIR : BI
LSI : DISU1 INR : IGCK4 NCCP : BASICINPSTNPB
METHOD : 1 NET : NA0 SPC(H/D) : 0270/00624
AUTOMATIC CONGESTION CONTROL
REJ11 : - REJ12 : - REJ21 : - REJ22 : -

ACT11 : NO ACTION ACT12 : NO ACTION ACT21 : NO ACTION ACT22 : NO ACTION
SELECTIVE CIRCUIT RESERVATION
TRES1 : - TRES2 : -
DR1A : - DR2A : - ART1A : - ART2A : - ACTA : NO ACTION
DR1B : - DR2B : - ART1B : - ART2B : - ACTB : NO ACTION
DR1C : - DR2C : - ART1C : - ART2C : - ACTC : NO ACTION
ADDITIONAL PARAMETERS:
AREA : - STD : -
MAN : - AAN : -
SSET : - CLI : -
CAC : - CACI : -
REMN : - RFCL : -
ICLI : - CHRN : -
ATV : -
EC : 0 DBA : 1 PRI : 1 CORG : 0 DCC : -

LOC : - DNN : 0 RDQ : 4 DDQ : 4 IGOR :
ECAT : - EOS : -
DCA : NO ARF : NO CX : NO CTR : NO NUCO : NO

TA : NO ATME : NO DCME : NO ECHO : NO RSU : NO
CLIR : - LC : NO CHG : - OAOC : - SCBM : NO
SCIE : NO SCIC : NO CA : - CAI : - ASTC : -
APRI : - ACOR : - RDR : - RNPR : - PLOCK : -
HB : NO
CIRCUIT(S):
PCM-TSL ORD CTRL HGR STATE CCSPCM
602-1 1 Y 1-1 WO-EX 0

602-2 2 X 1-2 WO-EX 0
602-3 3 Y 1-3 WO-EX 0
602-4 4 X 1-4 WO-EX 0
602-5 5 Y 1-5 WO-EX 0
602-6 6 X 1-6 WO-EX 0
602-7 7 Y 1-7 WO-EX 0
602-8 8 X 1-8 WO-EX 0
602-9 9 Y 1-9 WO-EX 0
602-10 10 X 1-10 WO-EX 0
602-11 11 Y 1-11 WO-EX 0
602-12 12 X 1-12 WO-EX 0
602-13 13 Y 1-13 WO-EX 0
602-14 14 X 1-14 WO-EX 0
602-15 15 Y 1-15 WO-EX 0
DN98905095 Id:0900d80580570d42 51
Issue 7-0
602-17 16 Y 1-16 WO-EX 0

602-18 17 X 1-17 WO-EX 0
602-19 18 Y 1-18 WO-EX 0
602-20 19 X 1-19 WO-EX 0
602-21 20 Y 1-20 WO-EX 0
602-22 21 X 1-21 WO-EX 0
602-23 22 Y 1-22 WO-EX 0
602-24 23 X 1-23 WO-EX 0
602-25 24 Y 1-24 WO-EX 0
602-26 25 X 1-25 WO-EX 0
602-27 26 Y 1-26 WO-EX 0
602-28 27 X 1-27 WO-EX 0
602-29 28 Y 1-28 WO-EX 0
602-30 29 X 1-29 WO-EX 0
602-31 30 Y 1-30 WO-EX 0
COMMAND EXECUTED
3 Check the routes (RRI).

ZRRI:GSW:ROU=<route number>;
Example
Check the information concerning route 1500
ZRRI:GSW:ROU=1500;
DX 200 LAB 1998-12-13 09:59:32

ROU TYPE OUTR STP TSG TMT SAT ATME DCME ECHO CONT TON SEQH ICR
1500 EXT OMPF0 1 - - N N N N - UNK N N
RCR MCR OCR RPR PBX ISDN STATE NCGR

N N N N Y Y WO-EX AR01
APRI ASTC NCCP T_IND ENBLOC CLISET NCLISET

N N BASICOUTPSTNPBX 0 - 0 1 DEFAULT
AICR PNR RNPR RFCL

- - - -
FCL
-
COMMAND EXECUTED
4 Interrogate digit analyses (RIR).

To display the digit analyses that lead to the destinations specified by the search
keys given, enter the following command:
ZRIR:ROU=<route number>;
5 Check the state of the subdestination and destination (RIL).
ZRIL:NSDEST=<subdestination name>;
Example
Check the state of the subdestination called AR01
ZRIL:NSDEST=AR01;
52 Id:0900d80580570d42 DN98905095
Issue 7-0
DX 200 LAB 1998-12-13 09:59:37
NAME OF SUBDESTINATION: AR01 SDEST: 53
CT SP AR RC RT RNBR SRCL MNL

NC 1 - APR ROU 1500 N 0
COMMAND EXECUTED
6 Check supplementary service information (SAI).

The command used without specifying any parameters displays all the supplemen-
tary services that have been defined for the switch.
ZSAI:NCGR=<circuit group name>:;
Example
Check the information concerning the supplementary services of the circuit
group called AR01
ZSAI:NCGR=AR01:;
DX 200 LAB 1998-12-13 09:59:46
DIGITAL BRANCH EXCHANGE SUPPLEMENTARY SERVICES:
CGR = 1200
NCGR = AR01
SUPPLEMENTARY SERVICES:
FIS....FIRST SUBNUMBER: 0000
LAS....LAST SUBNUMBER: 9999
COMMAND EXECUTED
7.3 Changing the state of the interface elements and configu-

ration
Purpose
The following section explains how to change the state of the various interface elements
and their configuration.
Steps
1 Change the link state (DTC, DNS, DNT).
Use the following commands to change the state of the link:
for DSS1
ZDNS:<D-channel name>;
DN98905095 Id:0900d80580570d42 53
Issue 7-0
or
ZDNT:<D-channel name>;
for DPNSS1.
2 Change the circuit state (CEC).
Use the CEC command to change the state of the circuits.
Example
Change the state of the circuits (CEC).
ZCEC:CRCT=931&&-15&-17&&-31:<state>;
3 Change circuit group state (CRM).
Use the following commands to change the state of the circuit group:
ZCRM:NCGR=<circuit group name>:<state>;
ZCRM:CGR=<circuit group number>:<state>;
4 Change the state of the route (CRC).
Use the following command to change the state of the route:
ZCRC:ROU=<route number>:<state>;
7.4 Changing the parameters of interface elements

Purpose
This section explains how to change the parameters of the various interface elements.
Steps
1 Change the circuit group parameters (RCM).
Example
The RCM command can be used to modify the line signalling mode:
ZRCM:NCGR=AR01:LSI=PRA02;
The syntax and parameters used in the example are:
ZRCM:NCGR=<circuit group name>:LSI=<line signalling>;
2 Change and interrogate route parameters (RRM, RRI).
Use the RRM command to change the parameters of the routes, and the RRI
command to interrogate them.
Example
Change the type of number of the route 1500 to NOE.
ZRRM:ROU=1500,TON=NOE;
ZRRM:ROU=<route number>,TON=<type of number>;
54 Id:0900d80580570d42 DN98905095
Issue 7-0
ROUTE MODIFIED
ROU = 1500
BEFORE MODIFICATION
TON UNK
AFTER MODIFICATION
TON NOE
COMMAND EXECUTED
To interrogate the routes use the following command:

ZRRI:GSW:ROU=1500;
DX 200 LAB 1998-12-13 09:59:35

1500 EXT OMPF0 1 - - N N N N - NOE N N


AICR PNR RNPR RFCL

- - - -
FCL
-
COMMAND EXECUTED
3 Change subdestination parameters (RMK).

Example
Change the seizure point of subdestination AR01 to 4.
ZRMK:NSDEST=AR01:SP=4;
ZRMK:NSDEST=<name of subdestination>:SP=<seizure point>;
DN98905095 Id:0900d80580570d42 55
Issue 7-0
EXECUTION STARTED
SUBDESTINATION DATA MODIFICATION REQUESTED
NO CHECKING OF ASSOCIATED ANALYSES
NSDEST NB RT CT SP RC SRCL CANA MNL SSQT

OLD DATA AR01 1500 ROU NC 1 APR N - 0
NEW DATA AR01 1500 ROU NC 4 APR N - 0
CONFIRMATION: Y/N/E ?Y
SUBDESTINATION DATA MODIFIED
COMMAND EXECUTED
4 Change the destination parameters (RMM).

Example
Change the destination type of the destination called ACCESSROUTER to P and
the percentage value of destination 0 and 1 of ACCESSROUTER to 50
ZRMM:NDEST=ACCESSROUTER:DTYPE=P:SPERC0=50,SPERC1=50;
ZRMM:NDEST=<name of destination>:DTYPE=<destination
type>,SPERC0=<percentage value of subdestination
0>,SPERC1=<percentage value of subdestination 1 >;
EXECUTION STARTED
DESTINATION DATA MODIFICATION REQUESTED
NO CHECKING OF ASSOCIATED ANALYSES
NDEST NL PC CNP ADDSERV DTYPE PA IA EC CDRS SSET

OLD DATA ACCESSROUTER 0 ORD N PBX 54 A N N N 0 0
NEW DATA ACCESSROUTER 0 ORD N PBX 54 P N N N 0 0
SPERC0 SPERC1 SPERC2 SPERC3 SPERC4

OLD DATA A A - - -
NEW DATA 50 50 - - -
CONFIRMATION: Y/N/E ?Y
DESTINATION DATA MODIFIED
COMMAND EXECUTED
For a more detailed description of the command, see Routing and Analyses over-
view, in Routing and Analyses.
For a more detailed description of the command, see Routing and Analyses.
5 Modify supplementary services (SAM).
Example
56 Id:0900d80580570d42 DN98905095
Issue 7-0
1. Activate CLIR for the circuit group AR01.

ZSAM:NCGR=AR01:CLIR=1;
ZSAM:NCGR=<circuit group name>:CLIR=<clir type>;
DX 200 LAB 1998-12-13 09:59:47

CGR = 1200
NCGR = AR01
SUPPLEMENTARY SERVICES BEFORE MODIFICATION:

SUPPLEMENTARY SERVICES AFTER MODIFICATION:

CLIR...PERMANENT MODE
COMMAND EXECUTED
2. Remove supplementary service DDI from private branch exchange interface

ACCESSROUTER.
ZSAM:PBXI=ACCESSROUTER:DDI=N;
ZSAM:PBXI=<digital branch exchange interface
name>:DDI=<direct dialling in>;
DX 200 LAB 1998-12-13 09:59:51

PBXI = ACCESSROUTER
INDEX OF SUPPLEMENTARY SERVICES = 54
SUPPLEMENTARY SERVICES BEFORE MODIFICATION:

DDI....DIRECT DIALLING IN
CLIP...CALLING LINE IDENTIFICATION PRESENTATION
SUPPLEMENTARY SERVICES AFTER MODIFICATION:

COMMAND EXECUTED
DN98905095 Id:0900d80580570d42 57
Issue 7-0
Deleting the D-channel interface D-Channel Signalling
8 Deleting the D-channel interface

Purpose
This section describes how to delete an interface. The steps are explained with syntax
and parameters. The DSS1 commands are the same for both the 30B+D and 23B+D
interface but the name of the link is different for different commands that can be used
for deletion.
f Caution
Remember to follow the order presented here strictly when deleting the interface.
8.1 Deactivating the links

Purpose
Before deleting the interface, the ongoing calls must be finished. You can interrogate the
ongoing calls in several ways.
Steps
1 Interrogate ongoing calls (MCJ, CEL, CET).
You can use one of the following commands:
ZMCJ:ALL=<all calls or number of calls Y/N>;
ZCEL:NCGR=<circuit group names>,FORM=<listing
form>,CONN=<information of circuit>;
The CEL command shows the status of the circuits for the whole circuit group.
ZCET:CRCT=<circuit>;
After all calls are terminated, the link or links must be deactivated to make sure that
further call attempts will not reserve circuits from the interface.
For more detailed examples, see Find out if there are ongoing calls.
2 Interrogate link (DSI, DNI).
Interrogate whether the link is active or not.
The syntax and parameter for the LAPD link are:
ZDSI:NAME=<D-channel link name>;
The syntax and parameter for the DPNSS1 link are:
ZDNI:<DLC D-channel name>;
For further examples, see Interrogate if the link is active.
3 Interrogate the working state of link (DTI, DNP).
To interrogate the working state of the DSS1 link, use the following command:
ZDTI:NAME=<D-channel link name>;
To interrogate the working state of the DPNSS1 link, use the following
command:
ZDNP:<DLC D-channel name>;
4 Deactivate link (DNT, DTC).
58 Id:0900d80580570d46 DN98905095
Issue 7-0
D-Channel Signalling Deleting the D-channel interface
To deactivate the DPNSS1 link, use the following command:

ZDNT:<name of link>;
To deactivate the LAPD link, use the following command:
ZDTC:<name of link>:BL;
8.2 Deleting digit analysis and digit analysis components

Steps
1 Interrogate digit analyses (RIR).
Find out all the digit analyses leading to the interface. Use the following command:
ZRIR:ROU=<route number>;
2 Interrogate special route analyses (RIR).
If there are analyses leading to a special route, for example for number modification,
these analyses can be displayed with the following command:
ZRIR:SPR=<special route number>;
3 Delete analyses (RDD).
ZRDD:TREE=<analysis tree>,TON=<type of number>,DIG=<digit
string>;
4 Interrogate destination and its characteristics (RIL).
ZRIL:NDEST=<destination name>;
5 Delete destinations (RDD).
ZRDD:NDEST=<destination name>;
6 Interrogate subdestinations (RIL).
ZRIL:NSDEST=<subdestination name>;
7 Delete subdestinations (RDD).
ZRDD:NSDEST=<subdestination name>;
8.3 Deleting the route and link

Steps
1 Interrogate route (RRI).
To interrogate the route, use the following command:
ZRRI:<switch>:ROU=<route number>;
2 Delete route (RRD).
To delete the route, use the following command:
ZRRD:GSW:ROU=<route number>;
3 Delete link (DND, DSD).
To delete the DPNSS1 link, use the following command:
ZDND:<name of link>;
To delete the LAPD link, use the following command:
ZDSD:<name of link>;
DN98905095 Id:0900d80580570d46 59
Issue 7-0
8.4 Deleting the call number and supplementary services

Steps
1 Interrogate call number of circuit group (SDO).
ZSDO:NCGR=<name of circuit group>;
2 Delete call number (SDD).
ZSDD:NCGR=<circuit group name>;
3 Interrogate supplementary services of circuit group (SAI).
ZSAI:NCGR=<circuit group name>;
4 Delete supplementary services of circuit group (SAD).
ZSAD:NCGR=<circuit group name>;
5 Interrogate supplementary services of PBX (SAI).
Interrogate the supplementary services of the digital branch exchange interface.
ZSAI:PBXI=<digital branch exchange interface name>;
6 Delete supplementary services of PBX (SAD).
Delete the supplementary services of the digital branch exchange interface.
ZSAD:PBXI=<digital branch exchange interface name>;
8.5 Deleting the circuit group

Steps
1 Set circuit groups to 'not used' state (CEC).
ZCEC:CRCT=<pcm-tsl>:BA;
ZCEC:CRCT=<pcm-tsl>:NU;
2 Interrogate circuit group (RCI).
ZRCI:SEA=3:NCGR=<circuit group name>:PRINT=4;
3 Delete circuit group (RCD).
ZRCD:NCGR=<name of circuit group>;
Further Information
8.6 Example of deleting an interface

Purpose
This section presents an example of deleting a signalling link with execution output
examples.
Steps
1 Find out if there are ongoing calls.
Purpose
Before deleting the interface, you must find out if there are ongoing calls. Use the
following commands:
60 Id:0900d80580570d46 DN98905095
Issue 7-0
Interrogate active calls:

ZMCJ:ALL=N;
Here is an example of a typical execution output:
TOTAL NUMBER OF ALL RECORDS IN STU-WO IS 25000

NUMBER OF ORIGINAL LEGS IS 00000
NUMBER OF HANDOVER LEGS IS 00000
NUMBER OF ROAMING LEGS IS 00000
NUMBER OF FORWARDING LEGS IS 00000
TOTAL NUMBER OF RESERVED CALL RECORDS IS 00000
COMMAND EXECUTED
List all the trunk circuits of the circuit groups AR01 in states busy and idle, and
also the number of those trunk circuits.
ZCEL:NCGR=AR01,FORM=EXT,CONN=BU&ID;
CGR NCGR NBCRCT

1200 AR01 30
CRCT STATE CONN SYS-INFO
92- 1 WO-EX IDLE -
92- 2 WO-EX IDLE -
92- 3 WO-EX IDLE -
92- 4 WO-EX IDLE -
92- 5 WO-EX IDLE -
92- 6 WO-EX IDLE -
92- 7 WO-EX IDLE -
92- 8 WO-EX IDLE -
92- 9 WO-EX IDLE -
92- 10 WO-EX IDLE -
92- 11 WO-EX IDLE -
92- 12 WO-EX IDLE -
92- 13 WO-EX IDLE -
92- 14 WO-EX IDLE -
92- 15 WO-EX IDLE -
92- 17 WO-EX IDLE -
92- 18 WO-EX IDLE -
92- 19 WO-EX IDLE -
92- 20 WO-EX IDLE -
92- 21 WO-EX IDLE -
92- 22 WO-EX IDLE -
92- 23 WO-EX IDLE -
92- 24 WO-EX IDLE -
92- 25 WO-EX IDLE -
92- 26 WO-EX IDLE -
92- 27 WO-EX IDLE -
92- 28 WO-EX IDLE -
92- 29 WO-EX IDLE -
92- 30 WO-EX IDLE -
92- 31 WO-EX IDLE -
STATE CONN COND NUMBER
WO-EX IDLE - 30
COMMAND EXECUTED
Interrogate the call connection information of the trunk circuits 92 and 94.
ZCET:CRCT=92-1&&-15&-17&&-31&94-1&&-15&-17&&-31;
The execution output shows whether there are any calls active in the trunk cir-
cuits.
2 Interrogate if the link is active (DSI, DTI).
DN98905095 Id:0900d80580570d46 61
Issue 7-0
1. Interrogate the data of D-channel link PRA01.

ZDSI:NAME=PRA01;
DX 200 LAB 1998-12-13 11:25:04

----- --- ------- ----------- --------------- ---------- -------
PRA01 19 P NETW 92-16 PAU-0 1 0 4038H 64 20-08
COMMAND EXECUTED
2. Interrogate the working state of the primary rate access D-channel PRA01.
ZDTI:NAME=PRA01
DX 200 LAB 1998-12-13 11:25:05

INTERROGATING D-CHANNEL WORKING STATE
EXT WORKING
NAME NUM D-CHANN PCM-TSL STATE
----- --- ------- ----------- -------
PRA01 19 P 92-16 WO-EX
COMMAND EXECUTED
3 Deactivate the link (DTC).

ZDTC:PRA01:BL;
The execution output shows the new state of the link.
4 Delete analyses and analysis components (RIR, RDD, RRI, RRD).
1. Search the digit analyses of route 1500.
ZRIR:ROU=1500;
DX 200 LAB 1998-12-13 11:25:30
TREE= 2 ATYPE=N TON=NAT

DIGITS AL NBR RT CT SP NL RC DEST CHI CNT SDEST
3911 0 1500 ROU NC 1 0 APR 53 6 N 53
AL NBR RT CT SP NL RC DEST CHI CNT SDEST
1 1501 ROU NC 1 0 APR 53 6 N 54
2. Delete all the analyses of AR01.

ZRDD:TREE=2,TON=NAT,DIG=3911;
3. Interrogate the digit analysis components of the exchange and their character-
istics.
ZRIL:NDEST=ACCESSROUTER;
62 Id:0900d80580570d46 DN98905095
Issue 7-0
DX 200 LAB 1998-12-13 11:25:40

NAME OF DESTINATION: ACCESSROUTER DEST: 53
NAL TCR CNP PRI NL ADD IND PA IA EC CDRS

1 N N ORD 0 Y 54 N N N 0
DESTINATION SSET = 0
DTYPE DSTATE PRESTR PPERC PSDEST PNSDEST PCHI

A A N - - - -
ALT SPCH QA NSDEST SDEST SDTYPE SRESTR

0 0 N AR01 53 A N
CHI: 6
CORG NCHA:
0 ACCESSROUTER
ALT SPCH QA NSDEST SDEST SDTYPE SRESTR

1 0 N AR02 54 A N
CHI: 6
CORG NCHA:
0 ACCESSROUTER
COMMAND EXECUTED
4. Delete the destination ACCESSROUTER.

ZRDD:NDEST=ACCESSROUTER;
5. Interrogate the subdestination.
ZRIL:NSDEST=AR01;
DX 200 LAB 1998-12-13 11:25:43

NAME OF SUBDESTINATION: AR01 SDEST: 53
CT SP AR RC RT RNBR SRCL MNL

NC 1 - APR ROU 1500 N 0
COMMAND EXECUTED
6. Delete the subdestination.

ZRDD:NSDEST=AR01;
7. Interrogate the route on the basis of the route number (1500).
ZRRI:GSW:ROU=1500;
DN98905095 Id:0900d80580570d46 63
Issue 7-0
DX 200 LAB 1998-12-13 11:25:46

1500 EXT OMPF0 1 - - N N N N - UNK N N


AICR PNR RNPR RFCL

- - - -
FCL
-
COMMAND EXECUTED
8. Delete the route 1500.

ZRRD:GSW:ROU=1500;
5 Delete the call number and supplementary services (SDO, SDD, SAI, SAD).
1. Interrogate the call number of the circuit group (AR01).

ZSDO:NCGR=AR01;
ROUTING DATA BASED OF CIRCUIT GROUPS
CGR NCGR CALL NUMBER NBR OF SIGNIFICANT DIGITS RZI

1200 AR01 039110 3 0
COMMAND EXECUTED
2. Delete the call number.

ZSDD:NCGR=AR01;
3. Interrogate the supplementary services of the circuit group (AR01) of the digital
branch exchange.
ZSAI:NCGR=AR01;

CGR = 1200
NCGR = AR01
COMMAND EXECUTED
4. Delete the supplementary services of the circuit group.

ZSAD:NCGR=AR01;
64 Id:0900d80580570d46 DN98905095
Issue 7-0
5. Interrogate the supplementary services of the digital branch exchange interface

(PBXI).
ZSAI:PBXI=ACCESSROUTER;
DX 200 LAB 1998-12-13 11:25:52

PBXI = ACCESSROUTER
INDEX OF SUPPLEMENTARY SERVICES = 54
COMMAND EXECUTED
6. Delete the supplementary services of the branch exchange interface.

ZSAD:PBXI=ACCESSROUTER;
6 Delete the circuit group (CEC, RCI, RCD).
1. Set the circuits to 'not used' state.
ZCEC:CRCT=92-1&&-15&-17&&-31&94-1&&-15&-17&&-31:BA;
ZCEC:CRCT=92-1&&-15&-17&&-31&94-1&&-15&-17&&-31:NU;
The execution output shows all the circuits and their new state.
2. Interrogate the features of the circuit group AR01. The following command also
lists all the circuit groups of the exchange. Use this command to verify that the
circuits are in the 'not used' state.
ZRCI:SEA=3:NCGR=AR01:PRINT=4;
3. Delete the circuit group.
ZRCD:NCGR=AR01;
7 Delete the link (DSP, DSI).
1. Interrogate the link data.
ZDSI:NAME=PRA01;

----- --- ------- ----------- --------------- ---------- -------
PRA01 19 P NETW 92-16 PAU-0 1 0 4038H 64 20-08
COMMAND EXECUTED
2. Delete the link.

ZDSD:PRA01;
DN98905095 Id:0900d80580570d46 65
Issue 7-0
Configuring supplementary services with D-channel D-Channel Signalling
signalling
9 Configuring supplementary services with D-

channel signalling
Purpose
There are various supplementary services available for the DSS1 and the DPNSS1 sig-
nalling systems. They are created for the PBX circuit groups.
g This is an introduction to D-channel supplementary services. For full activation instruc-

tions, see customer-specific feature documentation.
The following supplementary services are not available with 23B+D:

Closed User Group (CUG)
Advice of Charge (AOC)
Call Forwarding (CF)
Call Completion to Busy Subscriber (CCBS), Call Completion on No Reply (CCNR)
Private Numbering Plan (PNP) (for description, see MobileCentrex)
User-to-User Signalling (UUS)
g Private Numbering Plan (PNP) supplementary service is used with Mobile Centrex and
it functions with DPNSS1 and DSS1 but is not supported by 23B+D. When using PNP,
the subscriber can use a short number in dialling to another subscriber of his own PNP.
For further information concerning PNP, see MobileCentrex.
9.1 Configuring Advice of Charge (AOC)

Purpose
Advice of Charge (AOC) is a group of supplementary services which allows the served
user to be informed of usage-based charging information. Advice of Charge at the end
of the call (AOC-E) and during the call (AOC-D) are supported by 30B+D.
There are two modes used with AOC:
functional mode
stimulus mode
In the functional mode, the information is conveyed through a functional protocol, which
consists of a sequence of functional information elements. The user terminal must be
able to analyse and process these information elements.
In the stimulus mode, the information is conveyed via a sequence of stimulus informa-
tion elements. A stimulus information element is either generated as a result of a single
event at the user-network interface or it may contain basic instructions from the network
to be executed by the user. Stimulus information is transmitted to the network through a
keypad information element and to the network-user through a display information
element.
Advice of Charge at the end of the call (AOC-E)supplementary service in PBX
means that the metering pulses or currency information is sent to subscriber A after
the completion of the call. AOC-E can be provisioned to the PBX in the following two
ways:
66 Id:0900d80580570d5a DN98905095
Issue 7-0
D-Channel Signalling Configuring supplementary services with D-channel
signalling
Permanent
For 'Permanent' mode, the charging information is given to the subscriber when
the call is released.
Per-call basis
For 'Per-call basis', the charging information is only given to the subscriber if the
subscriber has requested it via the call setup signalling.
There are two possible cases for call release:
A releases the call
B releases the call
These cases are presented in the following figures.
Figure 10 AOC-E, A releases
Figure 11 AOC-E, B releases

Advice of Charge during the call (AOC-D) supplementary service in PBX means that
the metering pulses or currency information is sent to subscriber A during the
speech phase and after the completion of the call. AOC-D can be provisioned to the
PBX in the following two ways:
Permanent
For 'Permanent' mode, the charging information is given to the subscriber when
the call is answered and when it is released.
Per-call basis
For 'Per-call basis', the charging information is only given to the subscriber if the
subscriber has requested it via the call setup signalling.
An example of sending AOC-D information is shown below with the subscriber
requesting AOC-D during call setup phase (that is, the user has 'Per-call basis'),
receiving AOC-D charging information during the speech phase and again when A
releases the call.
DN98905095 Id:0900d80580570d5a 67
Issue 7-0
signalling
Figure 12 AOC-D
The AOC can also be sent in a Release Complete message. If the MSC receives
release as the first clearing message then the AOC information is sent in the
Release Complete message.
Before you start

This section explains the configuration of AOC.
Functional AOC-D
Off
Per-call basis
Permanent
Functional AOC-E
Off
Per-call basis
Permanent
g It is possible to activate both AOC-D and AOC-E for the subscriber. However, only
AOC-E information will be provided at the completion of the call.
Stimulus AOC-D
Not Supported
Stimulus AOC-E
Valid only when Functional AOC-E is selected for 'Permanent'
Charging information can be sent as a number of metering pulses or in the form of
currency with a currency identifier. It has effects on both the functional AOC-D and AOC-
E, the format of which we select to send. The reason is that both AOC information use
the same format as the charging information.
To create the AOC, first you have to create a text announcement and then a digit
analysis in the announcement tree.
68 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
Steps
1 Create a text announcement (RAC).
ZRAC:SPR=<special route number>,TXIND=<text announcement
index>,TXTEXT=<text announcement contents>;
For an example of creating the supplementary service AOC-E in stimulus mode, see
Example of AOC-E (stimulus mode).
2 Create the digit analysis in the announcement tree (RDC, WOI).
ZRDC:TREE=<tree>,DIG=<dig>,TON=<ton>:NDEST=<ndest>;
Digits for chargeable calls are 0E109 and for non-chargeable calls 0E101, in which
the first digit specifies the language (0 is the default value), the letter specifies the
type of announcement (E = text), and the three last digits specify the announcement.
The value of the analysis tree can be defined in the PRFILE parameter
ANN_ANAL_TREE. You can check the possible parameter values with the WOI
command. The default value is 48.
ZWOI:0;
in which the syntax is:
ZWOI:<parameter class>;
For further information on creating the analysis, see Announcements overview.
For further information on creating the analysis, see Announcements.
3 Create/connect the AOC-E stimulus mode (SAC).
With the SAC command, the AOC-E stimulus mode is created/connected to the PBX.
ZSAC:NCGR=<name of circuit group>:ACE=2, (LANG=0),
ITE=STI/BOTH;
The parameter LANG is only required if the language has not been defined at an
earlier stage. ACE has value 2 because Stimulus mode requires AOC-E in 'Perma-
nent' mode. ITE can be STI or BOTH. If BOTH is selected, AOC-E functional infor-
mation is also sent to the PBX in addition to the stimulus information. To create the
functional mode AOC-E, use the following syntax and parameters:
ZSAC:NCGR=<name of circuit group>:ACE=1/2, (ITE=FUN/BOTH),
IAO=1/2, (CI=);
The parameter ITE is only required if ACE is set to 2 'Permanent' mode. ITE=FUN
sends the AOC-E in functional mode. ITE=BOTH sends the stimulus AOC-E in
addition to functional information. The parameters IAO, CI, and PFP pertain only to
functional AOC-E information. CI and PFP are needed when IAO is set to value 2
for currency charging information. CI defines the currency identifier and PFP defines
the conversion factor for each metering pulse (that is, charges = PFP x amount of
metering pulses).
To create the functional AOC-D, use the following syntax and parameters:
ZSAC:NCGR=<name of circuit group>:ACD=1/2, IAO=1/2, (CI=);
The parameters CI and PFP are needed when IAO is set to value 2 for currency
charging information. CI defines the currency identifier and PFP defines the conver-
sion factor for each metering pulse (that is, charges = PFP x amount of metering
pulses).
4 Modify supplementary services (SAM).
DN98905095 Id:0900d80580570d5a 69
Issue 7-0
signalling
Use the SAM command to modify the supplementary services. In this case, the
command is used to add the ACE.
ZSAM:NCGR=<circuit group name>:ACE=2,(LANG=0);
Further Information
Example
Example of AOC-E (Functional mode)
The following example is an execution output of creating the supplementary service
AOC-E in Functional mode with per-call basis and with currency as the charging infor-
mation.
ZSAC:CGR=4:ACE=2, IAO=2, PFP=10.00,CI=EURO;
CGR = 4
NCGR = PBXISDN2
CREATED SUPPLEMENTARY SERVICES:

ACE.... PER-CALL BASIS WITH DEFAULT NOT USED
IAO....CURRENCY USED WITH AOC
PFP....PRICE FOR A PULSE: 10.00
CI.....CURRENCY IDENTIFIER: EURO
COMMAND EXECUTED
Example
Example of AOC-D (Functional mode)
The following example is an execution output of creating the supplementary service
AOC-D in Functional mode with 'Permanent' mode and metering pulses as the charging
information.
ZSAC:CGR=5:ACD=1;
CGR = 5
NCGR = PBXISDN3
CREATED SUPPLEMENTARY SERVICES:

ACD....PERMANENT MODE
COMMAND EXECUTED
9.2 Configuring Call Completion to Busy Subscriber (CCBS)

Purpose
CCBS is a supplementary service for the calling subscriber. It is not available with 23B
+D. The basic functionality is as follows:
1. If the called subscriber is busy, subscriber A can request CCBS.
2. The network monitors the destination B to see when it becomes idle.
70 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
3. When B becomes idle, the network waits a moment to ensure that B is not making
an outgoing call. If B does not make an outgoing call, the network automatically
informs A that now the call to destination B is possible.
There are two DSS1 call completion enhancements to the basic CCBS:
CCBS with the calling subscriber being located in a private, public ISDN or GSM
network
CCNR service, which enables the subscriber A to have a call completed to a target
subscriber who is currently not at home or not reachable. CCNR is not applicable to
GSM, it is only applicable between PBX and PBX, or PBX and ISDN.
The services are not available for emergency calls.
In the case of GSM network, the SSAP protocol must be supported between the origin
and the destination networks.
Figure 13 Call completion supplementary services architecture

After the feature has been taken into use, it is possible
to deactivate or interrogate the status of all active CCBS requests with non-CCBS
MSs.
for a wider range of mobile subscribers to use CCBS due to USSD (unstructured
supplementary service data).
for a network operator to monitor SSAP activity in the own network element.
Before you start

The network elements involved in CCBS are the following:
HLR Queues and SSAP connections are implemented in the HLR within Feature
896: Completion of Calls to Busy Subscribers (CCBS) -queueing and SSAP.
In the MSC/VLR, functions are implemented to provide the CCBS possibility and
Recall for subscriber and subscriber monitoring.
From the HLR part, Feature 896: Completion of Calls to Busy Subscribers (CCBS)
Queuing and SSAP describes what is needed in the HLR end to install the feature. The
present instructions mostly describe the installation of the MSC/VLR.
DN98905095 Id:0900d80580570d5a 71
Issue 7-0
signalling
CCBS usually concerns both the MSC and HLR of the calling subscriber, and the MSC
and HLR of the called subscriber, but these network elements may sometimes be the
same for the calling and the called subscriber.
g Using the feature requires that the feature-specific software is installed into the MSC.
9.2.1 Configuring CCBS in the HLR

Purpose
You need to have the CCBS software activated for HLR subscribers before MSC/VLR
configuration.
Steps
1 Check whether CCBS has been activated (WOI).
To check whether Feature 896: Completion of Calls to Busy Subscribers (CCBS)
Queuing and SSAP has been activated, use the following command:
2 Activate CCBS (WOC).
If the feature is not activated, activate it with the following command:
ZWOC:<parameter class>,<parameter number>,<parameter value>;
3 Provision target CCBS (MIM).
If the operator wishes to provision target CCBS to all subscribers, this is done with
the Multiple Subscribers Handling MML commands by creating an IMSI-file.
To use the IMSI-file, use the Home Subscribers Identification Handling MML:
ZMIM:IMSI=<name of the imsifile>:OCCBS=<>, TCCBS=<>;
9.2.2 Activating the CCBS in the MSC

Steps
1 Define PRFILE parameters for CCBS and CCNR (WOC, WOI).
The PRFILE parameters for CCBS and CCNR need to be defined as described in
the feature activation instructions of Feature 234: Completion of Calls to Busy Sub-
scriber, Phase 2.
To activate CCBS or CCNR, use the following command:
ZWOC:<parameter class>,<parameter number>,<parameter value>;
For more information on these parameters, see the feature activation instructions of
Feature 234: Completion of Calls to Busy Subscriber, Phase 2.
Check whether either feature has been activated and is in use in the MSC with the
following command:
2 Set and confirm CCBS supplementary services (MXM, MXO).
Set VLR to allow CCBS supplementary service to subscribers by adding CCBS to
the Supported Supplementary Service list with the following command:
72 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
ZMXM:::CCBS=Y;
To confirm that the CCBS supplementary service is supported, use the MXO
command.
3 Modify circuit group to support CCBS and CCNR (SAM, SAI).
ZSAM:NCGR=<circuit_group_name>:CCBS=Y,CCNR=Y;
For example:
ZSAM:NCGR=DSO02A:CCBS=Y,CCNR=Y;
To confirm, use the following command:
ZSAI:NCGR=<circuit_group_name>;
4 Modify outgoing route to support CCBS and CCNR (RRM, RRI).
ZRRM:ROU=<Route_number>,FCL=CCBS,FCL=CCNR;
For example:
ZRRM:ROU=304,FCL=CCBS,FCL=CCNR;
To confirm, use the following command:
ZRRI:GSW:ROU=<Route_number>;
5 Check parameter 'SSAP_ANAL_TREE' .
Check parameter 'SSAP_ANAL_TREE'. The parameter class is 7
(CALL_CONTROL) and the parameter number is 74. This parameter is used to
define the analysis tree where the destination number is analysed to obtain routing
information for SSAP. Although the default value is 2, this default should not be used
for SSAP connection.
9.3 Configuring user-to-user signalling

Purpose
User-to-User Signalling (UUS) is a supplementary service that allows a subscriber to
send or receive a limited amount of subscriber-generated information (for example,
short messages or activation information of a service) to (or from) another PLMN or PBX
subscriber. Sending the information always takes place in association with a call to a
user, unlike the sending of short messages. Only one of the users needs to activate the
feature. After that all calling parties are able to use the UUS.
g The MS must also support User-to-User Signalling (UUS).
UUS is not available with 23B +D.

The information can be sent and received during the origination of a call, when the user
pushes the 'off hook' button, the calling party can activate the service in the call set-up
phase and send text information, for example, a calling card number. During the release
of a call, when the user pushes the 'on hook' button, all the other users can do the same.
First, the calling subscriber receives an indication that the called party is being informed
of the call, and the remote party's phone starts alerting. The called party can then
choose to automatically send text information to the calling party, for example a
message that the phone cannot be answered because the called party is in a meeting.
The calling party, in turn, can choose to send back a text message, stating that this is a
DN98905095 Id:0900d80580570d5a 73
Issue 7-0
signalling
priority call and the called party should answer. This service is activated by the calling
party when originating the call.
While the connection is established, all parties (calling or called) can choose to activate
the service, after which all users can, for example, send text messages to each other.
The calling user can also activate the service when originating the call.
The information is passed transparently through the network, that is, the text messages
created with these services are sent directly from one user to another. The user can also
be an application, for example, a server sending information (that is, activation informa-
tion of a service) or communicating with another user.
g No separate activation for the UUS needs to be defined. Once the UUS has been
provided for the operator, it is active.
9.3.1 Configuring UUS in the HLR

Steps
1 Manage provisioning of UUS (MSC, MSO).
1. Provision UUS
ZMSC:IMSI=<imsi>:uus=Y/N;
2. Print subscriber provisioned services
ZMSO:IMSI=<imsi>;
2 Manage HLR and PLMN parameters (MJS, MJP, MJT).
1. Create Not Allowed Service Code Modification
If sending of the UUS information needs to be prevented, create 'Not Allowed
Service Code Modification' with the MJS command and with the NSS parameter.
This NSS parameter specifies the supplementary service that is not transferred
when the subscriber roams to the defined PLMN.
ZMJS:NAME=<name>:NSS=<uus>;
2. Output PLMN parameters
Output PLMN Parameters with the MJP command.
ZMJP:NAME=<name>;
3. Delete 'Not Allowed Service Code Modification'
If you need to remove the prevention of the UUS information, delete 'Not Allowed
Service Code Modificaction' with the MJT command. The MJT command deletes
the code that prevents a supplementary service from being transferred when the
subscriber roams from one PLMN to another.
ZMJT:NAME=<name>:NSS=<uus>;
3 Filter subscribers (MHH).
Filter subscribers in the HLR if necessary. The MHH command in the HLR is used for
filtering subscribers according to the properties of UUS subscription information.
ZMHH:IMSIFILE=<name>::::SSLIST=UUS;
74 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
9.3.2 Configuring UUS in the MSC/VLR

Steps
1 Configure route handling (RRM, RRI).
1. Set the UUS supported
ZRRM:ROU=number,FCL=uus;
2. Interrogate route
ZRRI:GSW:ROU=rou;
2 Configure charging administration (GTM, GTI).
1. Set CDR generation parameter
Set a CDR generation parameter for UUS with the GTM command. A parameter
is used to decide which supplementary service requires an SS-CDR.
The operator may set the UUS as chargeable when providing it for the sub-
scriber. The usage of the UUS can be charged according to transferred
messages or for transferred amount of data, if the UUS is set to be chargeable.
For the UUS, there are two SS-CDRs. Both SS-CDRs are generated for the
subscriber who has activated the UUS service(s). The first one collects the infor-
mation when the UUS service has been activated/rejected. The second CDR is
generated when the call is released. It contains information on the amount of the
transferred data and the amount of messages transferred. The information is
collected per one UUS service.
A CDR is not generated separately for each transferred UUIE, but a CDR is gen-
erated for each UUS (1, 2, and 3). The billing center ensures that the transferred
UUS messages and/or the octet counts per UUS service are available for the
charging. The operator may choose whether the charging is based on the trans-
ferred amount of octets or on transferred UUI messages.
ZGTM:SUPS,uus:type,cdr;
2. Interrogate charging parameters
ZGTI:CDR:SUPS,uus;
3 Configure PBX interface (SAC).
Create Digital Branch Exhange Supplementary Services with the SAC command.
1. For UUS1:
ZSAC:NCGR=ncgr:uus=value;
(UUS value can be 0, 1, or 2)
2. For UUS2 and UUS3:
ZSAC:NCGR=ncgr:uus=value;
(UUS value can be Y or N)
4 Display Digital Branch Exchange Supplementary Service (SAI).
ZSAI;
5 Modify Digital Branch Exhange Supplementary Services (SAM).
1. For UUS1:
ZSAM:NCGR=ncgr:UUS=value;
(UUS value can be 0, 1, or 2)
2. For UUS2 and UUS3:
ZSAM:NCGR=ncgr:UUS=value;
(UUS value can be Y or N)
DN98905095 Id:0900d80580570d5a 75
Issue 7-0
signalling
6 Delete digital branch exchange supplementary services (SAD).

ZSAD:NCGR=<ncgr>
7 Configuring VLR (MXM, MXO, MVS).
1. Modify VLR parameters
ZMXM::::uus=Y/N;
2. Output VLR parameters
ZMXO:;
3. Print subscriber data
To print subscriber's data, use the following command. It also displays UUS
services provisioned for the subscriber.
ZMVS:IMSI=imsi:BSERV=bserv;
Further Information
If the you want to use UUS, you need to have a cellular phone which supports UUS.
The standardised MMI for the MS subcriber is the following:
Supplementary Service UUS

Service Code Required
UUS Service 1 361 R
UUS Service 2 362 R
UUS Service 3 363 R
all UUS Services 360 R
Table 3 Man-Machine Interface for the MS Subscriber
If UUS is to be activated when originating a call, enter:

' * 36X * R # <called number> SEND'
(X indicates the requested UUS service)
'UUS required' option
For the 'UUS required' option two values are defined:
R=0 UUS not required
R=1 UUS required
g If the 'UUS required' option is requested for a call, the call will only be established if
the requested UUS capabilities are available.
If the 'UUS required' option is not contained in an activation request, UUS is acti-
vated without the UUS required option.
9.4 Configuring calling line identification (CLI)

Purpose
The functionalities of calling line identification include CLI screening, CLI checking,
CLIR handling, CLI modification, and CLIP handling. The order in which these pro-
cesses take place is presented in the following figure:
76 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
Figure 14 Calling Line Identification

For further information on CLI modification, see the feature description of Feature 827:
CLI Handling Improvement. All the other phases are described in this section.
9.4.1 CLI screening in the MSC

Purpose
CLI screening is a part of the ISDN Calling Line Identification supplementary service
(CLIP). The purpose of screening is to check that the calling line identity (CLI) received
from the PBX (or any other equipment using DPNSS1 or DSS1 signalling) is valid. After
the screening, the valid CLI is sent forward. The purpose of CLI screening is that the
called party can be sure that the CLI received can be used to call back (if the calling party
wants to show its CLI and the called party has subscribed to CLIP). This functionality
applies to both DSS1 and DPNSS1. The screening function is defined in ETS 300 092
1 Integrated Services Digital Network (ISDN); Calling Line Identification for 30B+D and
in ANSI T1.625 for 23B+D.
Steps
1 Interrogate NDC, national and international prefixes, CC, and the extension range
(WWI).
Screening is done according to the definitions in the MSC and they are in line with
the E.164, which is the ISDN numbering plan. It means that the MSC must know the
national destination code (NDC), national and international prefixes, the country
code (CC), and the extension range to be able to perform the function. These defi-
nitions can be interrogated with the WWI command.
2 Interrogate national significant number (SDO).
The national significant number (NSN) is defined in two parts (body and extension
range). These definitions can be interrogated with the SDO command.
Screening means that the CLI received is compared against these definitions to
determine the validity.
The operator can choose whether to use screening or not when configuring the PBX
interface.
DN98905095 Id:0900d80580570d5a 77
Issue 7-0
signalling
9.4.2 Configuring CLI screening

Steps
1 Check call routing.
First, you need to find out how the calls are routed to the PBX interface: what is the
national prefix, national destination code (NDC), and national significant number
(NSN) with the extension range.
2 Define the call number of the PBX (SDC).
ZSDC:NCGR=<circuit group name>,AREA=<national
prefix+NDC>,CALL=<default number>,SID=<number of digits which
is common to all extensions>,RZI=<routing zone index for
emergency and service numbers>;
3 Define subnumber range (SAC).
Define the subnumber range for extensions with the command:
subnumber>,LAS=<last subnumber>;
Further Information
Example
The PBX network, for example, has the attendant number 51121. The extension
numbers start from 20000 and go up to 69999. The common part for all numbers is 511
when dialling from the PSTN or PLMN. So the number of significant digits in the atten-
dant number is 3. The national prefix is 0 and the network code is 9. To configure the
MSC correctly in such a case, give the following commands:
ZSDC:NCGR=NOKIAPBX,AREA=09,CALL=51121,SID=3,RZI=0;
ZSAC:NCGR=NOKIAPBX:FIS=20000,LAS=69999;
If screening does not succeed, the called party receives 0951121 as CLI.
9.4.3 Modifying CLI screening

Steps
1 Modify CLI screening (CPM).
ZCPM:NCCP=<nccp>:::CLIS=<Y/N>;
2 Modify CLI screening for statistics (CPM).
ZCPM:NCCP=<nccp>:::CLIT=<Y/N>;
3 Modify CLI screening for call number (CPM).
ZCPM:NCCP=<nccp>:::CALLNS=Y/N>;
9.4.4 Configuring CLIR

Purpose
Calling Line Identification Restriction (CLIR) supplementary service is a service with
which the service provider can offer the subscriber the option to prevent the presentation
of the calling number to the called party. The options are the following:
78 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
subscription option permanent, allowed, or restricted. When allowed, the CLI is

always shown to the called party and when restricted, the CLI is never shown to the
called party by the terminating MSC, except in case of CLIR override.
subscription option temporary, that is, the PBX extension can control the presenta-
tion of CLI on a per call basis.
When opting for the temporary mode, the subscriber must choose one of the following
two presentation modes as the default:
presentation restricted
presentation not restricted
In the temporary mode, the subscriber can control the presentation of his number to the
called party on a per call basis.
The subscriber can change the default value by giving a code in front of the called
number which allows action against the default value.
The values are the following:
0 NOT ACTIVE allowed
1 PERMANENT MODE restricted
2 TEMPORARY MODE allowed
3 TEMPORARY MODE restricted
If the service is not active, the indication of the calling number is permanently allowed
and the number is shown. If the permanent mode is active, the indication is restricted
and the number is not shown. In the temporary mode the presentation is either allowed
or restricted.
The operator can create CLIR control to preanalysis so that the subscriber can, for
example, dial a prefix before the called number and thus opt for either presentation
allowed or restricted. The standard GSM CLIR prefixes are the following:
*31# = CLIR suppression, presentation allowed
#31# = CLIR invocation, presentation restricted
Any other digit sequences can be used for CLIR prefix and they can be applied to both
DSS1 and DPNSS1.
The following table is a presentation of how CLIR works in a table format.
Subscriber Option Information received from the signal- Action

ling
Allowed (CLIR=0) - allowed
presentation restricted allowed
presentation allowed allowed
CLIR Invoke prefix (for example #31#) allowed
CLIR Suppress prefix (for example *31#) allowed
Restricted - restricted
presentation restricted restricted
presentation allowed restricted
Table 4 CLIR
DN98905095 Id:0900d80580570d5a 79
Issue 7-0
signalling
Subscriber Option Information received from the signal- Action

ling
CLIR Invoke prefix (for example #31#) restricted
CLIR Suppress prefix (for example *31#) restricted
Temporary mode, - restricted
default restricted presentation restricted restricted
Temporary mode, - allowed
default allowed presentation restricted restricted
Table 4 CLIR (Cont.)
Steps
1 Create CLIR control to preanalysis .
Create CLIR control to preanalysis in normal side in the order shown.
1. CLIR suppression 'restricted'
ZRWC:<call origin>,<type of number>,<numbering
plan>,<dialled digits>:<analysis result identifier>:;
For example:
CLIR suppression on temporary mode restricted. If *31# is received from the
subscriber, the CLI of the A party is shown to the B party.
ZRWC:TOC,2,3,B31C:STOP:;
ZRWM:TOC,2,3,B31C:PREANA:FEAT=SUPCLIR,REML=4;
2. CLIR invocation allowed
ZRWC:<call origin>,<type of number>,<numbering
plan>,<dialled digits>:<analysis result identifier>:;
For example:
CLIR invocation on temporary mode allowed. If #31# is received from the sub-
scriber, the CLI of the A party is not shown to the B party:
ZRWC:TOC,2,3,C31C:STOP:;
ZRWM:TOC,2,3,C31C:PREANA:FEAT=INVCLIR,REML=4;
9.4.5 Configuring CLIP

Purpose
Calling Line Identification Presentation (CLIP) supplementary service in a PBX is a
service provided for the called party. CLIP makes it possible to indicate the line identity
of the PBX extension to the called party. Depending on whether the service is active or
not, the number of the calling party is either shown to the called party or not.
80 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
CLIP can have values Yes (Y) and No (N). If the value is N, the CLI is not sent to the
PBX. If the value is Y, the presentation status is either allowed, which means that the
CLI is sent to the PBX, or restricted, in which case CLIR override can be either active or
not active. If CLIR override is active (Y), the CLI is sent to the PBX and if CLIR override
is not active (N), the CLI is not sent to the PBX. This process is presented in the following
figure:
Figure 15 CLIP
CLIP is functional with both DPNSS1 and DSS1.
The SAC command is used to define whether the CLI is sent to the PBX or not.
Steps
1 Send CLI to PBX (SAC).
ZSAC:<digital branch exchange name>:<digital branch exchange
supplementary service name>;
For example:
The CLI is sent to the PBX if the presentation state allows it.
ZSAC:PBXI=HYPOCGR:CLIP=Y;
2 Do not send CLI to PBX (SAC).
The SAC command is used to define whether CLI is sent to PBX or not.
ZSAC:<digital branch exchange name>:<digital branch exchange
supplementary service name>;
For example:
ZSAC:PBXI=HYPOCGR:CLIP=N;
9.4.6 Configuring CLIR override

Purpose
Override category is an additional functionality to CLIP. If the called subscriber has the
override category active, the CLI of the calling subscriber is shown regardless of
possible barring set by the calling subscriber.
DN98905095 Id:0900d80580570d5a 81
Issue 7-0
signalling
Before you start

The RRI command can be used to interrogate the name of the outgoing call control
parameter set (NCCP), which is needed for defining CLIR override. The syntax is:
ZRRI:<switch>:ROU=<route number>;
For example:
Interrogate the name of the outgoing call control parameter set for the GSW switch when
the route number is 2100.
ZRRI:GSW:ROU=2100;
Steps
1 Send CLI to PBX (CPF).
With the CPF command, you can modify the outgoing call control parameter set, that
is override CLIR.
ZCPF:NCCP=<name of call control parameter set>:::<operator
centrex>;
The CLI is sent to the PBX even if the presentation status is 'restricted'.
For example:
ZCPF:NCCP=OMPM7:::OPCX=Y;
2 Do not send CLI to PBX (CPF).
With the CPF command, you can modify the outgoing call control parameter set, that
is override CLIR.
ZCPF:NCCP=<name of call control parameter set>:::<operator
centrex>;
The CLI is not sent to the PBX.
For example:
ZCPF:NCCP=OMPM7:::OPCX=N;
9.5 Configuring direct dialling-in (DDI)

Purpose
The supplementary service called the Direct Dialling-in (DDI) allows extensions to be
reached directly by dialling the extension number without the assistance of the PBX
operator. DDI functions with both the D-channel signalling systems, DPNSS1 and DSS1
(30B+D and 23 B+D). The following figure shows how DDI functions:
Figure 16 DDI
82 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
DDI can have the values yes (Y) and no (N). When the value is Y, the B-number is sent,
and when the value is N, the call number is sent.
Steps
1 Define DDI for a PBX (SAC).
ZSAC:<digital branch exchange interface name>:<digital branch
exchange supplementary service type>;
For example:
Define DDI for a PBX. The PBX interface name is HYPOCGR.
ZSAC:PBXI=HYPOCGR:DDI=Y;
9.6 Configuring call forwarding

Purpose
Both DPNSS1 and DSS1 support call forwarding. The terminating PBX can instruct the
MSC to do the forwarding, that is, the MSC is the forwarding point. This means that the
circuit between the MSC and the PBX is released and is optimising the usage of the
circuits at the interface. The call forwarding for the DPNSS1 is defined in the BTNR 188
and for the DSS1 30B+D in ETS 300 207-1. The following table describes the possible
call forwarding reasons in the call forwarding request and the corresponding event code:
Event DPNSS1 Supplementary DSS1 Call forward-

code service string in ing reason in
DPNSS1 DSS1
CFU 100DH X DVT-I X CFU
CFB 1011H X DVT-B X CFB
CFNA 1013H X DVT-R X CFNR
CDI 102CH X CDIMMEDI-
ATE
CDA 102EH X CDALERT-
ING
Night 1027H X NS-DVT
service
Table 5 Possible call forwarding reasons in the call forwarding request and the cor-
responding event code
X = possible
Call forwarding is an optional feature for DSS1 30B+D, like multiple call forwarding. In
order to get the forwarding to work, an end-of-selection (EOS) analysis must be created
or modified for each event code and the result should be a number analysis in the
analysis tree used for the forwarded-to numbers. Some signallings, DPNSS1 and DSS1
30B+D of the ones covered by this document, support a notification to the calling party
that a call forwarding has happened. It is possible to give an announcement. These are
also controlled with the EOS analysis. First check if the EOS analysis already exists for
DN98905095 Id:0900d80580570d5a 83
Issue 7-0
signalling
the event code in the desired result group. The result group is one of the parameters in
the incoming call control parameter set, which is attached to the circuit group.
Steps
1 Interrogate circuit group (RCI).
ZRCI:SEA=3:NCGR=<name of the circuit group>;
You can see the name of the parameter set in the field NCCP in the command
output.
2 Check the result group (CPI).
Check the result group defined in the incoming call control parameter set with the
following command:
ZCPI:IN:NCCP=<name of the parameter set>;
You can find the value of the result group in the field RESULT GROUP.
3 Check if analysis exists (RXI).
Check if the analysis exists for the event code in the result group, by entering the
command:
ZRXI:RESGR=<number of the result group>,CAUSE=<event code
value>;
4 Create analysis (RXC).
If the command output is empty, the analysis is missing and has to be created.
ZRXC:<event code value>:<number of the result group>,<analysis
result>,<analysis tree>,<charging origin>,<notification for
i/c signalling>,<timeslot for tone>,<announcement
number>,<announcement charging>;
5 Modify result (RXM).
If the output indicates an inadequate result, you can modify the result so that it
contains the appropriate result with the command:
ZRXM:<number of the result group>:<event code value>:<analysis
result>,<analysis tree>,<charging origin>,<notification for
i/c signalling>,<timeslot for tone>,<announcement
number>,<announcement charging>;
6 Set call control parameter to a specific value (CPM).
Purpose
Remember to check every possible event code which can be received and every
possible result group from which the calls can be originated and led to the interface.
The PBX-originated calls can include an indication that the call has been forwarded
inside the PBX or a private network. This indication is supported in both DPNSS1
and DSS1. However, the call forwarding counter is not supported in DPNSS1. It is,
however, possible to set a value or change the value for the call forwarding counter
if the forwarded call is received. The parameters are in the incoming call control
parameter set attached to the circuit group. The following table describes how the
settings are applied.
84 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
Call forward- Call forward- Modification New call for- Call forward-
ing indicated ing counter parameter in warding ing value
in setup in setup incoming call counter value used by call
message message control parame- control
ter set
N X X X 0
Y N N X 5
Y Y N X As received
from the
incoming sig-
nalling
Y N Y 0-5 0-5
Y Y Y 0-5 0-5
Table 6 Call forwarding
X = not relevant
Y = yes
N = no
To set the counter to a specific value, give the following command:
ZCPM:NCCP=<name of the parameter
set>::::::MODCFC=Y/N,NEWCFC=<new value from 0 to 5>;
For an example, see Example of changing the call forwarding counter for DPNSS1.
7 Check maximum number of call forwardings (WOI).
Purpose
The maximum number of call forwardings in DSS1 is 5, which is also the limit in GSM
specification. However, GSM specifications allow one extra call forwarding which is
normally directed to a voice mail. There is no limit in DPNSS1 specifications. You
can check the maximum number of call forwardings allowed with the following
command:
ZWOI:17;
8 Change maximum number (WOC).
The MAX_NBR_OF_CALL_DIVER parameter holds the maximum value. You can
change it with the following command:
ZWOC:17,3,<new value>;
9 Set parameter for partial rerouting (SAC, CGR).
There is a separate parameter for Partial Rerouting. The parameter gives a possi-
bility to set the partial Rerouting supplementary service provisioned for some PBX
circuit group. This parameter is used with both DSS1 and DPNSS1 signallings. If the
PRR is set to N, PBX-originated Partial Rerouting attemps are rejected by MSC.
The parameter is set with one of the following commands:
1. Set the parameter with the SAC command:
ZSAC:NCGR=<name_of_the_cgr>
DN98905095 Id:0900d80580570d5a 85
Issue 7-0
signalling
2. Set the parameter with the CGR command:

ZCGR=<number_of_the_cgr>:PRR=<Y/N>;
Further Information
Example
Example for creating a result for an event code
This example assumes that the name of the circuit group is PSTNISUP. A call originat-
ing from this circuit group and terminating to a PBX can be instructed to be forwarded
by the terminating PBX. The example uses event code value 100DH, which is the value
for the CFU. The analysis result is set to number analysis to be executed in analysis tree
20, The charging origin to be used is 0, and a notification to the called party is to be
given.
1. Check the name of the incoming call control set defined for circuit group PSTNISUP
with the following command:
ZRCI:SEA=3:NCGR=PSTNISUP:PRINT=2;
The name of the incoming call control parameter set is BASICINPSTNPBX.
2. Check the value of the result group with the following command:
ZCPI:IN:NCCP=BASICINPSTNPBX;
The value is 5.
3. Check that all the parameters for checking the end-of-selection are found:
ZRXI:RESGR=5,CAUSE=100D;
The analysis is empty, and it must be created.
4. Create the EOS analysis with the following command:
ZRXC:100D:ALL,CMANAL,20,0,NOTIF,,;
This command creates the result for every result group. If a different kind of handling
is needed for a certain result group, it can be modified with the RXM command. The
phases 3 and 4 should be repeated for every possible event code and all the phases
should be repeated for every result group used in the MSC.
Example
Example of changing the call forwarding counter for DPNSS1
The following example sets the value of the call forwarding counter to 1 if the incoming
call from the PBX connected with the DPNSS1 is received with a forwarding indication
in the ISRM/SSRM sequence. The name of the DPNSS1 circuit group is assumed to be
CALLCENTER.
1. Check the name of the incoming call control parameter set:
ZRCI:SEA=3:NCGR=CALLCENTER:PRINT=2;
The name of the incoming call control parameter set is BASICINPSTNPBX.
2. Modify the counter to value 1.
ZCPM:NCCP=BASICINPSTNPBX::::::MODCFC=Y,NEWCFC=1;
9.7 Defining tones with D-channels

Purpose
If the PBX cannot give tones or if the tones are required to be given from the MSC, it is
possible to define them to be given by the MSC. The setting is circuit group-specific. The
parameter controls the following tones:
Dial tone when a call setup is received without digits (does not work with DPNSS1).
86 Id:0900d80580570d5a DN98905095
Issue 7-0
signalling
Ringing tone for the PBX-terminated call. It is required that an ALERTING message,
when DSS1 is used, and a NAM message, when DPNSS1 is used, is received
before the tone is connected.
Release tone. This tone is given when the call is cleared by other party than the
PBX.
The connection of a tone is also controlled by the bearer service, which is used when
setting up the call. Tones are connected when information transfer capability is either
speech or 3.1kHz. If the tone option is set when using DSS1, a Progress Indicator with
value #8 ('in-band information of appropriate pattern now available') is included in an
appropriate signalling message. You can set the tone option with the following com-
mands:
Steps
1 Set tone option by circuit group name (SAM).
ZSAM:NCGR=<circuit group name>:COTO=Y/N;
2 Set tone option by circuit group number (SAM).
ZSAM:CGR=<circuit group number>:COTO=Y/N;
9.8 Configuring charging based on distance

Purpose
The service called Charging based on distance allows the operator to define the
charging of a call according to the distance between the calling and the called party.
Charging of the call depends, on the location of both the calling party and the called
party.
Each cell is attached to a charging area. The distance between the calling and the called
party can be defined by charging areas for mobile calls. The number of charging areas
is 9999. If the charging area of the called party is not reachable, the operator can use
the default charging area of a PLMN. A charging area can also be defined for a PBX. If
Advice of Charge (AOC) has been provisioned for a subscriber, the tariff used can be
displayed for the calling subscriber by using the AOC parameters.
The following figure shows the basic principle of charging based on distance:
DN98905095 Id:0900d80580570d5a 87
Issue 7-0
signalling
Figure 17 Charging based on distance

For further information on charging based on distance, see the feature description of
Feature 606: Charging based on distance.
This section explains how to create, modify, and display charging areas for a PBX.
Steps
1 Create charging area for PBX (SAC).
ZSAC:NCGR=<circuit group name>:CA=<charging area>;
ZSAC:CGR=<circuit group number>:CA=<charging area>;
2 Modify charging area (SAM).
ZSAM:NCGR=<circuit group name>:CA=<charging area>;
ZSAM:CGR=<circuit group number>:CA=<charging area>;
3 Display supplementary services (SAI).
ZSAI;
88 Id:0900d80580570d5a DN98905095
Issue 7-0
D-Channel Signalling Configuring an emergency/service call with D-channel
signalling
10 Configuring an emergency/service call with

D-channel signalling
Purpose
The configuration of emergency calls or service number calls is similar to the configura-
tion of mobiles. The only difference is the routing zone index, which is given when
creating the call number for the interface. The routing zone index for mobile-originated
calls is attached to the BSC configuration. DSS1 and DPNSS1 do not have a separate
setup message for emergency calls contrary to the GSM specification. The nature of the
call is defined in the dialling preanalysis. The final routing number is indexed with the
service type from the preanalysis and the routing zone index from the call number defi-
nition.
Before you start

To configure an emergency call, you need to create a routing zone index, preanalysis,
and an area service number. The required commands are presented below.
Steps
1 Create the preanalysis (RWC).
ZRWC:<call origin>,<type of number>,<numbering plan>,<dialled
digit>:<analysis result identifier>,<numbering plan of
analysis result>,<call characteristics>,<service type>;
2 Create the routing zone index (SDO).
The routing zone index is assumed to be given when the call number was defined.
The value can be checked with the SDOcommand.
ZSDO:NCGR=<circuit group name>;
or
ZSDO:CGR=<circuit group number>;
3 Define the final routing number (RUA).
ZRUA:SN=<area service number>,ST=<service type>, RZ=<routing
zone>,TON=<type of number>;
Further information
Example Configuration example for originating emergency call/service number
call
The following example assumes that the number for the emergency call is 112, the type
of number for the number is unknown, and the numbering plan is ISDN/Telephony. If the
definition is made for DPNSS1-originated calls, the type of number and numbering plan
must be set to 'not exist' value because the signalling does not carry the corresponding
information explicitly. The final routing number is 358912345678 and the type of number
is international. The routing zone index is 0 and the service type is 1.
1 Create the preanalysis with the following command:
ZRWC:TOC,2,3,112:CONT,2,EMERG,1;
The routing zone index is assumed to be given when the call number was defined.
2 Define the final routing number with the following command:
DN98905095 Id:0900d80580570d5d 89
Issue 7-0
Configuring an emergency/service call with D-channel D-Channel Signalling
signalling
ZRUA:SN=358912345678,ST=1,RZ=0,TON=I;
If a separate analysis tree for the final routing number is required, it can be defined
here. Otherwise, the analysis tree defined to the circuit group is used.
90 Id:0900d80580570d5d DN98905095
Issue 7-0
D-Channel Signalling Configuring IN services with D-channel signalling
11 Configuring IN services with D-channel sig-

nalling
Purpose
IN services can be used with originating and terminating DSS1/DPNSS1 calls. The
service set is defined in supplementary service records. Other possible places for
defining the IN service set are, for example, subdestination and destination as a result
of the number analysis for dialled digits. The service set for the originating basic call
state model (OBCSM) and the terminating basic call state model (TBCSM) is defined
with the SAM command with the NCGR or CGR parameters. Although the service set can
also be defined in circuit group data, it is not taken into account and it is relevant only in
trunk-originated calls.
Steps
1 Define a service set (SAM).
ZSAM:NCGR=<circuit group name>:SSET=<service set>;
See Digit Analysis Modification MML for setting the service set to the subdestination
and destination. The triggers are defined with the RGC command and the service set
with the RGScommand. For example, the value of the SKEY is set differently than
that of the mobile subscriber. It may also be necessary to change or create the end-
of-selection (EOS) analysis for event and clear codes, and to create a new number
analysis (for example, for Connect operation received from the Service Control
Point).
For further information concerning IN services, see Core INAP in MSC/VLR/SSPand
HLR.
Example
Configuration example of IN services
The following example defines a service set called BCSMSET to a circuit group called
HYPOCGR. It is assumed that the supplementary service records for the interface have
already been defined.
ZSAM:NCGR=HYPOCGR:SSET= number of BCSMSET;
DN98905095 Id:0900d80580570d60 91
Issue 7-0
Values of the LSI parameter D-Channel Signalling
12 Values of the LSI parameter

Restart procedure in Signalling Remarks
use
PRA01 ON ETS 300 102-1 Default
PRA02 OFF ETS 300 102-1 Needed with PRA loop
PRA03 ON, without Channel ID, ETS 300 102-1 Needed with Meridian PBX
all interfaces
PRA04 ON ETS 300 403-1 Feature 904: Support of
New Data Services in
Primary Rate Access in
M9
PRA05 ON ETS 300 102-1 Does not support
FACILITY IE
PRA06 ON ANSI T1. 607/ Feature 840: 23B+D
ANSI T1. 607a version 1 in M9
PRA07 ON ETS 300 102-1 Feature 821: ISDN V.120
and GSM interworking v1
in M8. Does not send LLC
IE. Needed with Access
Router and V.120.
PRA08 ON ETS 300 102-1 Does not send NOTIFY
message. Needed by
Sonofon & Mobilix.
PRA09 ON ETS 300 102-1 Does not send STATUS
message. Needed with
Eurotel.
PRA10 ON, without Channel ID, ETS 300 403-1 Needed with Meridian
all interfaces PBX.
PRA11 ON ETS 300 403-1 PRA04+PRA09
PRA12 ON ETS 300 403-1 PRA04+PRA08 used by
Sonofon & Mobilix.
PRA13 OFF ETS 3004031 Feature 904: Support of
M9, Restart procedure is
not supported. Used by
Omnitel
Table 7 Additional information on the values of the LSI parameter
92 Id:0900d80580570d66 DN98905095
Issue 7-0
D-Channel Signalling Values of the LSI parameter
Restart procedure in Signalling Remarks

use
PRA14 ON ETS 3001021 Default, Channel Identifi-
cation extension bit (octet
3.3) is set to '0b0' in
Restart Acknowledge
Message. Used by
Omnitel (Italy).
PRA16 ON ETS 3004031 Feature 904: Support of
M9, Channel Identification
extension bit (octet 3.3) is
set to '0b0' in Restart
Acknowledge message.
Used by Omnitel (Italy).
Table 7 Additional information on the values of the LSI parameter (Cont.)
DN98905095 Id:0900d80580570d66 93
Issue 7-0

D Channel Signalling

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D Channel Signalling

Uploaded by

Copyright:

Available Formats

D-Channel Signalling

f Important Notice on Product Safety

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

3 Planning D-channel configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Configuring the DSS1 30B+D interface . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 Configuring the DSS1 23B+D interface . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.12 Creating/modifying the End-of-Selection (EOS) analysis for incoming sig-

6 Configuring a DPNSS1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7 Controlling the D-channel interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

8 Deleting the D-channel interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

9 Configuring supplementary services with D-channel signalling . . . . . . . 66

9.8 Configuring charging based on distance . . . . . . . . . . . . . . . . . . . . . . . . 87

10 Configuring an emergency/service call with D-channel signalling . . . . . 89

11 Configuring IN services with D-channel signalling . . . . . . . . . . . . . . . . . 91

12 Values of the LSI parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Changes made between issues 6-0 and 5-0

Changes made between issues 50 and 40

Changes made between issues 40 and 30

Changes made between issues 30 and 20

2.1 DPNSS1, DSS1 30B+D and 23B+D

DPNSS DSS1 30 B+D 23B +D

Table 1 Summary of the main properties of the three signalling systems

Connecting a PBX to the network

E1 vs. T1 channel structure

2.2 DSS1 signalling

Figure 1 Successful call/DSS1

2.2.1 Layer structure of OSI model

Figure 2 Layering of DSS1

2.2.3 ISDN services of DSS1

The DSS1 must be capable of transparent transformation of an information element

2.3 DPNSS1 signalling

Figure 3 Layering of DPNSS1

Figure 4 Successful call/DPNSS1

2.3.1 Services of DPNSS1

Real call signalling services of DPNSS1

Virtual call signalling service with DPNSS1

2.4 Bearer service types supported by DPNSS1 and DSS1

2.5 Supplementary services for D-channel

Charging based on distance (optional)

2.6 Capacity with D-channel

MSC Transit MSC Compact MSC

Table 2 Capacity with D-channel

=not applicable in this case

3 Planning D-channel configuration

Planning the interface

Before configuring the interface

Figure 5 D-channel configuration diagram

4 Configuring the DSS1 30B+D interface

Before you start

4.1 Creating a semipermanent cross connection in MGW

4.2 Creating and configuring the exchange terminal (ET)

4.3 Creating and configuring an echo canceller unit (ECU)

2 Create the plug-in unit (WTP).

4.4 Creating an LAPD signalling link and circuit group

4.5 Creating and modifying a route

4.6 Creating digit analysis components

4.7 Creating a Call Number and Routing Zone Index based on

g Routing Zone Index is used for a PBX-originated emergency call.

4.8 Defining services for PBX calls

4.10 Creating/modifying the End-of-Selection (EOS) analysis

4.11 Example of creating a DSS1 30B+D interface

Figure 7 DSS1 30B+D example