Section 7.8.5. Call Data Recording for Outgoing Connections

7.8.5. Call Data Recording for Outgoing Connections

Call data recording for outgoing connections (trunk and tie traffic) is always configured using Least Cost Routing (LCR) parameters. The VOICE/FAX and DATA services are normally handled in the same way as far as charges are concerned. Because you can configure LCR separately depending on the service, you can also assign another cost parameter to each service.

Configuration commands:

Activate the feature for outgoing trunk calls (including charge display) as follows:
```
CHANGE-FEASU:TYPE=A,CM=CDROGTR&DISCHTR; 
```
Activate the feature for outgoing tie traffic (including charge display) as follows:
```
CHANGE-FEASU:TYPE=A,CM=CDROGNW&DISCHNW;
```

Assign the LCR charge parameters as follows:

CHA-LDAT:LROUTE=<number>[,LSVC=VCE],
LRTEL=<number>,CARRIER=1,ZONE=LONG01,LATTR=WCHREG;

Explanation of important parameters:

CARRIER:	Network operator
ZONE:	Distance zone (EMPTY=no charges); you must configure the ZONE with the AMO TTBL
LATTR:	WCHREG activates call data recording for this routing element (see examples in Section 68.10, "Examples"). NOTRANS deactivates call data recording in all transit nodes in the route; only the charges reported by the CO are sent back to the source node (see example in Section 68.10.1, "Internal Call Data Recording in the Network"). EODSTCDR starts call data recording right after the end of dialing. INTCHARG treats outgoing tie connections as internal connections (see example in Section 68.10.1, "Internal Call Data Recording in the Network") NOCHDISP suppresses the call display in the source node if an "expensive" route is used on the way to the destination node (e.g., overflow into the CO) (see example in "Section 68.10.2, "Tie Traffic with Incoming Charges and Trunk Traffic in Transit"").

Define COT with the DPRE class of service and assign it to the trunk and tie circuits. DPRE causes the prefix digits to be added to the destination number that is sent to call data recording. This setting takes effect when an overflow trunk group is seized via a toll line.
If the network nodes have different ZAND settings for CDDISPEX (unit/charge), you must assign a COT with/without TRSC parameter to the trunk in the transit node (see example in Section 68.10.2, "Tie Traffic with Incoming Charges and Trunk Traffic in Transit").

If TRSC is set, charges are sent on this line in the direction of the source node; these can be displayed there, e.g. without ongoing call data recording. If TRSC is not set, then units are sent. This parameter works only in a connection's transit node.
```
CHA-COT:COTNO=15,COTTYPE=COTADD,PAR=DPRE;

CHA-COT:COTNO=15,COTTYPE=COTADD,PAR=TRSC;   
(only in transit node)

CHA-TDCSU: PEN=<g-uu-bbb-sss>,COTNO=15;
```
Define the class of service (COS) with CDRSTN authorization and assign it to the stations at which the charges should be displayed. Assign the COS to the station with the AMOs ACSU, SCSU, SBCSU; you must also use the AMOs TACSU, TSCSU, TDCSU to assign it to a circuit whose protocol cannot transmit the classmarks.
```
CHA-COSSU:TYPE=COS,COS=5,AVCE=CDRSTN,AFAX=CDRSTN,
ADTE=CDRSTN;
 
CHA-SCSU:STNO=<number>,COS1=5,COS2=5; 
```

Explanation of the following tables.

Table 48: In addition to the charges calculated in the separate node, it is also possible to receive call charge information from the line. Table 48 shows what affect the LCR parameters (AMO LDAT) have in this regard.

Table 49: If charges are received from the line, they are displayed according to this table. The charges were calculated in foreign nodes or they originate with the CO. The influence of activated call data recording is limited to a possible conversion of units into amounts or vice versa.

Table 50: If call data recording is activated and no charges are received from the line, the charges are calculated and displayed according to Table 50.

IMPORTANT:

Calculated charges are not added to charges that were received from the line. Charges from the line are always dominant.

Table 47. Combination of LRTEL parameters and their effect (outgoing connections)

Combination of LRTEL parameters			Effect
ZONE	LATTR =WCHREG	LATTR =NOTRANS	Effect
EMPTY	yes		No calculation of costs using cost parameters, costs are calculated based on call charge information over the line (trunk traffic). Conversion of pulses <-> charges is possible. Charges from the line:
		no	All types (trunk, tie) are possible.
		yes	Only trunk traffic from remote systems is possible.
not EMPTY	yes		Calculation of costs using cost parameters, calculation of costs based on charges via the line are dominant. Charges from the line:
		no	All types (trunk, tie) are possible.
		yes	Only trunk traffic from remote systems is possible.
any	no		No call data recording is activated, charges from the line can be displayed but not converted. Important: Note TRSC in the transit nodes. Charges from the line:
		no	All types (trunk, tie) are possible.
		yes	Only trunk traffic from remote systems is possible.

Table 48. AMO FEASU and AMO COSSU parameter (outgoing connections)

AMO FEASU		AMO COSSU	Meaning (Axxx=authorization for specific service)
CM= DISCHNW	CM= DISCHTR	Axxx = DIDB	Meaning (Axxx=authorization for specific service)
yes	any	yes	Charges displayed on the station display
any	yes	yes	Charges displayed on the station display
any	any	no	No charges whatsoever displayed on the station display
no	no	any	No charges whatsoever displayed on the station display

Table 49. AMO FEASU and AMO COSSU parameter (outgoing connections)

AMO FEASU				AMO COSSU	Meaning (Axxx=authorization for specific service)
CM = CDROGNW	CM= CDROGTR	CM= DISCHNW	CM= DISCHTR	Axxx = DIDB	Meaning (Axxx=authorization for specific service)
yes	yes	yes	yes	yes	Trunk and networking call data is recorded for the station and all charges are displayed.
yes	no	yes	any	yes	Networking call data is recorded for the station and charges are displayed. No trunk charges.
no	yes	any	yes	yes	Trunk call data is recorded for the station and charges are displayed. No networking charges.
yes	yes	no	yes	yes	Trunk and networking call data is recorded for the station, only trunk charges are displayed.
yes	yes	yes	no	yes	Trunk and networking call data is recorded for the station, only networking charges are displayed.
yes	yes	any	any	no	Trunk and networking charge data is recorded for the station, but no charges are displayed.
yes	no	any	any	no	Networking call data is recorded for the station, but not trunk call data; no charges are displayed.
no	yes	any	any	no	Trunk call data is recorded for the station but networking call data is not, and no charges are displayed.
no	no	any	any	any	Call data is not recorded for any station and no charges are displayed.

IMPORTANT:

CDRSTN=no has the same effect as DISCHNW=no and DISCHTR=no and CDRSTN=any.

${DocTitle}, ID: ${DocID}

© 03/2026 Mitel Networks Corporation. All rights reserved. Mitel and the Mitel logo are trademark(s) of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH & Co. KG. All other trademarks herein are the property of their respective owners.