CCS Trace

MITEL
CCS Trace
CCS Trace
Product Release NA
Issue 1 – 25th March 2011

NOTICE
The information contained in this document is believed to be accurate in all respects but is not
warranted by Mitel Corporation (MITEL). The information is subject to change without notice
and should not be construed in any way as a commitment by Mitel or any of its affiliates or
subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or
omissions in this document. Revisions of this document or new editions of it may be issued to
incorporate such changes
Inter-Tel® is a registered trademark of Inter-Tel (Delaware), Incorporated.

Mitel® is a registered trademark of Mitel Networks Corporation.
All other trademarks mentioned in this document are the property of their respective owners,
including Mitel Networks Corporation and Inter-Tel (Delaware), Incorporated. All rights
reserved.
© 2011 Mitel Networks Corporation
Personal use of this material is permitted. However, permission to reprint/republish this material
for advertising or promotional purposes or for creating new collective works for resale or
redistribution to servers or lists, or to reuse any copy righted component of this work in other
works must be obtained from Mitel Networks Corporation.
Error! Reference source not found.
Table of Contents
CCS Trace
Appendix 01 – CCS Trace Message Descriptions
Appendix 02 – Supplementary Information String Identifiers
Appendix 03 – Supplementary Information String Parameters
Appendix 04 – CRM/CIM Messages
i
Error! Reference source not found.
ii
01
CCS Trace
Objectives
When you finish this module, you will be able to:
 Use and understand the CCS Trace Commands

CCS Trace
01- 2 01_ccs_trace.doc
CCS Trace
Table of Contents
Common Channel Signalling – CCS ............................................................................................5

CCS Trace ................................................................................................................................5
Maintenance commands...........................................................................................................5
CCS Trace Message Structure ....................................................................................................7
CCS Trace Message Details ........................................................................................................8
Examples of other CCS Traces ..............................................................................................12
IP and SIP Trunk Traces ............................................................................................................14
IP Trunks ................................................................................................................................14
SIP Trunks ..............................................................................................................................14
Using CCS Trace as a Diagnostic Tool......................................................................................16
Basic Call Interpretation..........................................................................................................16
01- 3
CCS Trace
CCS Trace
Common Channel Signalling – CCS
CCS Trace
CCS refers to the messages that pass over a digital trunk on channel 16 (E1 digital trunk) and
are used by the telephone systems at each end to send calling and clearing information about a
call being made.
The messages can be read with maintenance commands on the Mitel SX2000 and 3300 ICP’s
and are a useful diagnostic tool to help fault find on digital trunks.
On the Mitel 3300 CCS trace can also be used to view the message used on IP trunks between
3300’s and also on SIP trunks from/to a SIP service provider.
Interpreting the trace is not easy due to the amount of information available. This manual is
designed to show you the most common situations. Detailed breakdowns of the messages are
shown based on the technical specifications for CCS trace in a series of BTNR 188 publications
in appendices at the end of this manual.
Maintenance commands
Caution
CCS trace should only be enabled during a fault finding session to gather
information. It should then be disabled. Leaving CCS trace running may
impact on the performance of the 3300/SX2000
CCS TRACE ENABLE - CCS Trace is enabled, monitoring the Signalling Channel. To view the
results you must first disable CCS Trace and then use the ‘CCS Trace show output’ command.
CCS TRACE DISABLE - CCS Trace is disabled, monitoring stops.
CCS TRACE SHOW OUTPUT – The results of the CCS Trace are displayed on the screen.
CCS TRACE ENABLE CONTINUOUS - CCS Trace is enabled and continuously monitors the
signalling channel; results are displayed in real time on the screen.
CCS TRACE SHOW CONTEXT - Displays which channels are active for CCS tracing.
CCS TRACE SET CONTEXT <PLID> - Activates the specific channel for testing.
CCS TRACE SET CONTEXT VIRTUAL <PLID> - Activates the specific virtual channel for
testing
CCS TRACE CLEAR CONTINUOUS - Resets channels to ALL for tracing.
The most common command to use is CCS TRACE ENABLE CONTINUOUS which is then
turned off after you’ve gathered the information you want with CCS TRACE DISABLE.
01- 5
CCS Trace
On a busy working system with many incoming and outgoing calls you may find there is a lot of
information available which will be in what appears a mixed up order based on when calls
started and ended. A useful tip when you have the results in the 3300 maintenance screen is to
copy the text to Notepad or similar program so you can search the text for the call you made
that you want to check on. In the 3300 Maintenance screen just select the text with your mouse
(or CTRL+A) and copy it.
CCS Trace
CCS Trace Message Structure
This is an example CCS trace from a DPNSS trunk between two 3300’s. Outgoing call from ext
1102, John Digby to ext 1750, Dan Dare which was answered.
11:46:45 RO6000 DPN 23 ISRM_I ;10;*1#*50*1102#*100*J.Digby*1#*19*Z#
11:46:45 RO6000 DPN 2D SSRM_I *58*CW*IOpj@@@@@IpF]p#*58*C6*001#*58*C4*4*1#
11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
This is how the messages breakdown. Please note, there may be other messages in a trace
and a full list is provided in Appendix A1 - CCS Trace Message Descriptions. The example
shown is typical of a digital trunk call.
330
3300 ISRM_I – Initial Service Request Message – incomplete (I). The 3300 is passing the first 3300
0 part of the message about the call to the other 3300. The message is not complete so
another message has to be sent.
SSRM_I – Subsequent Service Request Message – Incomplete (I). The 3300 is sending
more of the message which is still not complete. There may be further SSRM_I
SSRM_C – Subsequent Service Request Message – Complete (C). The 3300 is sending
the rest of the message which is now complete. The other 3300 has all the information
about the number (extension) being called and who is calling
NAM – Number Acknowledgement Message. The other 3300 has accepted the call and
identified the called number as valid. It will now ring that number (extension) and if
answered a conversation can take place.
CCM – Call Connect Message. The call has been connected.
CRM/CIM – Clear Request Message/Clear Information Message. This final message

shows how the call was completed, for example, not answered, invalid number or
successfully ended by being hung up.
01- 7
CCS Trace
CCS Trace Message Details
This is a detailed breakdown of a message explaining what each part of it means and how to
interpret it. Full details of each part are in the BTNR appendices. Several examples of calls are
provided on both public and private digital trunks, IP trunks and SIP trunks including examples
of failed calls.
Using the same example above of a CCS trace for this DPNSS call, this is the basic information
provided. Outgoing call from ext 1102, John Digby to ext 1750 Dan Dare which was answered.
11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
Taking each line in turn, this is how the message is interpreted.
11:46:45 RO6000 DPN 23 ISRM_I ;10; *1# *50*1102# *100*J.Digby*1# *19*Z#

------------ --------- ------ ---- ----------- ------ ---- -------------- ----------------------- ---------
1 2 3 4 5 6 7 8 9 10
1. Time the call was made

2. RO6000 - R = real trunk (digital trunk not IP or SIP). O = Outgoing. Call is outgoing
from the 3300 recording the trace and is on trunk number 6000
3. DPN – DPNSS protocol being used. Note: DPNSS and PRI digital trunk calls on
CCS traces on the 3300 show the protocol as DPN because of the way calls are
handled within the software. DASSII trunks show DAS.
4. 23 – length of the following message in hexadecimal
5. ISRM_I - Initial Service Request Message Incomplete. This is the information about
the call sent from the calling 3300 to the other 3300. I (incomplete) means it is
longer than 45 characters so there will be an ISRM_I (incomplete) instead which will
be followed by SSRM – Subsequent Service Request Messages until the message
has been sent.
6. ;10; - Service Indicator Code. The semicolons enclosing the number means it is a
binary encoded message. The value 10 means speech. Other values could be A0
for 64K data.
7. *1# - Supplementary Information String Identifier. The * shows the beginning of the
string, 1 is the value. If it was followed by a # that would indicate the end of that
string and another string would begin. If it is followed by another * (instead of #) this
indicates it is a Supplementary Information String Parameter. The parameter should
end with a #. If the parameter ends with a * it means a second parameter applies.
The Supplementary Information String Identifiers are explained in Appendix 02 - and the
String Parameters in Appendix 03.
In this example *1 is a single string meaning an Ordinary call. This extract from the
Supplementary String Identifier shows how to read the value 1.
CCS Trace
IDENTIFIER MNEMONIC SUPPLEMENTARY INFORMATION PARAMETER FIRST USE

CODE STRING NAME SECTION
1 CLC-ORD CALLING/CALLED LINE CATEGORY - SERVICE 6
ORDINARY MARKING
8. *50*1102# - This is another Supplementary String Identifier (*50) which means

Originating Line Identity (who is calling). The value 1102# is the extension number,
the # indicates the end of that string.
IDENTIFIER MNEMONIC SUPPLEMENTARY INFORMATION PARAMETER FIRST

CODE STRING NAME USE
SECTION
50 OLI/CLI ORIGINATING LINE IDENTITY A/B PARTY 6
/CALLED LINE IDENTITY ADDRESS
9. *100*J.Digby*1# - *100 Supplementary String Identifier means Textual Display

meaning text information. The *100 is followed by another * which means there is a
parameter in this case the name J.Digby. Looking up 100 in the table below for the
Supplementary Information String the Information column tells us it is Textual
Display and the Parameter column tells us it is Text. Looking up the word Text in the
String Parameters table tells us what it means, in this case the name to display but
there are two parameters showing (1) TEXT and (2) TEXT TYPE. The parameter in
the trace J.Digby is followed by another * and value 1. This tells us the parameter
also has a parameter. From the table for Supplementary Information String
Parameters, the TEXT TYPE can be 1, 2 or 3. In our case it is 1 meaning it is a
Name.
IDENTIFIER MNEMONIC SUPPLEMENTARY INFORMATION PARAMETER FIRST
CODE STRING NAME USE
SECTION
100 TEXT TEXTUAL DISPLAY (1)TEXT (2)TEXT 16
TYPE
Supplementary Information String Parameters

PARAMETER NAME DESCRIPTION AND CODING
TEXT This Parameter is used to indicate the textual information required for display.
It may be up to 24 IA5 characters, with the * represented by TC1 (0/1) and the
# represented by TC2 (0/2).
TEXT TYPE This Parameter is optional and defines the type of text provided in the String. It
comprises a single IA5 character allocated as follows: 1 = Name 2 = Message
3 = Reason for call failure Further TEXT TYPE values may be added in later
issues of BTNR 188, BTNR 189 and BTNR 189-1. If the Parameter is not
present no meaning may be assumed. Values which are not recognised may
be ignored, the String being treated as if the Parameter were missing.
10. *19*Z# - This is the last string in the ISRM_I message. *19 means ‘Loop Avoidance’
or the number of network hops allowed as the call transits multiple systems to reach
the destination. The string (*19) is followed by another * (parameter) with the value
of Z which means 25 hops allowed. The string ends with a # closing it. There are no
more strings in this message.
01- 9
CCS Trace
IDENTIFIER MNEMONIC SUPPLEMENTARY PARAMETER FIRST USE

CODE INFORMATION STRING SECTION
NAME
19 LA LOOP AVOIDANCE (1)NUMBER OF 37
FURTHER TRANSITS
(2)NUMBER OF
FURTHER ALTERNATIVE
ROUTES

PARAMETER DESCRIPTION AND CODING
NAME
NUMBER OF This Parameter is the count of the number of further Transit PBXs allowed to route
FURTHER the call. It comprises a single IA5 alpha character in the Range A-Z; A
TRANSITS representing 0 and Z representing 25.
Taking the next line in the trace

11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
11:46:45 RO6000 DPN 2D SSRM_I *58*CW*IOpj@@@@@IpF]p# *58*C6*001# *58*C4*4*1#

------------- ----------- -------- ---- ------------ ------------------------------------------ ------------------ -------------
1 2 3 4 5 6 7 8
5. SSRM_I – Subsequent Service Request Message Incomplete. Continuation of the

ISRM in the first line.
6. *58*CW*IOpj@@@@@IpF]p# - *58*CW* This NON-SPECIFIED INFORMATION
string is for Global Call ID, which was put in for LCS. The additional parameter of
IOpj@@@@@IpF]p is unclear without reference to Mitel design but it usually
means additional information about the caller. This information is Mitel specific.
7. *58*C6*001# - The string *58 again means NON-SPECIFIED INFORMATION.
There is a parameter which in this case means AS DEFINED BY USER. The precise
meaning of this parameter is unclear without reference to Mitel design but it usually
means additional information about the caller.
8. *58*C4*4*1# - as for 7 and 6 above.
11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
CCS Trace
11:46:45 RO6000 DPN 5 SSRM_C 1750

------------- ----------- -------- ---- ------------ ---------
1 2 3 4 5 6
5. SSRM_C – Subsequent Service Request Message Complete. The message started

with the ISRM is now complete. All the call information is sent to the other 3300.
6. 1750 – the called party number

11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
11:46:46 RI6000 DPN 1B NAM *1# *50*1750# *100*D.Dare*1#

------------- ----------- -------- ---- ------------ ---- --------------- ---------------------
1 2 3 4 5 6 7 8
5. NAM – Number Acknowledgement Message.

6. *1# - String, Calling/Called Line Ordinary (a normal call). The string ends with a # so
there is no parameter.
7. *50*1750# - String *50 meaning ORIGINATING LINE IDENTITY /CALLED LINE
IDENTITY with a parameter of A/B PARTY ADDRESS. The value of the parameter
here is 1750 which is the called party. As this NAM is INCOMING to the 3300 being
traced it is the CALLED LINE IDENTITY AND B PARTY ADDRESS. The other 3300
is acknowledging the original message from the 3300 calling 1750 by verifying the
number is valid.
8. *100*D.Dare*1# - String, Text display with parameter, the actual name followed by
another parameter (*1). The text display string is the other 3300 telling the originator
what to display on the calling phone.
11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
11:46:48 RI6000 DPN 1 CCM

------------- ----------- -------- ---- --------
1 2 3 4 5
5. CCM – Call Connected Message. The call has been connected and a conversation
can now take place over a voice channel
01- 11
CCS Trace
Taking the next 2 lines in the trace

11:46:45 RO6000 DPN 5 SSRM_C 1750
11:46:46 RI6000 DPN 1B NAM *1#*50*1750#*100*D.Dare*1#
11:46:48 RI6000 DPN 1 CCM
11:46:53 RO6000 DPN 2 CRM/CIM ;30;
11:46:53 RI6000 DPN 2 CRM/CIM ;30;
11:46:48 RO6000 DPN 2 CRM/CIM ;30;

------------- ----------- -------- ---- -------------------
1 2 3 4 5
5. CRM/CIM ;30; – Clear Request Message/Clear Information Message. The CRM is

being sent from one 3300 to the other (outgoing – RO6000) saying the call has been
cleared down. In the last line of the trace the CRM/CIM is from the other 3300
(RI6000). This is in fact the CIM acknowledging the CRM. The value 30 means the
call completed normally.
Examples of other CCS Traces

DPNSS call which is diverted to voicemail
DPNSS incoming call from 1750 to 1102 - not answered, and 1102 diverts to VM which does
answers
11:51:34 RI6000 DPN 22 ISRM_I ;10;*1#*50*1750#*100*D.Dare*1#*19*Z#
11:51:34 RI6000 DPN 2D SSRM_ I *58*CW*SJXC@@@@@J@f}P#*58*C6*001#*58*C4*4*1#
11:51:34 RI6000 DPN 5 SSRM_I 1102
11:51:34 RO6000 DPN 1C NAM *1#*50*1102#*100*J.Digby*1#
11:51:51 RO6000 DPN B NSIM ;1C;*100*;7F;*1#
11:51:51 RO6000 DPN 16 CCM *1*3#*50*2503#*166*6#
11:51:58 RI6000 DPN 2 CRM/CIM ;30;
The trace is as before but there is an NSIM – Non-Standard Information Message of:
11:51:51 RO6000 DPN B NSIM ;1C;*100*;7F;*1#
The ;1C;*100*;7F;*1# breaks down as follows:
1C is a Mitel specific message, *100 a supplementary string parameter for Text display (name)
and 7F meaning no name is available – in this case the call was answered by a voicemail port
with no name programmed.
PRI call – called number is busy
Incoming call on channel 102 from mobile 07530198766 to extension 431430.

12:54:07 RI102 DPN 2C ISRM_C 10;*3#*50*07530198766#*100*410*1#*19*Z#431430
12:54:07 RO102 DPN B CRM/CIM ;8;*166*2 3#
12:54:07 RI102 DPN B CRM/CIM ;8;*166*2 3#
The CRM/CIM value of 8 indicates called number busy. The called extension number 1430 is
shown as 431430. This is the complete number sent from the BT exchange (6 digits). The 3300
Trunk Attribute programming will remove the 43.
CCS Trace
PRI call – called number is invalid (not recognised by the 3300)
Incoming call on channel 1001 from 01216412100 to extension 1190 (which does not exist).
12:00:32 RI1001 DPN 2B ISRM_I 10;*3#*50*01216412100#*100*410*1#*19*Z#
12:00:32 RI1001 DPN 1A SSRM_I *238*dXD#*50*01216412100#
12:00:32 RI1001 DPN 19 SSRM_C *235*HX@*1216412100#1190
12:00:32 RO1001 DPN 2 CRM/CIM ;0;
12:00:32 RI1001 DPN 2 CRM/CIM ;0;
The CRM/CIM value of 0 indicates called number invalid. The SSRM_C shows the CLI of the
calling number (note there is no 0, this is removed by the BT exchange). The called number
1190 is sent as 4 digits from the BT exchange. The 3300 Trunk Attributes will absorb 0 digits.
01- 13
CCS Trace
IP and SIP Trunk Traces
CCS Trace can be used with both SIP and IP trunks. The information recorded is the same
although there will be some NSIM – Non-Standard Information Message which are Mitel
specific and whose values are not known without reference to Mitel Design and Support.
Below are some examples of calls.
IP Trunks
IP Trunk channels are ‘virtual’ so the trunk number always shows as X, either incoming or
outgoing (RIX or ROX)
The protocol is always DPNSS (DPN) and the PBX number the trace is running on is also
shown, PBX2 in this example (from the IP Trunk programming forms on the 3300). There is
also a call identifier of 2 2 (after the PBX 2 number). On the example further down the page this
is 3 3. This call identifier allows you to follow a particular call through a CCS trace that may
contain many different types of calls.
Outgoing from ext 1102 to 1750 - answered

09:34:19 ROX DPN PBX2 2 2 D** B** 23 ISRM_I ;10;*1#*50*1102#*100*J.Digby*1#*19*Z#
09:34:19 ROX DPN PBX2 2 2 D** B** 2D SSRM_I 58*CW*IOpj@@@@@KOvt`#*58* C6*001#
*58*C4*4*1 #
09:34:19 ROX DPN PBX2 2 2 D** B** 5 SSRM_C 1750
09:34:19 RIX DPN PBX2 2 2 D** B** 1B NAM *1#*50*1750#*100*D.Dare*1#
09:34:21 RIX DPN PBX2 2 2 D** B** 1 CCM
09:34:22 RIX DPN PBX2 2 2 D** B** 2 CRM/CIM ;30;
Outgoing from ext 1102 to 1750. 1750 diverts to VM which answers
09:35:39 ROX DPN PBX2 3 3 D** B** 23 ISRM_ ;10;*1#*50*1102#*100*J.Digby*1#*19*Z#

09:35:39 ROX DPN PBX2 3 3 D** B** 2D SSRM_I *58*CW*IOpj@@@@@KO}E`#*58*C6*001#
*58*C4*4*1#
09:35:39 ROX DPN PBX2 3 3 D** B** 5 SSRM_C 1750
09:35:39 RIX DPN PBX2 3 3 D** B** 1B NAM *1#*50*1750#*100*D.Dare*1#
09:35:55 RIX DPN PBX2 3 3 D** B** B NSIM ;1C;*100*;7F;*1#
09:35:56 RIX DPN PBX2 3 3 D** B** 18 CCM *1*1 3#*50*2522#*166*6#
09:36:02 RIX DPN PBX2 3 3 D** B** D EEM_C *58*CM*ME09#
09:36:02 RIX DPN PBX2 3 3 D** B** D EEM_C *58*CM*MB00#
09:36:03 ROX DPN PBX2 3 3 D** B** 2 CRM/CIM ;30;
09:36:03 RIX DPN PBX2 3 3 D** B** 2 CRM/CIM ;30;
There is also an EEM_C and EEM_I message in this example. This is an End to End Message
and is providing additional information after the call has connected. It is usually seen if a call is
put on hold or transferred.
SIP Trunks
The protocol is always DPNSS (DPN) and the SIP Peer being used is shown (from the SIP
Trunk programming forms on the 3300). Please note that with SIP trunks the service providers
may just send the extension number into the 3300 or the whole number. It varies.
On each trace a call identifier number is shown, in the first example below this is 552 and in the
second it is 691. This allows you to identify each line of the trace when there are other traces
also being recorded.
CCS Trace
Outgoing call on SIP Peer CandW_SIP from L.Long extension 101144 to 07971256790
14:50:02 ROL DPN PEER CandW_SIP 552 26 ISRM_I ;10;*1#*50*1011444# *100*L.Long*1#
*19*Z#
14:50:02 ROL DPN PEER CandW_SIP 552 22 SSRM_I *58*CW*@@@@@@@@@YwoOP#
*58*C6*001#
14:50:02 ROL DPN PEER CandW_SIP 552 2B SSRM_C *58*CL*E*1*1011444*U0015485*A#
907971256790
14:50:02 RIL DPN PEER CandW_SIP 552 7 NIM *51*3#
14:50:02 RIL DPN PEER CandW_SIP 552 11 NAM *3#*166*1 2 3 4#
14:50:21 RIL DPN PEER CandW_SIP 552 1 CCM
14:50:23 ROL DPN PEER CandW_SIP 552 2 CRM/CIM ;30;
Incoming call on SIP Peer CandW_SIP from 8706095050 to 1011817 P.Waters

14:50:00 RIL DPN PEER CandW_SIP 691 26 ISRM_I ;10;*3#*19*S# *58*Ca*1*S#
*100*8706095050#
14:50:00 RIL DPN PEER CandW_SIP 691 26 SSRM_I*58*CW*@@@@@@@@@YwoHp#
*50*8706095050#
14:50:00 RIL DPN PEER CandW_SIP 691 B SSRM_C 1173221817
14:50:00 ROL DPN PEER CandW_SIP 691 28 NAM *1#*50*1011817# *166*6#
*100*P.Waters*1#
14:50:05 ROL DPN PEER CandW_SIP 691 2 CRM/CIM ;30;
01- 15
CCS Trace
Using CCS Trace as a Diagnostic Tool
The large amount of information about a call allows you to use CCS Trace to diagnose trunk
problems. For example you can see the incoming and outgoing numbers being dialled; what the
BT exchange is actually sending you and what your 3300 ARS is actually dialling out. The
CCM/CIM messages let you see the status of the completed or failed call.
Basic Call Interpretation

You can look at a CCS Trace and gather basic call information.
Example: PRI call incoming to a 3300. The references are highlighted in the trace in bold.
Trunk 1001 incoming. Calling number 01216412100. Calling number CLI ID 1216412100 (note
the 0 is removed by the exchange). Called number 1102. Called number verified as valid
(NAM). Call was connected (CCM) and cleared down normally (CRM/CIM 30;)
11:59:39 RI1001 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*233*`IBc#*58*CI*W6a#
11:59:39 RI1001 DPN 1A SSRM_I *238*dXD#*50*01216412100#
11:59:39 RI1001 DPN 19 SSRM_C *235*HX@*1216412100#1102
11:59:39 RO1001 DPN 23 NAM *1#*50*1102#*166*6#*100*J.Digby*1#
11:59:40 RO1001 DPN 1 CCM
11:59:43 RO1001 DPN 2 CRM/CIM ;30;
11:59:43 RI1001 DPN 2 CRM/CIM ;30;
Example: PRI call outgoing from a 3300
Trunk 1001 Outgoing. Calling party 1102. Called number 01216412100. Call connected (CCM)
and call cleared normally (CRM/CIM 30;)
11:58:10 RO1001 DPN 2D SSRM_I *58*CW*IOpj@@@@@Ip{}P#*58*C6*001#*58*C4*4*1#
11:58:10 RO1001 DPN C SSRM_C 01216412100
11:58:10 RI1001 DPN 7 NIM *51*3#
11:58:10 RI1001 DPN 13 NAM *4*4#*166*1 2 3 4#
11:58:11 RI1001 DPN A CCM *58*CP*G#
11:58:13 RO1001 DPN 2 CRM/CIM ;30;
11:58:14 RI1001 DPN 2 CRM/CIM ;30;
Example: a failed call due to invalid digits not recognised by the 3300
In this example the 3300 trunk attributes are set to absorb 0 digits and expects the exchange to
send a 4 digit number which it does, 1190:
12:00:32 RI1001 DPN 19 SSRM_C *235*HX@*1216412100#1190
However the 3300 has still rejected the call with the CRM/CIM of 0. This is because the number
1190 does not exist in the 3300 database.
12:00:32 RI1001 DPN 2B ISRM_I 10;*3#*50*01216412100#*100*410*1#*19*Z#
12:00:32 RI1001 DPN 1A SSRM_I *238*dXD#*50*01216412100#
12:00:32 RI1001 DPN 19 SSRM_C *235*HX@*1216412100#1190
12:00:32 RO1001 DPN 2 CRM/CIM ;0;
12:00:32 RI1001 DPN 2 CRM/CIM ;0;
CCS Trace
Example: a failed call due to the wrong digit length from the exchange
In this example the 3300 trunk attributes are set to absorb 0 digits and expects the exchange to
send in just 4 digits. In fact the exchange is sending 6 digits, 652119:
14:00:12 RI1001 DPN 19 SSRM_C *235*HX@*1216412100#652119
Therefore the 3300 is trying to process 652119 which is not recognised so it rejects the call with
the CRM/CIM message of 0.
14:00:12 RI1001 DPN 2B ISRM_I 10;*3#*50*02073511100#*100*410*1#*19*Z#
14:00:12 RI1001 DPN 1A SSRM_I *238*dXD#*50*02073511100#
14:00:12 RI1001 DPN 19 SSRM_C *235*HX@*2073511100#652119
14:00:12 RO1001 DPN 2 CRM/CIM ;0;
14:00:12 RI1001 DPN 2 CRM/CIM ;0;
In both of the above examples you can see exactly what the exchange is sending in before any
processing by the 3300 trunk attribute form.
Example: multiple SSRM messages. ARS not programmed correctly.
In this example the Initial Service Request Message for this outgoing call is from extension
87772 which has dialled 07768048168. The ISRM_I only shows the first 3 digits of the number.
The rest of the number is sent digit by digit with SSRM’s until complete. This is caused by the
ARS Route being set to default ‘4 digits before outpulsing’. Therefore the extension has dialled
9077 (4 digits) which triggers the first ISRM_I. Each digit after that is treated as a separate
message. For digital trunks the ARS Route for should be set to Blank digits before outpulsing.
12:58:16 RO179 DAS F ISRM_I/ ;10;*86*87772#077
12:58:17 RO179 DAS 2 SSRM_I/ 6
12:58:17 RO179 DAS 2 SSRM_I/ 8
12:58:17 RO179 DAS 2 SSRM_I/ 0
12:58:17 RO179 DAS 2 SSRM_I/ 4
12:58:17 RO179 DAS 2 SSRM_I/ 8
12:58:18 RO179 DAS 2 SSRM_I/ 1
12:58:18 RO179 DAS 2 SSRM_I/ 6
12:58:18 RO179 DAS 2 SSRM_C/ 8
12:58:25 RI179 DAS 7 CAM/NAM *86*X#
12:58:36 RO179 DAS 2 CRM/CIM ;30;
12:58:36 RI179 DAS E CRM/CIM ;30;*AA*CLEARED#
01- 17
CCS Trace
A1
CCS Trace Message
Descriptions
CCS Trace
A1- 2 A1_mess_desc.doc
CCS Trace Message Descriptions
Where the description refers to ‘field contains supplementary information’ this relates to the
Supplementary Information String Identifiers (Module 02) and Supplementary Information
Parameters (Module 3).
CCM Call Connected Message This message indicates to the Originating PBX that the
call has been answered by the called terminal and that
the speech or data phase can be entered.
The Indication Field contains supplementary
information
CIM Clear Indication Message This message is used to acknowledge a CRM. The
coding of the Clearing Cause field is normally the same
Clearing Cause as was received in the CRM
CRM Clear Request Message This message is used to initiate the clearing sequence.
Each PBX in a multi-link call releases the connection,
repeats the Clear Request Message to the next link,
and returns a Clear Indication Message to confirm that
the channel is now free. An Indication Field can be
provided for additional information that is not contained
within the Clearing Cause field
EEM(C) End-to-End Message This message is used only after completion of the
(Complete) routing phase to carry end to end information between
Originating, Terminating and Branching PBXs in the
forward or backward direction. The message may be
used both before and after answer. This message
contains supplementary information and is a complete
request. This message is also used to indicate the
completion of an end-to-end sequence which was
started with an EEM(I). The Indication Field contains
supplementary information.
EEM(I) End-to-End Message This message is used only after completion of the
(Incomplete) routing phase to carry end-to-end information between
Originating, Terminating and Branching PBXs in the
forward or backward direction. The message may be
used both before and after answer. It is used when the
45 octets of an EEM(C) are not enough to hold the
supplementary information. The sequence started by
an EEM(I) will be completed by an EEM(C) unless the
call is cleared in between. The Indication Field contains
ERM(C) End-to-End Recall This message is used, only after completion of the
Message (Complete) routing phase, by certain Supplementary Services to
establish a second call, via the same channel as an
existing call, as far as the existing call's End PBX. It
contains the complete recall request and should not be
followed by any Subsequent Service Request
Messages. The Service Indicator Code (SIC) and
Selection Field are used in the same way as in the
ISRM.
A1- 3
CCS Trace
ERM(I) End-to-End Recall This message is used, only after completion of the
Message (Incomplete) routing phase, by certain Supplementary Services to
establish a second call via the same channel as an
existing call, as far as the existing call's End PBX. It is
used in place of an ERM(C) under the same
circumstances as an ISRM(I) is used in place of an
ISRM(C). It is normally followed by at least one SSRM
containing further selection information, eg Destination
Address digits.
ISRM(C) Initial Service Request The ISRM(C) is used to establish a new call across the
Message (Complete) network. The call may be Real or Virtual. This message
contains the complete request and should not be
followed by any Subsequent Service Request
Messages (SSRMs).
ISRM(I) Initial Service Request This message is used instead of an ISRM(C) under the
Message (Incomplete) following circumstances:
i. Where the 45 octets of an ISRM(C) are not enough to
hold the selection information and the Destination
Address.
ii. Where Destination Address digits are sent to a
slower speed signalling system eg 10 pps.
iii. Where end-of-dialling cannot be determined by the
Originating PBX.
An ISRM(I) is normally followed by at least one
Subsequent Service Request Message containing
further selection information.
LLM(C) Link-by-Link Message This message is used only after completion of the
(Complete) routing phase to carry information between adjacent
PBXs. It is also used to indicate the completion of a
link-by-link sequence which was started with an LLM(I).
information.
LLM(I) Link-by-Link Message
(Incomplete)
LLRM Link-by-Link Reject This message is used to reject an unrecognised or
Message invalid message in the Link-by-Link message group
(0100). The Rejection Cause field is coded in the same
way as the Clearing Cause field.
LMM Link Maintenance This message is used to request, or respond to a
Message request for, maintenance actions to be performed. The
Maintenance Action field identifies the action required
or the response being made. The message may be
sent independently of the state of any call in progress
on the channel. The Indication Field contains
LMRM Link Maintenance Reject This message is used to respond to a request for
Message maintenance actions to be performed, when the
request has been rejected. The Indication Field
contains supplementary information.
NAM Number Acknowledge This message is sent for successful Simple Calls within
Message DPNSS. The message is also used to indicate that all
digits have been received in certain interworking
situations eg with an outgoing call to a 10 pps link. The
use of the NAM for non- Simple Calls (eg calls
containing or encountering Supplementary Services)
does not automatically imply that the required
extension is free; that information may be unknown at
this stage. Subsequent messages containing additional
information will follow.
NIM Network Indication This message is used only during the routing phase of
Message a call to notify PBXs along the route of its progress, eg
Alternative Routing. The message can be used only in
the backward direction and cannot be used after a
NAM.
RM(C) Recall Message This message is used, only after completion of the
(Complete) routing phase, by certain Supplementary Services to
existing call. It contains the complete call request and
should not be followed by any SUBSEQUENT
SERVICE REQUEST Messages.
The Service Indicator Code (SIC) and Selection Field
are used in the same way as in the ISRM.
RM(I) Recall Message This message is used, only after completion of the
(Incomplete) routing phase, by certain Supplementary Services to
existing call. It is used in place of an RM(C) under the
same circumstances as an ISRM(I) is used in place of
an ISRM(C). It is normally followed by at least one
SSRM containing further selection information, eg
Destination Address digits.
RRM Recall Rejection This message is used to indicate that a Recall Request
Message has not succeeded.
An Indication Field can be provided for additional
information that is not contained within the Rejection
Cause field. The Rejection Cause field is coded in the
same way as the Clearing Cause field.
SM Swap Message This message is used during a call to request a change
from the current service mode to a new mode as shown
by the Service Indicator Code. The message is also
used to acknowledge a SWAP. The Indication Field
contains supplementary information.
SCIM Single-Channel Clear This message is used to acknowledge an SCRM. The
Indication Message coding of the Clearing Cause field normally contains
the same Clearing Cause as was received in the
SCRM.
information.
A1- 5
CCS Trace
SCRM Single-Channel Clear This message is used to initiate the clearing sequence
Request Message of one of the calls on a channel in dual use. The
particular call of the two which is to be released is
indicated by a Supplementary Information String within
the Indication Field of the message. On receipt of an
SCRM, a PBX releases the indicated call and returns
an SCIM to confirm that the channel is now in single
use. In the case of a Transit PBX, the SCRM is then
repeated to the next link. The Indication Field contains
SSRM(C) Subsequent Service This message is used to send additional selection
Request Message information (eg digits) not included in a preceding
(Complete) ISRM(I), ERM(I), RM(I) or SSRM(I) and to indicate the
end of selection. No further Subsequent Service
Request Messages can be sent after this message.
The sequence started by an ISRM(I), ERM(I) or RM(I)
will not always be completed by an SSRM(C).
The Selection Field contains the selection information
relating to a call set up or Supplementary Service
Request. It may be omitted if the SSRM is indicating
merely the end of selection
SSRM(I) Subsequent Service This message is used to send additional selection
Request Message information (eg digits) not included in a preceding
(Incomplete) ISRM(I), ERM(I), RM(I) or SSRM(I). An indefinite
number of SSRM(I)s can follow an ISRM(I), ERM(I) or
RM(I); the sequence is normally completed by an
SSRM(C). The Selection Field contains the selection
information relating to a call set-up or Supplementary
Service Request.
A2
Supplementary Information
String Identifiers
CCS Trace
A2- 2 A2_supp_string_ident.doc
Supplementary Information String Identifiers
These are the strings that follow a CCS Trace Message. The String may be followed by a
parameter (See Module 4)
HISTORY
Issue 1 - May 1983 Issue 2 - February 1984 Issue 3 - September 1984 Issue 4 - March 1986
Issue 5 - December 1989 Issue 5.1 - December 1993 - Corrigenda: some pages replaced.
Issue 6 - January 1995:
 New Strings and Parameters added for interworking between DPNSS 1 and ISDN
signalling systems, see BTNR 189-I.
 New Strings and Parameters added for enhanced Sections: 6, 16, 22 and 33.
 New Strings and Parameters added for new Sections: 44, 45, 46, 47 and 48.
 SERVICE MARKING Parameter extended.
 STATUS Parameter extended.
APPENDIX 1, Issue 1 added.
BTNR 188 SECTION 4 ANNEX 2 Issue 6 Page 2 January 1995

GENERAL
This Annex gives details of the Supplementary Information String Identifiers and Parameters
used in DPNSS 1 and is complete at the time of issue.
New Strings and Parameters are continually being added to DPNSS 1, however, for the
following reasons:
 support of new Supplementary Services;
 support of enhanced Supplementary Services;
 additions to Service Independent Strings (SECTION 16);
 support of interworking between DPNSS 1 and other signalling systems.
This Annex is intended to record the master list of Supplementary Information Strings for all
DPNSS 1 applications and will be updated periodically as the BTNRs are reissued. Reference
should be made, however, to BTNR 188, BTNR 189 and BTNR 189-I to ensure that the latest
information is taken into account.
1.1 Use of Strings

In general, Supplementary Information Strings are associated with the Services and
Supplementary Services defined in SECTION 6 onwards.
Some Supplementary Information Strings, however, are not associated with a particular
Supplementary Service Section, and their "First-Use Section" in the list of Identifiers is shown
as SECTION 16. The use of these Strings is described in SECTION 16 of BTNR 188 and
SECTION 16 of BTNR 189 where they are termed "Service Independent Strings".
NOTE: In Subsections 2 and 4 of this Annex the "First-Use Section" refers to BTNR 188
unless indicated otherwise (eg 6/189 refers to a first use in SECTION 6 of BTNR 189).
1.2 Use of Parameters
If a Supplementary Information String has a Parameter, then the use of the Parameter is
mandatory unless otherwise stated.
If more than one Parameter is indicated for a Supplementary Information String, then the
Parameters must be sent in the order specified. If a Parameter is optional it will be sent last.
Where more than one Parameter is optional then, in order to send the second optional
Parameter, it is mandatory to send the first. The rule is extended where more than two
Parameters are optional.
A2- 3
CCS Trace
CODING OF SUPPLEMENTARY INFORMATION STRING IDENTIFIERS

MNEMONIC PARAMETER FIRST
IDENTIFIER SUPPLEMENTARY INFORMATION
USE
CODE STRING NAME
SECTION
CALLING/CALLED LINE SERVICE
1 CLC-ORD 6
CATEGORY - ORDINARY MARKING
2 CLC-DEC CALLING/CALLED LINE STATUS 6/189
CATEGORY - DECADIC
3 CLC-ISDN CALLING/CALLED LINE (1)STATUS NOTE 1
NOTE 1 CATEGORY - PUBLIC ISDN (2)ISDN TYPE
4 CLC-PSTN CALLING/CALLED LINE STATUS 6/189
CATEGORY - PSTN
5 CLC-MF5 CALLING/CALLED LINE STATUS 6/189
CATEGORY - SSMF5
CALLING/CALLED LINE
6 CLC-OP CATEGORY - OPERATOR NONE 20
CALLING/CALLED LINE
7 CLC-NET CATEGORY - NETWORK NONE 9
8
NOTE 2
9
CALL BACK WHEN FREE -
10B CBWF-R NONE 9
REQUEST
11B CBWF-FN CALL BACK WHEN FREE -FREE NONE 9
NOTIFICATION
12B CBWF-CSUI CALL BACK WHEN FREE -CALL NONE 9
SET-UP(IMMEDIATE)
13B CBWF-C CALL BACK WHEN FREE - NONE 9
CANCEL
14B RO RING OUT NONE 9
15B CBC CALL BACK COMPLETE NONE 9
16B CBWF- CALL BACK WHEN FREE -CALL NONE 9
CSUD SET-UP(DELAYED)
NOTE 1: In BTNR 189 and earlier issues of BTNR 188, IDENTIFIER CODE No 3 was
allocated to CLC-DASS2. The scope of this CLC has since been expanded to cover access to
the public ISDN in general (see BTNR 189-I) and the CLC has consequently been renamed as
CLC-ISDN. The Status Parameter has also been expanded to allow the additional optional
Parameter "ISDN Type" to be used to indicate the type of public ISDN interface encountered
(see Subsection 3 of this Annex).
NOTE 2: In BTNR 189, BTNR 189-I and earlier issues of BTNR 188, IDENTIFIER CODE No 8
was allocated to CLC-CONF (Calling Line Category - Conference). No Supplementary Service
has ever been written incorporating this String; to avoid confusion this String has been
withdrawn and IDENTIFIER CODE No 8 is now undefined.
CALL BACK WHEN NEXT

17B CBWNU-R NONE 31
USEDREQUEST
18 COS CLASS OF SERVICE (1)ROUTE 16

RESTRICTION
CLASS (2)CALL
BARRING
GROUP
(3)FACILITY
LIST CODE
19 LA LOOP AVOIDANCE (1)NUMBER OF 37
FURTHER
TRANSITS
(2)NUMBER OF
FURTHER
ALTERNATIVE
ROUTES
20 EI-PVR EXECUTIVE INTRUSION -PRIOR INTRUSION 10
VALIDATION CAPABILITY
LEVEL
21 EI-R EXECUTIVE INTRUSION - INTRUSION 10
REQUEST CAPABILITY
LEVEL
22B IPL-R INTRUSION PROTECTION LEVEL- NONE 10
REQUEST
23 IPL INTRUSION PROTECTION LEVEL INTRUSION 10
PROTECTION
LEVEL
24B EI-C EXECUTIVE INTRUSION 14
INTRUSIONCONVERT CAPABILITY
LEVEL
25 EI-I INTRUDED NONE 10
26 CW CALL WAITING NONE 17
27 CO CALL OFFER NONE 14
28T SN-REQ SEND NEXT-REQUEST NONE 6/189
29 HGF HUNT GROUP FORWARDED NESTING 16
LEVEL
30B DIV-V DIVERSION-VALIDATION NONE 11
31B DIV-FM DIVERSION-FOLLOW ME C PARTY 11
ADDRESS
32 DIV-BY DIVERSION-BY PASS NONE 11
DIVERSION CANCEL -
33B DIV-CI NONE 11
IMMEDIATE
34B DIV-CR DIVERSION CANCEL - ON NO NONE 11
REPLY
35B DIV-CB DIVERSION CANCEL - ON BUSY NONE 11
36B DIV-CA DIVERSION CANCEL - ALL NONE 11
37F DVG-I DIVERTING IMMEDIATE B PARTY 11
ADDRESS
38F DVG-B DIVERTING ON BUSY B PARTY 11
ADDRESS
A2- 5
CCS Trace
39F DVG-R DIVERTING ON NO REPLY B PARTY 11

ADDRESS
40B DVT-I DIVERT IMMEDIATE C PARTY 11
ADDRESS
41B DVT-B DIVERT ON BUSY C PARTY 11
ADDRESS
42 DVD-I DIVERTED IMMEDIATE C PARTY 11
ADDRESS
43 DVD-B DIVERTED ON BUSY C PARTY 11
ADDRESS
44 DVD-R DIVERTED ON NO REPLY C PARTY 11
ADDRESS
45 DVT-R DIVERT ON NO REPLY C PARTY 11
ADDRESS
46 SIC SERVICE INDICATOR CODE SIC 7/189
BEARER SERVICE SELECTION -
47R BSS-M SIC 18
Mandatory
48I BSS-P BEARER SERVICE SELECTION - SIC 18
Preferred
49I BSS-N BEARER SERVICE SELECTION - SIC 18
Notification
50 OLI/CLI ORIGINATING LINE IDENTITY A/B PARTY 6
/CALLED LINE IDENTITY ADDRESS
51 RTI ROUTING INFORMATION (1)ROUTING 6
INFORMATION
(2)ISDN TYPE
52
53 DVD-E DIVERTED-EXTERNALLY DIVERSION 11/189
TYPE
54 REJ REJECT NONE 12
55 ACK ACKNOWLEDGE NONE 10
56 SN SEND NEXT NONE 6/189
DASS 2-SERVICE INDICATOR
57A D-SIC SIC 16/189
CODE
58 NOTE NSI NON-SPECIFIED INFORMATION (1)NSI 15
IDENTIFIER
(2,3,ETC) AS
DEFINED BY
USER
59 OCP ORIGINALLY CALLED PARTY B-PARTY 5
ADDRESS ANNEX 4
60B HOLD-REQ HOLD REQUEST NONE 12
61 RECON RECONNECTED NONE 12
62 HDG HOLDING NONE 5
ANNEX 4
63 CD-Q CALL DISTRIBUTION-QUEUE NONE 43
64B TEXT-M TEXT MESSAGE TEXT 39
65 SOD-B STATE OF DESTINATION-BUSY NONE 9

66 SOD-F STATE OF DESTINATION-FREE NONE 9
CD-DNQ CALL DISTRIBUTION-DO NOT NONE 43
67B 68
QUEUE
69B CD-LINK CALL DISTRIBUTION-LINKED CALL INDEX 43
DIVERSION-REMOTE SET C PARTY
70B DIV-RSI 33
IMMEDIATE ADDRESS
71B DIV-RSB DIVERSION-REMOTE SET ON C PARTY 33
BUSY ADDRESS
72B DIV-RSR DIVERSION-REMOTE SET ON NO C PARTY 33
REPLY ADDRESS
73B DIV-RCI DIVERSION-REMOTE CANCEL NONE 33
IMMEDIATE
DIVERSION-REMOTE CANCEL ON
74B DIV-RCB NONE 33
BUSY
75B DIV-RCR DIVERSION-REMOTE CANCEL ON NONE 33
NO REPLY
76B DIV-RCA DIVERSION-REMOTE CANCEL NONE 33
ALL
77B PASSW PASSWORD PASSWORD 33
78B SPL SPLIT NONE 13
79 TWP TWO PARTY CALL-DIR 13
80 ENQ ENQUIRY CALL HC-CLC 13
81F SCE SINGLE CHANNEL ENQUIRY HC-CLC 13
82 TRFD TRANSFERRED CALL-DIR 13
83F SHTL SHUTTLE NONE 13
84H COC CONNECTED CALL NONE 13
85 TRFR TRANSFER NONE 13
CALL DISTRIBUTION-FREE
86B CD-FN CALL INDEX 43
NOTIFY
87 ICC INTERCOM CALL NONE 16
88H AD-RQ ADD-ON REQUEST NONE 13
89B AD-V ADD-ON VALIDATION NONE 13
90 AD-O ADDED-ON NONE 13
91B ENH ENHANCED SSMF5 NONE 6/189
92 BAS BASIC SSMF5 NONE 6/189
93B CD-UNLINK CALL DISTRIBUTIONUNLINKED CALL INDEX 43
94 SNU SIGNAL NOT UNDERSTOOD ENHANCED 5
STRING ID
95 SU SERVICE UNAVAILABLE STRING ID 5
RECALL REJECTED SIGNAL NOT ENHANCED
96 RR-SNU 5
UNDERSTOOD STRING ID
97B CD-CSU CALL DISTRIBUTION-CALL SET CALL INDEX 43
UP
98 IG-SNU IGNORED-SIGNAL NOT STRING ID 5
UNDERSTOOD LIST
A2- 7
CCS Trace
99 IG-SU IGNORED-SERVICE STRING ID 18

UNAVAILABLE LIST
100 TEXT TEXTUAL DISPLAY (1)TEXT 16
(2)TEXT TYPE
101 SIM-A SIMULATED ANSWER NONE 6/189
102B ACT ACTIVATE NONE 27
103B DEACT DEACTIVATE NONE 27
CHANNEL
104B TCS TRAFFIC-CHANNEL STATUS 27
STATUS
105B CHID CHANNEL IDENTITY CHANNEL 27
NUMBER
106B FR-R FORCED RELEASE - REQUEST NONE 38
PRIORITY
107J PB-P BPL 35
BREAKDOWNPROTECTION
108 PB-R PRIORITY BREAKDOWNREQUEST BCL 35
109 DI DEVICE IDENTITY DEVICE 43
INDEX
110B ROP-R ROUTE OPTIMISATION - CALL 19
REQUEST REFERENCE
NUMBER
111H ROP-CSU ROUTE OPTIMISATION - CALL NONE 19
SET UP
112B ROP-CON ROUTE OPTIMISATION - NONE 19
CONNECTED
113 DND DO NOT DISTURB SOD 32
114 DND-O DO NOT DISTURB-OVERRIDE NONE 32
115B DND-S DO NOT DISTURB-SET NONE 34
116B DND-C DO NOT DISTURB-CLEAR NONE 34
117
118B EST EXTENSION STATUS CALL NONE 20
119 CDIV CONTROLLED DIVERSION NONE 21
REASON FOR
120 RDG REDIRECTING 22
REDIRECTING
121 RCF REDIRECTING ON CALL FAILURE (1)CLEARING 22
CAUSE and
(2)B PARTY
ADDRESS
122H TOV-R TAKEOVER REQUEST NONE 24
123B TOV-V TAKEOVER VALIDATION NONE 24
RECONNECT
124B SER-R SERIES CALL REQUEST 23
ADDRESS
125 SER-C SERIES CALL-CANCEL NONE 23
126 SER-E SERIES CALL-ESTABLISHMENT NONE 23
127B NS-N STATE OF 25
NIGHT SERVICE - NOTIFICATION
OPERATOR
128A NS-DVT NIGHT SERVICE-DIVERT (1) NIGHT 25

SERVICE
ADDRESS
(2)PBX FLAG
129 NS-DVG NIGHT SERVICE - DIVERTING NONE 25
130 NS-DVD NIGHT SERVICE - DIVERTED C PARTY 25
ADDRESS
131 NS-RDVT NIGHT SERVICE - REDIVERT C PARTY 25
ADDRESS
132 NS-RDVG NIGHT SERVICE - REDIVERTING NONE 25
133 NS-RDVD NIGHT SERVICE - REDIVERTED C PARTY 25
ADDRESS
134 NS-DA NIGHT SERVICE - DEACTIVATED NONE 25
135 Q-INFO QUEUE INFORMATION (1) NUMBER 16
OF CALLS & (2)
NUMBER OF
SERVERS
136 Q-PRIO QUEUE PRIORITY PRIORITY 16
LEVEL
137T SW-V SWAP - VALIDATION NONE 8
138 SW-R SWAP - REJECTED LOCATION 8
139
140 A2 SSMF5 SIGNAL 'A-2' NONE 6/189
141
143
146
CALL BACK WHEN FREE-CALL
151B CBWF-CLB NONE 9/189
BACK
152B DVT DIVERT C PARTY 11/189
ADDRESS
153 SOD-I STATE OF NONE 11/189
DESTINATIONINDETERMINABLE
154 DVG DIVERTING B PARTY 11/189
ADDRESS
155B SOD-REQ REQUEST STATE OF NONE 11/189
DESTINATION
156B CBWF-CB CALL BACK WHEN FREE-CALL NONE 9/189
BACK REQUEST
A2- 9
CCS Trace
157A NAE-DC NETWORK ADDRESS SUBADDRESS 41

EXTENSION -DESTINATION
COMPLETE
158 SFI SUPPLEMENTARY FACILITIES NONE 35
INHIBITED
NETWORK ADDRESS
159A NAE-DI EXTENSION -DESTINATION SUBADDRESS 41
INCOMPLETE
160 DRS DIRECT ROUTE SELECT NONE 16
161B AS ALARM STATUS (1) ALARM 28
LEVEL (2)
STAFF
PRESENT
162B AS-R ALARM STATUS-REQUEST NONE 28
163B TAD-R TIME AND DATE-REQUEST NONE 30
164B TAD TIME AND DATE TIME AND 30
DATE ( 6
PARAMETERS)
165 SATB SATELLITE BARRED NONE 16
166 SERV SERVICE INFORMATION SERVICES 16
167 TID TRUNK IDENTITY (1) PBX 16
REFERENCE
NUMBER (2)
TRUNK GROUP
REF NUMBER
(3) TRUNK
MEMBER REF
NUMBER
168B PARK PARK REQUEST NONE 42
169 PKD PARKED NONE 42
ADD-ON CONFERENCE-NO ADD
170 AC-NAO NONE 29
ON CURRENTLY AVAILABLE
171B CBM-R CALL BACK MESSAGING - NONE 36
REQUEST
172B CBM-C CALL BACK MESSAGING - NONE 36
CANCEL
173 NAE-CC NETWORK ADDRESS SUBADDRESS 16
EXTENSION -CALLING/CALLED
IDENTITY COMPLETE
174 NAE-CI NETWORK ADDRESS SUBADDRESS 16
EXTENSION -CALLING/CALLED
IDENTITY INCOMPLETE
175
ADD-ON CONFERENCE-
176B AC-CDC NONE 13
CLEARDOWN CONFERENCE
177 AC-PI ADD-ON CONFERENCE-PARTY CONFERENCE 13
INDEX PARTY INDEX
178
ADD-ON CONFERENCE-DETAILS
179B AC-DR NONE 29
REQUEST
180 AC-PD ADD-ON CONFERENCE-PARTY CONFERENCE 29
DETAILS PARTY
DETAILS
181 AC-CBI ADD-ON CONFERENCE- CONFERENCE 29
CONFERENCE BRIDGE IDENTITY BRIDGE
ADDRESS
182 CH-AC CHARGE REPORTINGACCOUNT ACCOUNT 40
CODE CODE
183B CH-ACR CHARGE REPORTINGACCOUNT NONE 40
CODE REQUEST
184 CH-ACT CHARGE REPORTING-ACTIVE NONE 40
185B CH-CLR CHARGE REPORTING-CLEAR NONE 40
CHARGE REPORTING-COST
186B CH-CR NONE 40
REQUEST
187 CH-CST CHARGE REPORTING-COST (1)CURRENCY 40
UNITS (2)COST
QUALIFIER
(3)CURRENCY
INDICATION
188 CH-TR CHARGE REPORTING-TIME RATE (1)CURRENCY 40
UNITS (2)TIME
INTERVAL
(3)COST
QUALIFIER
(4)CURRENCY
INDICATION
189 CH-UR CHARGE REPORTING-UNIT RATE (1)CURRENCY 40
UNITS (2)COST
QUALIFIER
(3)CURRENCY
INDICATION
CHARGE REPORTING-UNITS
190 CH-UU UNITS 40
USED
191 OPD OUTPUT DIGITS REMOTE 40/189
ADDRESS
192B OPD-R OUTPUT DIGITS - REQUEST NONE 40/189
INTERNAL REROUTING
193 IRD NONE 16
DISABLED
194 ERD EXTERNAL REROUTING NONE 16
DISABLED
195B NLT-PT NON-LOOPED BACK TEST TEST INDEX 27
PERFORM TEST
196B NLT-RQ NON-LOOPED BACK TEST TEST TEST INDEX 27
REQUEST
197B NLT-SC NON-LOOPED BACK TEST NONE 27
SEQUENCE COMPLETE
198B NLT-RES NON-LOOPED BACK TEST TEST RESULT 27
RESULT
A2- 11
CCS Trace
199 AUTO-A AUTOANSWER NONE 16

200 HF-A HANDS-FREE - ACTIVATED NONE 16
201 HF-D HANDS-FREE - DEACTIVATED NONE 16
202B EI-W EXECUTIVE INTRUSION - NONE 10
WITHDRAW
203 DVT-RD DIVERT-REDIRECTION (1) REASON 22
FOR
REDIRECTING
(2) C PARTY
ADDRESS
204 DVT-CF DIVERT-CALL FAILURE C PARTY 22
ADDRESS
205 ASST-INFO ASSISTANCE-INFORMATION TYPE OF 16
ASSISTANCE
206 RED-BY REDIRECTION-BYPASS NONE 22
207
208 VIC VPN INITIATED CLEAR NONE 16
NUMBER PRESENTATION RESTRICTION
NPR-A 48
209 NOTE RESTRICTION-A PARTY DOMAIN
210 NOTE NPR-B NUMBER PRESENTATION RESTRICTION 48
RESTRICTION-B PARTY DOMAIN
211 ARC ROUTE 16
AUXILIARY ROUTE RESTRICTION
RESTRICTION
CLASS
CLASS
212 WOB WAIT ON BUSY NONE 45
GROUP
213B GPU-R GROUP PICK-UP REQUEST 46
PICKUP CODE
214B PU-DVT PICK-UP DIVERT 1)C-PARTY 46
ADDRESS
2)TIME
INTERVAL
215B PU-DVG PICK-UP DIVERTING TIME 46
INTERVAL
216B DPU-R DIRECTED PICK-UP REQUEST PICK-UP CALL 46
TYPE
217 218 RCC-CA ROUTE CAPACITY CONTROL NONE 44
CAPACITY AVAILABLE
ROUTE CAPACITY CONTROL
219 RCC-OI NONE 44
OVERRIDE INVOKED
220 PU-DVD PICK-UP DIVERTED NONE 46
NUMBER PRESENTATION RESTRICTION
NPR-O 48
221 NOTE RESTRICTION - OTHER PARTY DOMAIN
222K MCI MALICIOUS CALL INDICATION MALICIOUS 16
CALL
REFERENCE
223 224 225 NSL NETWORK SIGNALLING LIMIT NONE 16
NOTE: The NPR-A, NPR-B and NPR-O String Identifier Codes shall have no Suffix, an
"A" Suffix or a B" Suffix depending on the requirements of a network with respect to
how PBXs that do not recognise NPR-A, NPR-B or NPR-O should be forced to respond
to their receipt.
226 TCOS TRAVELLING CLASS OF SERVICE (1)ROUTE 47
RESTRICTION
CLASS (2)CALL
BARRING
GROUP
(3)FACILITY
LIST CODE
227B TCOS-R TRAVELLING CLASS OF NONE 47
SERVICE-REQUEST
228B DIV-RSC DIVERSION-REMOTE SET C PARTY 33
COMBINED ADDRESS
229B DIV-RCC DIVERSION-REMOTE CANCEL NONE 33
COMBINED
230 RDC REDIRECTION CONTROL TIMER VALUE 16
231 CAUSE CLEARING CAUSE CLEARING 6
CAUSE
232 CP CALL PROCEEDING NONE 6/189-I
I-BC ISDN-BEARER CAPABILITY BEARER 6/189-I
233 NOTE
CAPABILITY
234 I-CC ISDN-CLEARING CAUSE CAUSE 6/189-I
235 I-CPN ISDN-CALLING PARTY 1) ISDN 6/189-I
/CONNECTED NUMBER NUMBER
ATTRIBUTES 2)
ISDN NUMBER
DIGITS
236A I-CSA ISDN-CALLING PARTY ISDN 6/189-I
/CONNECTED SUBADDRESS SUBADDRESS
237A I-DSA ISDN-DESTINATION (CALLED ISDN 6/189-I
PARTY) SUBADDRESS SUBADDRESS
238 I-HLC ISDN-HIGH LAYER HIGH LAYER 6/189-I
COMPATIBILITY COMPATIBILITY
239 NOTE I-LLC ISDN-LOW LAYER LOW LAYER 6/189-I
COMPATIBILITY COMPATIBILITY
NOTE: This String Identifier Code shall have no Suffix or a "B" Suffix depending on the
outcome of attempting to generate a SIC from Bearer Capability and/or Low Layer
Compatibility (see BTNR 189-I SECTION 4, ANNEX 2 and SECTION 6).
240 I-PROG ISDN-PROGRESS PROGRESS 6/189-I

INDICATOR
(may be
repeated)
241 IPN INTERWORKING VIA A PRIVATE NONE 6/189-I
ISDN
242 SAVE SAVE NONE 6/189-I
A2- 13
CCS Trace
243 V-NID VPN-NODAL IDENTITY VPN ACCESS 16

REFERENCE
NUMBER
244 M-INDEX MESSAGE INDEX INDEX 16
NUMBER
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
Supplementary Information
String Parameters A3
CCS Trace
A3- 2 A3_supp_string_paras.doc
Supplementary Information String
These are the parameters that follow a Supplementary Information String Identifier.
HISTORY
Issue 1 - May 1983 Issue 2 - February 1984 Issue 3 - September 1984 Issue 4 - March 1986
Issue 5 - December 1989 Issue 5.1 - December 1993 - Corrigenda: some pages replaced.
Issue 6 - January 1995:
 New Strings and Parameters added for interworking between DPNSS 1 and ISDN
signalling systems, see BTNR 189-I.
 New Strings and Parameters added for enhanced Sections: 6, 16, 22 and 33.
 New Strings and Parameters added for new Sections: 44, 45, 46, 47 and 48.
 SERVICE MARKING Parameter extended.
 STATUS Parameter extended.
APPENDIX 1, Issue 1 added.
BTNR 188 SECTION 4 ANNEX 2 Issue 6 Page 2 January 1995

GENERAL
This Annex gives details of the Supplementary Information String Identifiers and Parameters
used in DPNSS 1 and is complete at the time of issue.
New Strings and Parameters are continually being added to DPNSS 1, however, for the
following reasons:
 support of new Supplementary Services;
 support of enhanced Supplementary Services;
 additions to Service Independent Strings (SECTION 16);
 support of interworking between DPNSS 1 and other signalling systems.
This Annex is intended to record the master list of Supplementary Information Strings for all
DPNSS 1 applications and will be updated periodically as the BTNRs are reissued. Reference
should be made, however, to BTNR 188, BTNR 189 and BTNR 189-I to ensure that the latest
information is taken into account.
1.1 Use of Strings

In general, Supplementary Information Strings are associated with the Services and
Supplementary Services defined in SECTION 6 onwards.
Some Supplementary Information Strings, however, are not associated with a particular
Supplementary Service Section, and their "First-Use Section" in the list of Identifiers is shown
as SECTION 16. The use of these Strings is described in SECTION 16 of BTNR 188 and
SECTION 16 of BTNR 189 where they are termed "Service Independent Strings".
NOTE: In Subsections 2 and 4 of this Annex the "First-Use Section" refers to BTNR 188
unless indicated otherwise (eg 6/189 refers to a first use in SECTION 6 of BTNR 189).
1.2 Use of Parameters
If a Supplementary Information String has a Parameter, then the use of the Parameter is
mandatory unless otherwise stated.
If more than one Parameter is indicated for a Supplementary Information String, then the
Parameters must be sent in the order specified. If a Parameter is optional it will be sent last.
Where more than one Parameter is optional then, in order to send the second optional
Parameter, it is mandatory to send the first. The rule is extended where more than two
Parameters are optional.
A3- 3
CCS Trace
BTNR 188 Coding of Supplementary Information String Parameters
PARAMETER DESCRIPTION AND CODING

NAME
ACCOUNT CODE This Parameter comprises-a sequence of IA5 numeric characters representing an
account code.
ALARM LEVEL The Alarm Level shall always contain an IA5 numeric character in the range 0-4,
optionally followed by an IA5 alpha character. The first character shall be used as
follows:
Value Name Description
0 None No alarms currently active in the system
1 Low Some alarms active, but no effect on traffic handling
2 Medium Some alarms active which do have an effect on
traffic handling, but the PBX can still function
3 High Alarms active in the system are such that the PBX
operation is greatly affected
4 Alarm No alarm information shall be provided because
reporting maintenance personnel on site have inhibited the
inhibited reporting of alarms
The precise details of when each category is used is dependent upon the PBX
design. The optional alpha character shall be the letter "P" to indicate that the
mains power supply has failed. If this is not present it shall be assumed that power
is available.
A PARTY In general the A Party Address is a digit sequence that represents the address of
ADDRESS the originating caller. The precise meaning of the A Party Address Parameter is
subject to the CLC of the calling party. When the A Party is CLC-ORD or CLC-OP
then the A Party Address is that digit sequence which, when used as a DPNSS 1
Destination Address by any PBX in the network, will cause a call to be routed to
the originating extension or operator. When the A Party is CLC-ISDN, then the A
Party Address shall be a sequence of digits that, if sent as a destination address
to the public network via an access at the Gateway PBX where the call crossed
the public network boundary, would cause a call to be routed via the public
network to that party. In the case of an ETS 300 102 access, the digit sequence
shall be that which would be associated with Numbering Plan Identification and
Type of Number, "Unknown". Depending on the type of number (e.g. local or
national) and the topology of the private network, an A Party Address associated
with CLC-ISDN may also be valid at other public network accesses. It is therefore
recommended that an A Party Address sent by a PBX should have the widest
possible significance throughout the private network. For example, in the case of a
private network within the UK, the full national number including the 11011 prefix
should be used. NOTE: Before it can form a DPNSS 1 Destination Address, an A
Party Address associated with CLC-ISDN may need to be prefixed with digits to
cause routing to a Gateway PBX. When the A Party is CLC-MF5 then the
meaning of the A Party Address depends upon the numbering plan employed by
the private network: -if the DPNSS 1 and SSMF5 parts of the network share a
global numbering plan then the A Party Address is that digit sequence which,
when used as a Destination Address in a DPNSS ISRM, will cause a call to be
routed to the originating SSMF5 extension; - if the DPNSS 1 and SSMF5 parts of
the network have separate numbering plans then the A Party Address is that digit
sequence which, when sent via an SSMF5 route, will cause a call to be routed to
the originating SSMF5 extension (NOTE: Under these circumstances when the A
Party Address is used as a Destination Address in a DPNSS 1 ISRM, it must be
prefixed in order first to route the call to the SSMF5 Gateway). When the A Party
is CLC-PSTN or CLC-DEC the address of the calling party will not be available.
Some PBXs conforming to earlier versions of the BTNR may use the A Party
Address Parameter to convey the Trunk Number. No standardised method of
coding the Trunk Number is specified; this has to be mutually agreed at network
configuration. The A Party Address comprises a sequence of IA5 numeric
characters, each in the range 0-9. The numbers are sent most significant first.
example: Originating Line Identity = 5892 would be encoded as: *50*5892#
This Parameter comprises a sequence of IA5 characters representing the values
of octets 3, onwards of an ISDN Bearer Capability information element, using 3B4I
BEARER encoding (see APPENDIX 1 to this Annex). example: The following Bearer
CAPABILITY Capability information element: Octet 1: identifier Octet 2: length Octet 3:
10010000 Octet 4: 10010000 Octet 5: 10100011 would be encoded as:
*233*dIBc#
A3- 5
CCS Trace
In general the B Party Address is a digit sequence that represents the address of
the second party in a call, e.g. the originally called party in the case of Diversion.
The precise meaning of the B Party Address Parameter is subject to the CLC of
the second party. When the B Party is CLC-OPD or CLC-OP then the B Party
Address is that digit sequence which, when used as a DPNSS 1 Destination
Address by any PBX in the network, will cause a call to be routed to the
associated extension or operator. When the B Party is CLC-ISDN, then the B
Party Address shall be a sequence of digits that, if sent as a destination address
to the public network via an access at the Gateway PBX where the call crossed
the public network boundary, would cause a call to be routed via the public
network to that party. In the case of an ETS 300 102 access, the digit sequence
shall be that which would be associated with Numbering Plan Identification and
Type of Number, "Unknown". Depending on the type of number (e.g. local or
national) and the topology of the private network, a B Party Address associated
with CLC-ISDN may also be valid at other public network accesses. It is therefore
recommended that a B Party Address sent by a PBX should have the widest
possible significance throughout the private network. For example, in the case of a
private network within the UK, the full national number including the "0"prefix
should be used. NOTE: Before it can form a DPNSS 1 Destination Address, a B
B PARTY
Party Address associated with CLC-ISDN may need to be prefixed with digits to
ADDRESS
cause routing to a Gateway PBX. When the B Party is CLC-MF5 then the meaning
of the B Party Address depends upon the numbering plan employed by the private
network: -if the DPNSS 1 and SSMF5 parts of the network share a global
numbering plan then the B Party Address is that digit sequence which, when used
as a Destination Address in a DPNSS ISRM, will cause a call to be routed to the
called SSMF5 extension; - if the DPNSS 1 and SSMF5 parts of the network have
separate numbering plans then the B Party Address is that digit sequence which,
when sent via an SSMF5 route, will cause a call to be routed to the originating
SSMF5 extension (NOTE: Under these circumstances when the B Party Address
is used as a Destination Address in a DPNSS 1 ISRM, it must be prefixed in order
first to route the call to the SSMF5 Gateway). When the B Party is CLC-PSTN or
CLC-DEC the address of the called party will not be available. Some PBXs
conforming to earlier versions of the BTNR may use the B Party Address
Parameter to convey the Trunk Number. No standardised method of coding the
Trunk Number is specified and this has to be mutually agreed at network
configuration. The B Party Address comprises a sequence of IA5 numeric
characters, each in the range 0-9. The numbers are sent most significant first.
example: Diverting from address 1212 on busy. would be encoded as:
*38F*1212#
BREAKDOWN This Parameter is used to set the capability level of a call which may be used to
CAPABILITY breakdown an existing call. The Parameter comprises a decimal number coded as
LEVEL up to two IA5 numeric characters in the Range 0-15.
BREAKDOWN This Parameter is used to set the protection level of a call to guard against
PROTECTION subsequent attempts made to break down the call. The Parameter comprises a
LEVEL decimal number coded as up to two IA5 numeric characters in the Range 0-15.
BUSY SERVICES This Parameter has been renamed "SERVICES".
The Call Barring Group Parameter indicates the party's entitlement to make calls
CALL BARRING to or receive calls from other parties. It comprises a decimal number (from 0
GROUP upwards), coded as one or more IA5 numeric characters, or the null value for this
Parameter which is coded as the IA5 character, hyphen (2/13).
CALL-DIR This Parameter assigns a direction to a call, to provide a datum for subsequent
Supplementary Service requests. It comprises a single IA5 character as follows: 0
= Originating PBX T = Terminating PBX
CALL INDEX This Parameter is a non-zero decimal number coded as up to 3 IA5 numeric
characters used to identify a queued call. This Parameter is optional.
CALL That digit sequence which, when used as a Destination Address will cause routing
REFERENCE back to the PBX which has requested route optimisation and, on arrival at that
NUMBER PBX, identifies the call being optimised.
CAUSE This Parameter comprises a sequence of IA5 characters representing the values
of octets 3, onwards of an ISDN Cause information element, using 3B4I encoding
(see APPENDIX 1 to this Annex) example: The following Cause information
element: Octet 1: identifier Octet 2: length Octet 3: 10000000 Octet 4: 10010000
would be encoded as: 234`I@#
CHANNEL This Parameter is used to identify a specific traffic channel. The Channel Number
NUMBER is encoded as its 5-bit binary equivalent but is transmitted as an IA5 character in
accordance with the following table. On receipt of this Parameter the Terminating
PBX discards bits 6 and 7 of the IA5 character and uses the remaining 5 bits to
identify the Channel Number as in the following table.
5 BIT BLOCK MSB LSB IA5 CHARACTER CHANNEL NUMBER
00000 @ Not Used
0 0,0 0 1 A 1
00010 B 2
00011 C 3
00100 D 4
00101 E 5
00110 F 6
00111 G 7
01000 H 8
01001 1 9
01010 1 10
01011 K 11
01100 L 12
01101 M 13
01110 N 14
01111 0 15
10000 P 16
10001 Q 17
10010 R 18
10011 S 19
10100 T 20
10101 U 21
10110 V 22
10111 W 23
11000 X 24
11001 Y 25
11010 Z 26
11011 [ 27
11100 \ 28
11101 ] 29
11110 ^ 30
11111 _ 31
A3- 7
CCS Trace
CHANNEL The status of the traffic channel is identified by a single IA5 character allocated as
STATUS NAME follows: 1Free 2 Busy 3 Not equipped 4 Back-Busied by Me 5 Back-Busied by You
6 Looped-Back by Me 7 Looped-Back by You 8 Out of Service Further values may
be added in future issues of BTNR 188, BTNR 189 and BTNR 189-I. Where more
than one condition applies they shall all be included in the Parameter, separated
by the IA5 character space (2/0). If the status is indicated as "Not Equipped" or
"Out of Service", no other status may be given. The status "Free" may not
accompany the status "Busy", "Looped-Back by Me" or "Looped-Back by You".
The status "Busy" may not accompany the status "Free", "Looped-Back by Me" or
"Looped-Back by You". The status "Looped-Back by Me" may not accompany the
status "Looped-Back by You".
This Parameter comprises a pair of IA5 characters representing the value of the
Clearing Cause octet received in a CRM, using 1B21 encoding (see APPENDIX 1
CLEARING to this Annex). example: the Clearing Cause: Busy (08H) would be received in a
CAUSE CRM as octet: 00001000 - when used as a Parameter to String RCF, would be
encoded as: *121*@H*1234# (i.e. Redirecting on Call Failure (CC: Busy] to B
Party Address 1234)
CONFERENCE The Conference Bridge Address is that digit sequence which, when used as a
BRIDGE Destination Address, will cause routing back to the Conference PBX and, on
ADDRESS arrival at that PBX, will identify the particular conference bridge or group.
This Parameter comprises any combination of the following details coded in IA5
CONFERENCE
alpha characters as indicated: C = Controller L = Last S = Self If none of these
PARTY DETAILS
details applies this Parameter may be omitted.
CONFERENCE This Parameter comprises a decimal number encoded as one or more IA5
PARTY INDEX numeric characters.
COST QUALIFIER This Parameter consists of an IA5 character indicating how any charging data
received is to be qualified as follows: 0 - VAT not included. 1 - Supplementary
charges not included. Further values may be defined in future issues of BTNR
188, BTNR 189 and BTNR 189-I. If more than one qualification applies, they shall
all be included, separated by the IA5 character space (2/0). example: *187*253*0
1*A# (Note: "A" = CURRENCY INDICATION Parameter) This represents a call
cost of E2-53 excluding VAT and supplementary charges. If no qualifications
apply, the Parameter shall be coded as the IA5 character, hyphen (2/13). Where
no qualifications apply, charging data received may be assumed to indicate the
total cost of the call. Where supplementary charges are not included, the precise
significance of this is dependent on the charging source.
C PARTY That digit sequence which, when used as a Destination Address by any PBX in
ADDRESS the network, will cause the call to be routed to the third party in a call eg, diverted-
to party in the case of diversion. The C Party Address comprises a sequence of
IA5 numeric characters, each in the range 0-9. The numbers are sent most
significant first. example: *40B*3678# Divert this call to address 3678 In the case
of Remote Registration of Diversion Strings DIV-RSB/-RSC/-RSI/-RSR this
Parameter is optional.
This Parameter comprises a single IA5 character which indicates the currency in
CURRENCY which any associated currency units are specified. A - Pence (UK) Further values
INDICATION may be defined in future issues of BTNR 188, BTNR 189 and BTNR 189-I. This
Parameter is optional. If not present, a default currency must be assumed.
This Parameter comprises a sequence of IA5 numeric characters or a sequence of
IA5 numeric characters followed by another IA5 character sequence consisting of
CURRENCY the IA5 character "dot" (2/14) and a sequence of IA5 numeric characters. This
UNITS Parameter represents monetary cost, in the units of the given or assumed
currency, to N decimal places, where N is the number of numeric characters in the
second sequence (N=O if the second sequence is not present).
DEVICE INDEX This Parameter is a decimal number coded as up to 2 IA5 numeric characters
which can be used to sub-divide a DA, OLI, or CLI in order to identify uniquely a
particular device.
DIVERSION TYPE It comprises a single IA5 character, used as follows: I - Diversion Immediate B -
Diversion On Busy R - Diversion On No Reply This Parameter indicates the type
of diversion used.
Enhanced String ID comprises a copy of the IA5 numerals and suffix letter of one
Supplementary Information String Identifier or a single IA5 alpha character,
indicating one of the following: A = Unrecognised Maintenance Action E = Syntax
Error F = Selection Block capacity exceeded M = Missing Information R = Recall
ENHANCED not supported S = Unrecognised SIC example 1: *94*22B# The request for
STRING ID intrusion protection level was not understood. example 2: *94*E# Syntax Error In
the case of NSI Strings however, it is necessary to allow for the first Parameter of
the the NSI String to be included as part of the Parameter "Enhanced String ID". In
this case the NSI Parameter is separated from the ID(58) and suffix by a
semicolon. example: *94*58B;AA# The String 58B*AA was not understood.
The Facility List Code Parameter indicates the facilities the party is allowed to use.
FACILITY LIST
It comprises a decimal number (from 0 upwards), coded as one or more IA5
CODE
numeric characters, or the null value which is the IA5 character, hyphen (2/13).
GROUP PICK-UP The Group Pick-Up Code is a Parameter which indicates a network-wide
CODE group of extensions. It comprises a decimal number (from 0 upwards), coded as
one or more IA5 numeric characters.
HC-CLC The Parameter HC-CLC gives the Called/Calling Line Category of the held party.
This Parameter comprises a single IA5 numeric character allocated as follows: 1
Ordinary 2 Decadic 3 ISDN 4 PSTN 5 SSMF5 6 Operator 8 Conference example:
*80*1# Enquiry call with an ordinary extension on hold.
of octets 3, onwards of an ISDN High Layer Compatibility information element,
HIGH LAYER
using 3B4I encoding (see APPENDIX 1 to this Annex). example: The following
COMPATIBILITY
High Layer Compatibility information element: Octet 1: identifier Octet 2: length
Octet 3: 10010001 Octet 4: 10000100 would be encoded as: *238*dXP#
INDEX NUMBER This Parameter comprises a sequence of up to three IA5 numeric characters
representing a message index number between 0 and 255 (decimal).
INTRUSION
The Intrusion Capability level comprises a single IA5 numeric character 0, 1, 2 or 3
CAPABILITY
example: *21*1# Executive Intrusion Request with ICL 1
LEVEL
INTRUSION
The Intrusion Protection-Level comprises a Single IA5 numeric character 0, 1, 2,
PROTECTION
or 3 example: *23*2# IPL = 2
LEVEL
This Parameter comprises a sequence of IA5 characters representing the value of
octet 3 of an ISDN Calling Party Number or Connected Number information
ISDN NUMBER
element, using 3B4I encoding (see APPENDIX 1 of this Annex). The example of
ATTRIBUTES
encoding the ISDN NUMBER DIGITS Parameter includes an example of how to
encode this Parameter.
This Parameter comprises a sequence of IA5 numeric characters representing the
number digit octets (octet 4, and any repetitions) of an ISDN Calling Party Number
or Connected Number information element. The most significant (spare) bit of
each number digit octet is deleted and the remaining seven bit codes are the IA5
ISDN NUMBER numeric character codes of TABLE 1 of BTNR 188, SECTION 4, ANNEX 4. The
DIGITS following example shows the encoding of both an ISDN NUMBER ATTRIBUTES
and an ISDN NUMBER DIGITS Parameter as contained in an ISDN Calling Party
Number information element: Octet 1: identifier Octet 2: length Octet 3: 11001001
1st Octet 4: 00110010 2nd Octet 4: 00110101 3rd Octet 4: 00111001 4th Octet 4:
00110101 would be encoded as: *235*rP*2595#
A3- 9
CCS Trace

of octets 3, onwards of an ISDN Called Party Subaddress, Calling Party
Subaddress or Connected Subaddress information element, using 3B4I encoding
ISDN
(see APPENDIX 1 to this Annex). example: The following Calling Party
SUBADDRESS
Subaddress information element: Octet 1: identifier Octet 2: length Octet 3:
10000000 Octet 4: 01010000 Octet 5: 01000001 Octet 6: 01000010 would be
encoded as: *236A*IEAAPI#
ISDN TYPE This Parameter represents the type of public ISDN interface encountered. It
comprises a single IA5 character as follows: A = ETS 300 102 B = DASS 2 Further
types may be added in later issues of BTNR 188, BTNR 189 or BTNR 189-I. This
Parameter is optional. If not present then this shall be taken to indicate that no
specific information about the type of ISDN interface is available. A PBX may,
where necessary, make assumptions about the signalling type when this
Parameter is not present.
LOCATION The location of the failure is identified by using an IA5 character allocated as
follows: T - Other terminal P - Call Path E - Equipment needed to make the
connection I - Incompatible due to clash of services If more than one is applicable,
the one appearing first in the above list shall be used.
COMPATIBILITY This Parameter comprises a sequence of IA5 characters representing-the values
of octets 3, onwards of an ISDN Low Layer Compatibility information element,
using 3B4I encoding (see APPENDIX 1 to this Annex). example: The following
Low Layer Compatibility information element: Octet 1: identifier Octet 2: length
Octet 3: 10001000 Octet 4: 10010000 Octet 5: 00100001 Octet 5a: 01000101
Octet 5b: 00100000 Octet 5c: 10110011 would be encoded as: *239*bI@aQRBs#
This Parameter is an IA5 numeric character sequence comprising up to 3 digits for
MALICIOUS CALL
identifying a request to trace a malicious call a DPNSS 1 network. This Parameter
REFERENCE
is optional. It may be omitted if Malicious Call References are not used.
This Parameter is used to indicate the number of hunt groups that the call has
passed through. It comprises a single IA5 numeric character in the range 1-9 to
NESTING LEVEL
represent the level of nesting . This Parameter is optional; omission of the
Parameter indicates a nesting level of 1.
The Night Service Address is that digit sequence which, when used as a
Destination Address, will cause a call to be routed to the Night Service point. This
NIGHT SERVICE Parameter comprises a sequence of IA5 numeric characters each in the range 0 -
ADDRESS 9, sent most significant first. example: -128A*3678# (Night Service - Divert to
address 3678) This Parameter is optional. It may be omitted if no address is
available.
NSI IDENTIFIER This Parameter consists of two IA5 characters indicating a manufacturer and a
manufacturer-specific code. The first character is as allocated in TABLE 1 of
SECTION 15 of BTNR 188. The second character may be any IA5 character legal
for use in a Supplementary Information String Parameter.
This indicates the number of unanswered calls currently waiting on an extension
NUMBER OF
number, or the position of a call currently queued. The Parameter comprises a
CALLS
decimal number coded as up to two IA5 numeric characters.
NUMBER OF This Parameter is optional. If included it specifies the number of further alternative
FURTHER routes allowed during routing of the call. It comprises a single IA5 alpha character
ALTERNATIVE in the range A-Z; A representing 0 and Z representing 25.
ROUTES
NUMBER OF This Parameter is the count of the number of further Transit PBXs allowed to route
FURTHER the call. It comprises a single IA5 alpha character in the Range A-Z; A
TRANSITS representing 0 and Z representing 25.
The Number of Servers Parameter indicates the number of positions capable of
NUMBER OF
answering the queued calls. The Parameter comprises a decimal number coded
SERVERS
as up to two IA5 numeric characters.
PASSWORD This Parameter comprises up to 12 IA5 alphanumeric characters which may be
used as a password. When used with Travelling Class of Service Request (TCOS-
R) this Parameter is optional.
PBX FLAG This Parameter is optional. If included it contains the single IA5 character 'IS" to
indicate that the address contained in the previous Parameter is on the same PBX
as the sender of the message.
This is the sequence of IA5 numeric characters used to identify the PBX sending
PBX REFERENCE
the TID String.
NUMBER When used as the Destination Address it will cause routing to the sending PBX.
The Pick-Up Call Type Parameter gives the type of Pick-Up required. It comprises
a single IA5 character allocated as follows: R = Ringing call H = Held call W =
PICK-UP CALL Waiting call P = Parked call More than one Type may be included in the
TYPE Parameter, each being separated by the IA5 character space (2/0). Where more
than one Type is included, PBX-T shall assign its own priority. This Parameter is
optional and if omitted then PBX-T shall assign its own Type and priority
PRIORITY LEVEL This Parameter comprises a sequence of up to three IA5 numeric characters
representing a priority level between 0 and 255 (decimal).
of octets 3, onwards of an ISDN Progress indicator information element, using
PROGRESS
3B4I encoding (see APPENDIX I to this Annex). example: The following Progress
INDICATOR
Indicator information element: Octet 1: identifier Octet 2: length Octet 3: 10000010
Octet 4: 10000010 would be encoded as: *240*`hH#
This Parameter consists of two IA5 characters. The first character defines the
state of the call before redirection:A = Awaiting answer H = Held W = Waiting on
REASON FOR
busy The second character indicates whether the call was transferred into that
REDIRECTING
state:E = Transferred by an extension N = Not transferred 0 = Transferred by an
operator R = Transferred by the party to whom the call is being redirected
That digit sequence which, when used as a Destination Address, will cause a call
to be routed to the party to whom reconnection is required. This Parameter
RECONNECT
comprises a sequence of IA5 numeric characters, each in the range 0-9. The
ADDRESS
numbers are sent most significant first. example: *124B*123456# Reconnect a
caller who has requested Series Call Supplementary Service to address 123456.
REMOTE This Parameter comprises a sequence of IA5 numeric characters representing the
ADDRESS digits output by a Gateway PBX to another signalling system.
RESTRICTION This Parameter indicates the domain in which number presentation
DOMAIN restriction applies and comprises a single IA5 numeric character allocated as
follows: 1 = Private 2 = Public Further values may be added in future issues of
BTNR 188, BTNR 189 and BTNR 189-1. Where more than one restriction applies
they shall each be included in the Parameter, separated by the IA5 character,
space (2/0). This Parameter is optional; its omission indicates total restriction.
ROUTE The Route Restriction Class Parameter indicates the routing entitlements of the
RESTRICTION party.
CLASS It comprises a decimal number (from 0 upwards), coded as one or more IA5
numeric characters, or the null value which is the IA5 character, hyphen (2/13).
A3- 11
CCS Trace
Routing Information comprises a single IA5 numeric character allocated as

follows: 1 Alternative Route 2 3 Public ISDN encountered These values are (see
NOTE 1) used when inter-4 PSTN encountered working with 5 Decadic
encountered other signalling (see NOTE 2) systems see 6 - MF5 encountered
BTNR 189 and 7 - Private ISDN encountered BTNR 189-I NOTE 1: In earlier
issues of BTNR 188 and BTNR 189 Parameter value 3 indicated DASS 2
encountered. The scope of this value has since been expanded to cover access to
the public ISDN in general. NOTE 2: In earlier issues of BTNR 188 and BTNR 189
Parameter value 5 indicated 10 pps encountered. The scope of this value has
ROUTING since been expanded to cover access to non-DPNSS 1 private circuits in general.
INFORMATION Further Routing Information codes may be added in later issues of BTNR 188,
BTNR 189 and BTNR 189-I. More than one routing information digit can be
included in the Parameter each being separated by the IA5 character space (2/0).
example: *51*1 4# alternative route taken via the PSTN. Where the same value
occurs more than once it shall be treated by the receiving PBX as if the value
appeared only once. Values that are not recognised may be ignored and the
String processed on the remainder of the Parameter values. Transit PBXs shall
pass on the complete Parameter, including the unrecognised values. If none of the
values in the Parameter is recognised, the String shall be treated as if the
Parameter were missing.
The Service Marking Parameter supplements the Calling or Called Line Category.
It comprises a single IA5 character allocated as follows: 1 = PSTN BARRED 2 =
EMERGENCY TELEPHONE 3 = HUNT GROUP 4 = DISTRIBUTED GROUP 5 =
UNABLE TO INITIATE CLEARING AFTER ANSWER (Note) Further Service
Marking Codes may be added in later issues of BTNR 188, BTNR 189 and BTNR
189-I. More than one Service Marking character can be included in the Parameter,
each being separated by the IA5 character space (2/0). If one (or more) of the
allocated codes is (are) not present in this Parameter then the receiving PBX shall
presume the negation of the associated attribute(s): example: *1*2 3# = CLC-
ORD: NOT PSTN BARRED, EMERGENCY TELEPHONE, HUNT GROUP,NOT
DISTRIBUTED GROUP, ABLE TO INITIATE CLEARING AFTER ANSWER. If no
SERVICE
Parameter value is to be included then the Supplementary String Identifier shall he
MARKING NAME
followed by a # and all the associated attributes shall be presumed by the
receiving PBX to be negated. example: *1# = CLC-ORD: NOT PSTN BARRED,
NOT EMERGENCY TELEPHONE, NOT HUNT GROUP, NOT DISTRIBUTED
GROUP, ABLE TO INITIATE CLEARING AFTER ANSWER. Where the same
value occurs more than once, it shall be treated by the receiving PBX as if the
value appeared only once. Values that are not recognised may be ignored and the
String processed on the remainder of the Parameter values. Transit PBXs shall
pass on the complete Parameter including the unrecognised values. If none of the
values in the Parameter is recognised, the String shall be treated as if the
Parameter were missing. Note: The value 5 of this Parameter gives no indication
of the ability (or inability) to initiate clearing before answer.
SERVICES The SERVICES Parameter is a single IA5 character allocated as follows: 1 = Call
Offer not possible 2 = Executive Intrusion not possible 3 = Call Back When Free
not possible 4 = Call Back Messaging not possible (see Note) 5 = Hold not
possible 6 = Call Back When Next Used not possible Note: In BTNR 188, Issue 4,
this value of the Parameter represented "Call Back Messaging possible". This has
been changed here to harmonise with the other attributes of the Parameter which
are all negative. Further values may be added in later issues of BTNR 188, BTNR
189 and BTNR 189-1. More than one character may be included in the Parameter,
each being separated by the IA5 character space (2/0). If one (or more) of the
allocated codes is (are) not provided for this Parameter then the receiving PBX
shall not presume that the associated ,Supplementary Service(s) is (are) available.
example: *166*1 3# Service information indicating that neither Call Offer nor Call
Back When Free are possible. Other Supplementary Services may be possible. if
the same value occurs more than once it shall be treated by the receiving PBX as
if the value appeared only once. Values that are not recognised may be ignored
and the String processed on the remainder of the Parameter values. Transit PBXs
shall pass on the complete Parameter including the unrecognised values. If none
of the values in the Parameter is recognised, the String shall be ignored.
SIC This Parameter comprises a sequence of IA5 characters representing the value of
the SIC octet(s), using 1B21 encoding (see APPENDIX 1 to this Annex). example:
BSS-M; 48 kbit/s data; X30 Synchronous, full duplex, byte timed, X25 packet,
clock locked to transmission. (ie SIC Octets: 10100010, 00110100). would be
encoded as: *47R*JBCD# This Parameter may be used to carry either a DPNSS 1
SIC in association with a SIC String, or a DASS 2 SIC in association with a D-SIC
String. It should be noted that, whilst DPNSS 1 SICs are a maximum of 2 octets in
length, DASS 2 SICs may be extended in future issues of BTNR 190 to more than
2 octets.
STAFF PRESENT This indicates whether maintenance staff are on site. If so, no action need be
taken if alarms are being raised. It comprises a single IA5 character, used as
follows: Y - Staff are on site. N - No staff are on site. This Parameter is optional. If
the Parameter is omitted it shall be assumed that no staff are present.
This Parameter indicates the State of Destination of the called party and is used
STATE OF
as an adjunct to a Supplementary Information String used in a Clear Request
DESTINATION
Message. It comprises a single IA5 character allocated as follows: B Busy F - Free
This Parameter consists of a single IA5 alpha character allocated as follows: N =
STATE OF
The Operator group or specific position has night mode activated. D = The
OPERATOR
Operator group or specific position has night mode deactivated (day mode).
STATUS The Status Parameter supplements the Calling Line Categories: DEC, ISDN,
PSTN and MF5. It comprises a single IA5 character allocated as follows: 1 = Non-
DDI 2 = No Release Signal at any point in the call 3 = Release only available after
Answer 4 = outgoing 5 = Null Further Status codes may be added in later issues
of BTNR 188, BTNR 189 and BTNR 189-I. More than one Status Character can
be included in the Parameter, each being separated by the IA5 character, space
(2/0). If one (or more) of the codes 1 - 4 is (are) not present in this Parameter then
the receiving PBX shall presume the negation of the associated attribute(s) as in
the following examples:
*2*1# = CLC-DEC: Non-DDI, (Can release at any time), (Incoming). *2*3 4# =
CLC-DEC: (DDI), Can release only after Answer, Outgoing. *4*2 4# = CLC-PSTN:
(DDI), Can never release, Outgoing. Note: Deduced values are shown in brackets
The Parameter value 5 shall be used when no other Parameter value is to be
included and it is required to add a second Parameter to the String, e.g. "ISDN
TYPE" in the case of CLC-ISDN. If no Parameter value 1 - 4 is to be included and
no second Parameter is to be added, then the Supplementary String Identifier
shall be followed by #.
examples: *3# = CLC-ISDN: no Parameter value 1 -4 and no "ISDN Type"
Parameter present. *3*5*B# =CLC-ISDN: no Parameter value 1 -4 and ISDN
Interface explicitly identified as DASS 2. *3*2 4*A# = CLC-ISDN: Parameter
values 2 and 4 are applicable and ISDN Interface explicitly identified as ETS 300
102. Where the same value occurs more than once, it shall be treated by the
receiving PBX as if the value appeared only once. where the values 2 and 3
appear together, the value 3 shall be ignored. The values 1 and 4 should not be
considered contradictory, as the value 1 refers to the DDI characteristics of the
trunk whenever it is used incoming, whereas the value 4 refers to the direction of
use of the trunk on the current call. For the purposes of supplying and interpreting
the value 3, Answer should be considered as the sending or receiving of a valid
CCM irrespective of whether it contains the String SIM-A. A trunk should be
considered able to Release only if a Release signal is guaranteed by a normal
event (e.g. a timeout or user action). If Release is possible (e.g. via a maintenance
action) but not guaranteed under normal operation, the trunk should be
considered as unable to Release. Once a particular trunk has been allocated its
STATUS Parameter(s) for a given call, that allocation shall remain fixed for the
duration of that call. Values that are not recognised may be ignored and the String
processed on the remainder of the Parameter values. Transit PBXs shall pass on
the complete Parameter including the unrecognised values. If none of the values
in the Parameter is recognised, the String shall be treated as if the Parameter
were missing.
A3- 13
CCS Trace
STRING ID The Parameter String ID comprises a copy of the IA5 numerals and suffix letter of
one Supplementary Information String Identifier. example: *95*27# The Call Offer
Service is unavailable at the called extension. In the case of NSI Strings, however,
it is necessary to allow for the first Parameter of the NSI String to be included as
part of the Parameter "String ID". In this case the NSI Parameter is separated from
the ID (58) and Suffix by a semicolon. example: *95*58B; AA# (String 58B*AA
rejected because service is unavailable)
STRING ID LIST String ID List comprises a copy of the IA5 numerals and suffix letter of one or
more Supplementary Information String Identifiers. Where more than one is
included they shall be separated by a space (2/0). example *98*481 49I# The
requests for Bearer Service Selection (Preferred) and Bearer Service Selection
(Notification) were not understood, and were ignored. In the case of NSI Strings,
however, it is necessary to allow for the first Parameter of the NSI String to be
included as part of the Parameter "String ID List". In this case the NSI Parameter
is separated from the ID (58) and Suffix by a a semicolon. example: *98*58A;AB
58A;AC# (Strings 58A*AB and 58A*AC ignored not understood)
SUBADDRESS This Parameter comprises either a sequence of IA5 numeric characters (maximum
40) or a sequence of IA5 characters representing a sequence of binary octets
(maximum 20) using IB2I encoding (see APPENDIX 1 to this Annex).
TEST INDEX This Parameter indicates the test to be performed on the associated traffic
channel. It is coded as a sequence of IA5 numeric characters, the significance of
which is a matter for negotiation between the suppliers of the PBXs connected via
the traffic channels. This Parameter is optional and may be omitted if the default
test for the traffic channel is to be used.
TEST RESULT This Parameter indicates the result of a test by means of a single IA5 numeric
character allocated as follows: 0 = Pass 1 = Fail 2 = Aborted
TEXT This Parameter is used to indicate the textual information required for display. It
may be up to 24 IA5 characters, with the * represented by TC1 (0/1) and the #
represented by TC2 (0/2).
TEXT TYPE This Parameter is optional and defines the type of text provided in the String. It
comprises a single IA5 character allocated as follows: 1 = Name 2 = Message 3 =
Reason for call failure Further TEXT TYPE values may be added in later issues of
BTNR 188, BTNR 189 and BTNR 189-1. If the Parameter is not present no
meaning may be assumed. Values which are not recognised may be ignored, the
String being treated as if the Parameter were missing.
This comprises six Parameters which are structured as follows:
Parameter 1: Year (4 IA5 numeric characters) Parameter 2: Month (2 IA5 numeric
characters in the range 01 to 12). Parameter 3: Day of the month (2 IA5 numeric
characters in the range 01 to 31). Parameter 4: Hour of the day (2 IA5 numeric
TIME AND DATE characters in the range 00 to 23). Parameter 5: Minute of the hour (2 IA5 numeric
characters in the range 00 to 59). Parameter 6: Second (2 IA5 numeric characters
in the range 00 to 59). These six Parameters must always be sent as a block and
in the above order: example: *164B*1994*10*21*15*35*11# The time and date is
3.35 and 11 seconds pm, 21 October 1994.
TIME INTERVAL This Parameter comprises a sequence of IA5 numeric characters or a sequence of
IA5 numeric characters followed by another IA5 character sequence consisting of
the IA5 character "dot" (2/14) and a sequence of IA5 numeric characters. This
Parameter represents a time interval in seconds to N decimal places where N is
the number of numeric characters in the second sequence (N=O if the second
sequence is not present). When used with Call Pick-Up Strings PU-DVG and PU-
DVT this Parameter is optional. Its omission indicates that no Time Interval value
is available.
TIMER VALUE This Parameter is optional. It comprises a sequence of IA5 numeric characters
representing a timer value as an integer number of seconds.
TRUNK GROUP This is the sequence of IA5 numeric characters used to identify a Trunk Group at a
REFERENCE particular PBX.
NUMBER
TRUNK MEMBER This is the sequence of IA5 numeric characters used to identify a Trunk Member
REFERENCE within a Trunk Group at a particular PBX.
NUMBER
This Parameter comprises a single IA5 alpha character followed by a single IA5
numeric character. The alpha character defines the assistance type as follows: E
= A call from outside the private network seeking assistance for the first time. I = A
TYPE OF call from within the private network seeking assistance for the first time. R = A call
ASSISTANCE already handled by an operator seeking assistance again. The numeric character
comprises a number between 0 and 9 and offers the possibility to differentiate
priority within a given assistance type. The higher the number the higher the
priority.
UNITS This Parameter comprises a sequence of IA5 numeric characters representing a
number of charge units as a decimal number.
VPN ACCESS
This is a sequence of IA5 numeric characters used to identify the path of entry to a
REFERENCE
VPN.
NUMBER
A3- 15
CCS Trace
Clear Request Message/Clear
Information Message
(CRM/CIM)
A4
CCS Trace
A4- 2 A4_crm_cim.doc
Clear Request Message/Clear Information Message (CRM/CIM)
Clear Request Message/Clear Rejection Message (CRM/CIM)
VALUE CLEARING/REJECTION MEANING MNEMONIC

CAUSE
29 Access Barred Used when a particular caller is barred access to AB
outgoing routes.
14 Acknowledgement Used to inform the Requesting PBX that the ACK
Supplementary Service has been (or is being)
carried out.
01 Address Incomplete Used when insufficient address digits have been AI
received to achieve a valid address, unless conflict
dialing is permitted. Where conflict dialing is
permitted, NU shall be used.
08 Busy Used when the called party is engaged on a call. BY
23 Channel Out of Service Used to reject a call received on a channel which is CHOS
out of service or uninstalled.
2D DTE Controlled Not Ready Used when the called X.21 terminal is in the CNR
"Controlled Not Ready" state.
07 Congestion Used when PBX equipment or suitable routes are CON
busy.
30 Call Termination Used when a party releases a call by clearing in CT
the normal way.
18 Facility Not Registered Used when a PBX receives a request relating to a FNR
service where previous knowledge of its existence
is necessary, but that knowledge does not exist
(e.g. a Call Back When Free call made to a PBX
with no record of the original registration).
OA Incoming Calls Barred Used when the called party is barred to incoming ICB
calls.
13 Service Incompatible Used when the route available does not conform to INC
the required SIC.
1A Message Not Understood Used when rejecting an unrecognised message on MNU
an idle channel. Note that the channel on which
MNU was received may not be the one on which
the unrecognised message was detected because
Transit PBXs pass on Clearing Causes
unchanged.
1E Network Address Extension- Used to inform the Requesting PBX that a call has NAE-E
Error been rejected because of failure to process the
received NAE data.
02 Network Termination Used when the call is released by the network for NT
any reason (eg due to a timeout expiring, or
service interactions).
0 Number Unobtainable Used when the Destination Address is invalid (i.e. NU
spare).
24 Priority Forced Release Used when an authorised intruding party forces the PFR
release of an unwanted party, e.g. an operator or a
party with the required Breakdown Capability
19 Reject Used when the requesting or requested party of a REJ
Supplementary Service rejects the service (e.g.
Wanted party rejects a Call Offer request).
IC Route Out of Service Used when all suitable routes are out of service. ROS
A4- 3
CCS Trace
04 Used when the called party does not SI

conform to the requested SIC.
15 Used when rejecting message contents SNU
which have not been understood. This CC
is accompanied by the string SNU. SNU
either identifies a String which has not
been understood or indicates another
reason for not understanding the message
(e.g. syntax error).
16 Used only when a PBX working to Issue 1 SNV
of DPNSS 1 rejects a String that is invalid.
09 Used when the called party is out of SOS
service.
1B Used when the requested Service is not SSI
supported by the route available and there
is no other suitable route.
17 Used when the requested Service is STU
available on the PBX but can not be
provided at the moment.
03 Used when the requested Service is SU
supported by the PBX but not by the
called party. This Clearing Cause is
accompanied by the String SU which
identifies the Service being rejected.
1D Used (by issues 2 & 3 PBXs only) to TRFD
instruct the Branching PBX of a 3-party
call to connect the two remaining parties
together.
2E Used when the called X.21 terminal is in UNR
the "Uncontrolled Not Ready" state.
A4- 4 A4_crm_cim.doc

CCS Trace

Uploaded by

Document Information

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

CCS Trace

Uploaded by

Copyright:

Available Formats

MITEL

Issue 1 – 25th March 2011

Inter-Tel® is a registered trademark of Inter-Tel (Delaware), Incorporated.

© 2011 Mitel Networks Corporation

Appendix 01 – CCS Trace Message Descriptions

Appendix 02 – Supplementary Information String Identifiers

Appendix 03 – Supplementary Information String Parameters

Appendix 04 – CRM/CIM Messages

 Use and understand the CCS Trace Commands

Common Channel Signalling – CCS ............................................................................................5

Common Channel Signalling – CCS

CCS TRACE DISABLE - CCS Trace is disabled, monitoring stops.

CCS TRACE CLEAR CONTINUOUS - Resets channels to ALL for tracing.

CCS Trace Message Structure

CCM – Call Connect Message. The call has been connected.

CRM/CIM – Clear Request Message/Clear Information Message. This final message

CCS Trace Message Details

Taking each line in turn, this is how the message is interpreted.

11:46:45 RO6000 DPN 23 ISRM_I ;10; *1# *50*1102# *100*J.Digby*1# *19*Z#

1. Time the call was made

IDENTIFIER MNEMONIC SUPPLEMENTARY INFORMATION PARAMETER FIRST USE

8. *50*1102# - This is another Supplementary String Identifier (*50) which means

IDENTIFIER MNEMONIC SUPPLEMENTARY INFORMATION PARAMETER FIRST

9. *100*J.Digby*1# - *100 Supplementary String Identifier means Textual Display

Supplementary Information String Parameters

IDENTIFIER MNEMONIC SUPPLEMENTARY PARAMETER FIRST USE

Supplementary Information String Parameters

Taking the next line in the trace

11:46:45 RO6000 DPN 2D SSRM_I *58*CW*IOpj@@@@@IpF]p# *58*C6*001# *58*C4*4*1#

5. SSRM_I – Subsequent Service Request Message Incomplete. Continuation of the

11:46:45 RO6000 DPN 5 SSRM_C 1750

5. SSRM_C – Subsequent Service Request Message Complete. The message started

Taking the next line in the trace

11:46:46 RI6000 DPN 1B NAM *1# *50*1750# *100*D.Dare*1#

5. NAM – Number Acknowledgement Message.

11:46:48 RI6000 DPN 1 CCM

Taking the next 2 lines in the trace

11:46:48 RO6000 DPN 2 CRM/CIM ;30;

5. CRM/CIM ;30; – Clear Request Message/Clear Information Message. The CRM is

Examples of other CCS Traces

PRI call – called number is busy

Incoming call on channel 102 from mobile 07530198766 to extension 431430.

PRI call – called number is invalid (not recognised by the 3300)

IP and SIP Trunk Traces

Below are some examples of calls.

Outgoing from ext 1102 to 1750 - answered

Outgoing from ext 1102 to 1750. 1750 diverts to VM which answers

09:35:39 ROX DPN PBX2 3 3 D** B** 23 ISRM_ ;10;*1#*50*1102#*100*J.Digby*1#*19*Z#

Incoming call on SIP Peer CandW_SIP from 8706095050 to 1011817 P.Waters

Using CCS Trace as a Diagnostic Tool

Basic Call Interpretation

Example: PRI call outgoing from a 3300

Example: multiple SSRM messages. ARS not programmed correctly.

CCS Trace Message Descriptions

Supplementary Information String Identifiers

BTNR 188 SECTION 4 ANNEX 2 Issue 6 Page 2 January 1995

1.1 Use of Strings

CODING OF SUPPLEMENTARY INFORMATION STRING IDENTIFIERS

CALL BACK WHEN NEXT

18 COS CLASS OF SERVICE (1)ROUTE 16

39F DVG-R DIVERTING ON NO REPLY B PARTY 11

65 SOD-B STATE OF DESTINATION-BUSY NONE 9

99 IG-SU IGNORED-SERVICE STRING ID 18

128A NS-DVT NIGHT SERVICE-DIVERT (1) NIGHT 25

11:46:45 RO6000 DPN 23 ISRM_I ;10; 1# 501102# 100J.Digby1# 19Z#

8. 501102# - This is another Supplementary String Identifier (*50) which means

9. 100J.Digby1# - 100 Supplementary String Identifier means Textual Display

11:46:45 RO6000 DPN 2D SSRM_I 58CWIOpj@@@@@IpF]p# 58C6001# 58C441#

11:46:46 RI6000 DPN 1B NAM 1# 501750# 100D.Dare1#

09:35:39 ROX DPN PBX2 3 3 D B 23 ISRM_ ;10;1#501102#100J.Digby1#19Z#