DataKinetics DSC110 User Manual page 59

7.11.2 Clearing Cause Mappings
Clearing cause mapping tables are used to convey clearing causes received on
one side of a call into the appropriate clearing cause for transmission to the far
side.
When a clearing cause (or release reason) is received it is mapped to an Internal
Token using the Receive Clearing Cause Mapping Table. The Internal Token is
then conveyed across the converter and mapped using the Transmit Clearing
Cause Mapping Table into the appropriate clearing cause (or release reason) for
transmission.
In addition when the converter determines that a call should be released, it
generates an Internal Token which is then mapped using the Transmit Clearing
Cause Mapping Table into the appropriate clearing cause for transmission.
Call failure records generated by the converter always use the Internal Token to
identify the reason for call failure.
The clearing cause mapping tables are configured on a per-circuit group basis
using the CC parameter, separate tables can be configured for the received and
for the send side.
The user can select either one of the fixed mapping tables or generate (using the
REMCFG tool) and upload from the remote data centre a customer specific
clearing cause mapping table.
The mapping tables are:-
CC table
0 Transit all values transparently
1 ETSI ISDN cause values.
2 ETSI ISUP version 2 cause values.
3 Q767 ISUP cause values.
4 Australian Interconnect ISUP cause values.
5 ANSI cause values.
6 UK National user part.
7 Blue Book TUP cause values.
8 SSUTR2 cause values.
9 China TUP cause values.
10 DPNSS cause values.
11 - 90 Reserved for future use.
90 - 99 User customised clearing cause tables
uploaded from the remote data centre.
The definition of the values and mappings provided by the fixed mapping tables
are given in ANNEX B.
DataKinetics DSC110 / DSC210 User Manual Issue 12
Description
Page 59