CCS Trace Commands
CCS Trace Commands
CCS Trace
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. Nothing in this document may be reproduced in any manner, either wholly or in part for any use whatsoever, without written permission from Mitel Corporation.
TRADEMARKS
Mitel design is a registered trademark of Mitel Corporation. MediaPath is a trademark of Mitel Corporation. Microsoft is a registered trademark of Microsoft Corporation. Windows, Windows 95, Windows NT, Microsoft Exchange and, Microsoft BackOffice and SBS are trademarks of Microsoft Corporation.
FURTHER INFORMATION
Further information on Mitel Training courses may be found on the World Wide Web at;
www.mitel.com/uktraining
, , Trademark of Mitel Corporation. Copyright 1999, Mitel Corporation. All rights reserved. Printed in the United Kingdom
MITEL
Product Training
Mitel Telecom Ltd Mitel Business Park Portskewett Monmouthshire NP26 5YR Telephone: +(44) (0) 1291 430000 Fax: +(44) (0) 1291 430400
http://www.mitel.com
Table of Contents
CCS Trace Command.................................................................................................................... 4 CCS Trace Examples .................................................................................................................... 5 Normally Connected Call............................................................................................................ 5 Call Not Connected .................................................................................................................... 9 Examples of other calls .............................................................................................................. 9 Explanation of CCS Terms .......................................................................................................... 11 CODING OF SUPPLEMENTARY INFORMATION STRING IDENTIFIERS................................ 14 CODING OF SUPPLEMENTARY INFORMATION STRING PARAMETERS ............................. 31 TABLE OF CLEARING/REJECTION CAUSE CODES (CRM/CIM) ......................................... 53
Page - i
Page - 4
Actual CCS Trace RO130 DPN 2B ISRM_C ;10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400 RI130 DPN 20 NAM RI130 DPN 1 CCM RI130 DPN 2 CRM/CIM ;30; Explanation of trace: First line RO130 DPN 2B ISRM_C ;10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400
1 2 3 4 5 6 7 8 9 10
*1*1#*50*832400#*100*G.Rodgers#
Page - 5
BTNR 188 Coding of Supplementary Information String Parameters SERVICE MARKING 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
Page - 6
7 - *50*822300# Second Supplementary Information String Identifier. *50 is the Identifier (* marks the beginning). There is no # but another * indicating a string parameter follows. 50 means Originating Line Identity/Called Line Identity (from BTNR 188 Supplementary Information String Identifiers). The string parameter 822300 is the extension number of the calling party. So this basically means that 822300 made the call. 8 - *100*D.Sykes# Third Supplementary Information String Identifier (again with * at the beginning, the second * shows a string parameter follows). 100 means Text Display and the parameter (D.Sykes) is the text value, in this case the name on calling extension 822300. 9 *19*Z# Fourth Supplementary Information String Identifier (again with * at the beginning, the second * shows a string parameter follows). 19 means loop avoidance and the parameter is either Number of further alternative routes or Number of further transits. From the Coding of Supplementary String Parameters the value Z indicates 25. In other words a further 25 hops (26 is the maximum allowed). The hops can be set in the SX-2000/3300 trunk programming. This value shows it is has not been changed from default. 832400 Destination Address. There are no more Supplemental String Identifiers (they would be shown with a * prefix) so the final information is the Called Party, in this case extension 822401. Second Line RI130 DPN 20 NAM *1*1#*50*832400#*100*G.Rodgers#
1 2 3 4 5 6 7
1 - RI130 This is a Real Call (R), Incoming (I) and B Channel 130 was used. 2 - DPN DPNSS protocol used. 3 - 20 Length of the message in hexadecimal 4 - NAM Number Acknowledge Message. The called number is available. If the phone was not available (busy, or no answer or invalid number dialled) there would be no NAM. Page - 7
1 - RI130 This is a Real Call (R), Incoming (I) and B Channel 130 was used. 2 - DPN DPNSS protocol used. 3 - 1 Length of the message in hexadecimal 4 CCM Call Connect Message. The phone answered. Fourth Line RI130 DPN 2 CRM/CIM ;30;
1 2 3 4
1 RO130 This is a Real Call (R), Outgoing (O) and B Channel 130 was used. 2 - DPN DPNSS protocol used. 3 - 2 Length of the message in hexadecimal 4 CRM/CIM;30; Clear Request Message/Clear Information Message. PABX A has cleared down the call. String 30 indicates a normal clear down (see BTNR 188 Table Of Clearing/Rejection Cause Codes (CRM/CIM) under the column Hex Value. Value 30H (H for Hex) is a normal clear down. Note that for single values in the CCS Trace (e.g. 4) will be shown as 04H.
Page - 8
PABX B
CRM/CIM CRM/CIM
Actual CCS Trace RO130 DPN 2B ISRM_C ;10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400 RI130 DPN 20 NAM *1*1#*50*832400#*100*G.Rodgers# RO130 DPN 2 CRM/CIM ;30; RI130 DPN 2 CRM/CIM ;30; Explanation of trace: The first two lines are the same as the first example showing the calling and called extension. Extension 832400 does not answer so there is no CCM message. Extension 822300 (PABX A) clears down the call followed by B.
822300 calls 832400 who is busy. 822300 sets a callback and hangs up. 832400 then hangs up and the callback matures. 822300 answers and call completes
14:24:04 RO130 DPN 2B ISRM_C ;10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400 14:24:05 RI130 DPN 2 CRM/CIM ;8;
Page - 9
822300 calls 832400 who answers and then transfers the call to 822402 (supervised and then releases). 832402 then clears down.
14:29:19 RO130 DPN 2B ISRM_C ;10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400 14:29:19 RI130 DPN 20 NAM *1*1#*50*832400#*100*G.Rodgers# 14:29:22 RI130 DPN 1 CCM 14:29:24 RI130 DPN 6 EEM_C *60B# 14:29:24 RO130 DPN 5 EEM_C *55# 14:29:30 RI130 DPN B EEM_C *82*T#*61# 14:29:30 RO130 DPN 1E EEM_C *1*1#*50*822300#*100*D.Sykes# 14:29:30 RI130 DPN 1D EEM_C *1*1#*50*832402#*100*J.Kirk# 14:29:33 RI130 DPN 2 CRM/CIM ;30;
822300 calls 832400 who answers and then transfers the call to 822402 (unsupervised, releases before 832402 answers). 832402 then clears down.
14:30:27 RO130 DPN 2B ISRM_C 10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400 14:30:27 RI130 DPN 20 NAM *1*1#*50*832400#*100*G.Rodgers# 14:30:31 RI130 DPN 1 CCM 14:30:33 RI130 DPN 6 EEM_C *60B# 14:30:33 RO130 DPN 5 EEM_C *55# 14:30:37 RI130 DPN B EEM_C *82*T#*61# 14:30:37 RO130 DPN 1E EEM_C *1*1#*50*822300#*100*D.Sykes# 14:30:37 RI130 DPN 21 EEM_C *1*1#*50*832402#*100*J.Kirk#*66# 14:30:41 RI130 DPN 1 CCM 14:30:42 RI130 DPN 2 CRM/CIM ;30;
822300 calls 832400 who answers and then transfers the call to 822402 (unsupervised, releases before 832402 answers). 832402 does not answer, call returns to 832400 who answers and clears down.
14:31:49 RO130 DPN 2B ISRM_C ;10;*1*1#*50*822300#*100*D.Sykes#*19*Z#832400 14:31:50 RI130 DPN 20 NAM *1*1#*50*832400#*100*G.Rodgers# 14:31:54 RI130 DPN 1 CCM 14:31:55 RI130 DPN 6 EEM_C *60B# 14:31:55 RO130 DPN 5 EEM_C *55# 14:31:59 RI130 DPN B EEM_C *82*T#*61# 14:31:59 RO130 DPN 1E EEM_C *1*1#*50*822300#*100*D.Sykes# 14:31:59 RI130 DPN 21 EEM_C *1*1#*50*832402#*100*J.Kirk#*66# 14:32:32 RI130 DPN 5 EEM_C *66# 14:32:34 RI130 DPN 20 CCM *1*1#*50*832400#*100*G.Rodgers# 14:32:38 RI130 DPN 2 CRM/CIM ;30;
System 1 (extension 812300) calls System 3 (extension 832400). The call transits System 2 where this trace is being made. Normal call, extension 832400 answers and clears down.
14:34:01 RI100 DPN 26 ISRM_C ;10;*1#*50*812300#*100*Russ#*19*Z#832400 14:34:01 RO130 DPN 26 ISRM_C ;10;*1#*50*812300#*100*Russ#*19*Y#832400
Page - 10
ISRM(I)
0001
RM(I)
0011
EEM(I) EERM SM
Page - 12
BTNR 188
Supplementary Information String Identifiers
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 Page - 14
Page - 15
Page - 16
Page - 18
Page - 21
Page - 22
Page - 23
Page - 25
IDENTIFIER MNEMONIC SUPPLEMENTARY INFORMATION PARAMETER CODE 226 TCOS STRING NAME TRAVELLING CLASS OF SERVICE (1)ROUTE RESTRICTION CLASS (2)CALL BARRING GROUP (3)FACILITY LIST CODE 227B 228B 229B 230 231 232 233 NOTE 234 235 I-CC I-CPN ISDN-CLEARING CAUSE ISDN-CALLING PARTY /CONNECTED NUMBER TCOS-R DIV-RSC DIV-RCC RDC CAUSE CP I-BC TRAVELLING CLASS OF SERVICE-REQUEST DIVERSION-REMOTE SET COMBINED DIVERSION-REMOTE CANCEL COMBINED REDIRECTION CONTROL CLEARING CAUSE CALL PROCEEDING ISDN-BEARER CAPABILITY TIMER VALUE CLEARING CAUSE NONE BEARER CAPABILITY CAUSE 1) ISDN NUMBER ATTRIBUTES 2) ISDN NUMBER DIGITS 236A 237A 238 I-CSA I-DSA I-HLC ISDN-CALLING PARTY /CONNECTED SUBADDRESS ISDN-DESTINATION (CALLED PARTY) SUBADDRESS ISDN-HIGH LAYER COMPATIBILITY 239 I-LLC ISDN-LOW LAYER ISDN SUBADDRESS ISDN SUBADDRESS HIGH LAYER COMPATIBILITY LOW LAYER C PARTY ADDRESS NONE NONE
6/189-I
Page - 26
Page - 27
BTNR 188
Coding of Supplementary Information String Parameters
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 0 1 2 3 4 Name None Low Medium High Alarm reporting inhibited Description No alarms currently active in the system Some alarms active, but no effect on traffic handling Some alarms active which do have an effect on traffic handling, but the PBX can still function Alarms active in the system are such that the PBX operation is greatly affected No alarm information shall be provided because maintenance personnel on site have inhibited the 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 ADDRESS In general the A Party Address is a digit sequence that represents the address of 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
Page - 31
Page - 32
BUSY SERVICES This Parameter has been renamed "SERVICES". CALL BARRING
Page - 33
Page - 34
The status of the traffic channel is identified by a single IA5 character allocated as follows: 1 Free 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".
Page - 35
This Parameter comprises any combination of the following details coded PARTY DETAILS in IA5 alpha characters as indicated: C = Controller L = Last S = Self If none of these details applies this Parameter may be omitted. CONFERENCE PARTY INDEX This Parameter comprises a decimal number encoded as one or more IA5 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 ADDRESS Page - 36 That digit sequence which, when used as a Destination Address by any PBX in the network, will cause the call to be routed to the third party in a
DEVICE INDEX
Page - 38
would be encoded as: *235*rP*2595# This Parameter comprises a sequence of IA5 characters representing the values of octets 3, onwards of an ISDN Called Party Subaddress, Calling Party Subaddress or Connected Subaddress information element, using 3B4I encoding (see APPENDIX 1 to this Annex). example: The following Calling Party Subaddress information element: Octet 1: Octet 2: Octet 3: Octet 4: Octet 5: Octet 6: ISDN TYPE identifier length 10000000 01010000 01000001 01000010
would be encoded as: *236A*IEAAPI# 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. Page - 39
would be encoded as: *239*bI@aQRBs# MALICIOUS CALL This Parameter is an IA5 numeric character sequence comprising up to 3 digits for identifying a request to trace a malicious call a DPNSS 1 REFERENCE network. This Parameter is optional. It may be omitted if Malicious Call References are not used. NESTING LEVEL 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 represent the level of nesting . This Parameter is optional; omission of the Parameter indicates a nesting level of 1. NIGHT SERVICE 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 ADDRESS point. This Parameter comprises a sequence of IA5 numeric characters each in the range 0 - 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. NUMBER OF Page - 40 This indicates the number of unanswered calls currently waiting on an
More than one Type may be included in the 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). PROGRESS INDICATOR This Parameter comprises a sequence of IA5 characters representing the values of octets 3, onwards of an ISDN Progress indicator information element, using 3B4I encoding (see APPENDIX I to this Annex). example: The following Progress Indicator information element: Octet 1: identifier Octet 2: length Octet 3: 10000010 Octet 4: 10000010 Page - 41
Page - 42
Page - 44
Page - 45
TEST INDEX
TEXT TYPE
Page - 47
Page - 48
Page - 49
BTNR 188
Clearing/Rejection Cause Codes (CRM/CIM)
Signal Not Valid Subscriber Out of Service Signaling System Incompatible Service Temporarily Unavailable Service Unavailable
TRFD UNR
Used when the requested Service is supported by 03H the PBX but not by the called party. This Clearing Cause is accompanied by the String SU which identifies the Service being rejected. Transferred Used (by issues 2 & 3 PBXs only) to instruct the 1DH Branching PBX of a 3-party call to connect the two remaining parties together. DTE Uncontrolled Not Used when the called X.21 terminal is in the 2EH Ready "Uncontrolled Not Ready" state.
All other Clearing Cause values, with the exception of those encountered when interworking with DASS 2, are invalid within DPNSS 1 at present. Reference should be made to BTNR 190 and the individual Service and Supplementary Service Sections of BTNR 189 for Clearing Causes used when interworking with DASS 2. END OF SECTION 4 ANNEX 3
Page - 54