Que “EL PROGRAMA”, considera los siguientes apoyos: a) Proyecto de Organización Productiva

A CDR record typically has one 80-character line (two if Multi-Tenant Service, CLID, or Feature Group D ANI is involved) and an average length of 100 bytes when the OLD CDR format is selected.

When the NEW CDR format is selected, an 86-character first line is output followed by an 85-character second line and a 42-character third line. If the Time to Answer feature is active, a third 13-character line is output.

A Meridian 1 system with CDR can run out of call registers (CRs) for call processing if the SDI interface transmission rate is less than that of the CDR record generation. The SDI baud rate needs to be high enough so that records do not accumulate in the Meridian 1 output buffer, causing a shortage of call registers.

The Average Busy Season Busy Hour (ABSBH) traffic data provides a starting point for calculating the required capacity. The capacity includes a 30% reserve to accommodate traffic peaks.

Table 23 on page 147 and Table 24 on page 148 show the relationship between baud rate and number of CDR calls per hour for two different record lengths: 100 characters (an average record) and 160 characters (the maximum length) respectively. The tables rely on the following calculations:

SDI port baud rate * 0.70 / record length = records that can be transmitted per second

Records transmitted per second * 60 * 60 = CDR hourly call capacity. The tables, which apply to all Meridian 1 CPUs, assume that each call uses one call per record. Table 23 on page 147 shows the worst-case scenario, with each record at the maximum 160-character length. For other record lengths, interpolate between the two tables.

Table 23:

CDR data rate and system call capacity: record length 100 characters

Baud Rate 300 1200 2400 4800 9600

The table data ignores potential system limitations such as real time or traffic constraints that need to be engineered separately. The tables apply to all Meridian 1 CPUs.

Only calls generating CDR records need be included in capacity estimations. For example some systems keep CDR records only for outgoing calls. Calls that do not generate records should be excluded from the capacity

calculations.

Table 24

CDR data rate and system call capacity: record length 160 characters

Baud Rate 300 1200 2400 4800 9600

Page 149 of 274

Call record types

Contents

The following are the topics in this section:

B record (Abandoned call) . . . . . 152 N (Normal) record . . . 152 Feature Interactions/Call Scenarios . . . . . 153 S (Start) record . . . . . 157 Feature Interactions/Call Scenarios . . . . . 157 X record (Transfer) . . . 160 Feature Interactions/Call Scenarios . . . . . 160 E record (End) . . . 161 Feature Interactions/Call Scenarios . . . . . 161 I record (Initialization) . . . . . 162 T record (Time stamp) . .. . . 162 A record (Authorization Code/Scheduled Access Restriction) . . . 162 Feature Interactions/Call Scenarios . . . . . 163 C record (Charge Account) . . . 163 Feature Interactions/Call Scenarios . . . . . 164 M record (Charge Conference) . . . 166 Feature Interactions/Call Scenarios . . . . . 166 P record (Calling Party Number) . . . . . 166 F, R and Q records (ACD call connections) . . . 167 R records and F records . . . . . 168 L record (Internal CDR) . . . . . 168 Packaging requirements . . . 168

Feature Interactions/Call Scenarios . . . 168 G record (Internal Meridian 1 Packet Handler data call) . . . 170 H record (External Meridian 1 Packet Handler data call) . .. . . 170 D record (Station Activity) . . . 171 Packaging requirements . . . 171 Feature Interactions/Call Scenarios . . . 171 Y record (Public Network Feature Invocation) . . . . . 172 Feature Interactions/Call Scenarios . . . 172 Priority Connection Record . . . . . 176 CDR record sequencing . . . . . 176

All calls generate, at a minimum, single call records. Unmodified calls generate a Normal record. Modified calls generate Start, Transfer and End records. Multiple call records may be generated for calls which are impacted by certain features.

Table 25, “Call record types,” on page 151 presents a comprehensive list of call record types and the page on which they are described in detail. Each record type is described as it relates to packages, features and call scenarios. Record fields are discussed in the next chapter, starting on page 179.

After each record type is described, Priority connection records and CDR record sequencing are discussed. This chapter concludes with a description of the Enhanced Malicious Call Trace feature as it relates to CDR.

Table 25

Call record types

Record Description Page

A Authorization Code 162

B Abandoned Call 152

C Charge 163

D Station Activity 171

E End 161

F Connection (for ACD calls which are conferenced) 167 G Internal Meridian 1 Packet Handler data call 170 H External Meridian 1 Packet Handler data call 170

I Initialization 162

L Internal Call 168

M Charge for Conference 166

N Normal 152

P Calling Party Number 166

Q Connection (for calls connecting a trunk and an ACD Agent) 167 R Connection (for ACD calls which are transferred) 167

S Start 157

T Time stamp 162

X Transfer 160

B record (Abandoned call)

B records (Abandoned call) are output when the Time to Answer feature is active and New Format CDR is selected for CDR TTY output

(FCDR = NEW in LD 17). B records are only output to CDR Teletype devices.

B records are output when:

• an unanswered incoming trunk disconnects and ABAN = YES in LD 16 • Internal CDR is equipped and an unanswered internal station disconnects

from another internal station which has ABDA class of service

With the feature CDR on Busy Tone, a B record is produced when the originator of an incoming or internal call disconnects after receiving a busy tone. The CDR on Busy Tone B record information is displayed on the third line of the CDR B record when the New CDR format (FCDR) is configured.

N (Normal) record

An N record (Normal record) is generated when a simple call is established, whether or not it is extended through the Attendant Console, and when no other telephone feature is activated.

For a Normal record, all telephone set dial pad input is included in the CDR record until such time as the End-of-Dialing (EOD) timer interval is exceeded or the user enters # from the set dial pad. Thus, the dialed DN portion of the CDR record may include * symbols and unused digits. For example, speed call and autodial numbers often include * symbols. Each * symbol causes a software defined pause to occur when the symbol is interpreted by the system.

End-to-End Signaling (EES) digits are dialed after the timer expires, after the octothorpe (#) has been pressed, or after answer supervision is received. EES digits often include sensitive information such as authorization codes and account numbers. These digits appear in the CDR only if the customer chooses to include them. Administrators choose to include these digits in CDR by setting ECDR to YES in the Customer Data Block (LD 15). The default is NO.

A user may enter additional digits prior to the system receiving an EOD time-out or user-initiated # entry. In such cases, the call is completed to the correct destination but the CDR record contains the extra digits.