Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1277 Call Detail Recording 20 nTime This fields contains the time that the call ended, or the time that a user dropped from a multi-party call, if Call Splitting is active. nVDN (vdn) — 5 digits This field is only available on customized records. The call record contains the VDN extension number. If VDN Return Destination is active, this field contains the first VDN the caller accessed. Security Monitor call detail records daily for unusual calling patterns, long calls, international calls, calls outside of normal business hours, and other indications of toll fraud. Call accounting systems are available that automatically monitor CDR output for fraudulent calling patterns. Considerations nDate and Time If a time of day is not administered in the system, DEFINITY ECS does not generate CDR records. If the time is changed while a call is in progress, the actual duration for that call is not reflected in the CDR record. Instead, a special sequence of 9999 is recorded in the CDR record to indicate that the call was in progress during a time change. Interactions nAbbreviated Dialing When a user places a call using Abbreviated Dialing or a Facility Busy Indicator button, all outpulsed digits appear on the record. nAnswer Detection The DEFINITY ECS provides Answer Detection using a Call Classifier circuit pack. This feature is an option for your system and requires an 8-port call classifier circuit pack. CDR starts recording call duration at the time the answer is detected by the circuit pack. nAttendant Console If an attendant-assisted call involves an outgoing trunk, the primary extension of the user who requests attendant service is recorded as the calling number, even if the attendant dialed the outside number. Condition Code 1 indicates the call was assisted by the attendant.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1278 Call Detail Recording 20 If the attendant allows through dialing, the primary extension of the user who dialed the number is recorded as the calling party. Condition Code 1 indicates that a trunk access code was extended by the attendant. Condition Code 7 indicates that a feature access code was extended by the attendant. If Incoming or Outgoing Attendant Call Record is enabled, the system produces a separate record for the attendant portion of incoming or outgoing calls that are transferred. On attendant-assisted calls that require an account code, the account code must be entered before the trunk access code. If the attendant is redirecting an incoming call to an extension, the attendant may dial an account code before dialing the extension number. It is not possible to option the attendant for intraswitch calls. Intraswitch records are produced for an intraswitch-optioned extension calling the attendant or for a call from the attendant to an intraswitch-optioned extension. In the case of an attendant-assisted call involving an intraswitch extension, the calling number recorded is the extension of the party who called the attendant, and the dialed number recorded is the extension that the attendant extended the call to. The record has a Condition Code 0. nAUDIX For remote AUDIX over DCS, if station A on node 1 forwards its calls to AUDIX on node 2, each switch produces a call record. The record from node 1 contains A as the dialed number. The record from node 2 contains AUDIX as the dialed number. If the calling number is on a different switch within the DCS network, or the call comes in over ISDN, the actual calling number is recorded in the Calling Number field, and the TAC of the trunk bringing the call into the local switch is recorded in the Incoming Trunk Access Code field of 24-word records. If the forwarded call is an incoming call, then, as in all cases (other than vectoring) in which an incoming call is forwarded, transferred, or conferenced using an outgoing trunk, two separate CDR records are produced, one for incoming and one for outgoing trunk usage. The outgoing trunk usage record lists AUDIX as the Calling Number. nAUDIX - Transfer out of If Incoming Trunk Call Splitting is enabled, and Transfer out of AUDIX is used, CDR generates two records. The first contains the AUDIX, the second contains the transferred-to party.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1279 Call Detail Recording 20 nAuthorization Codes Authorization codes are recorded on CDR records provided account codes do not exceed 5 digits for non-ISDN and ISDN LSU formats, or 4 digits for Enhanced LSU formats. On the 59-character CDR International Processing and International Direct records, the authorization code is never recorded. When account codes are dialed, for the non-ISDN and the ISDN LSU formats, authorization codes are recorded on CDR printouts if the account code length does not exceed 6 digits. For Enhanced LSU, the account code length must not exceed 6 digits. nAutomatic Selection of DID Numbers Incoming calls, if recorded at all, are recorded for the DID extension number, not the room extension number. nAAR and ARS CDR records contain the following information for Automatic Route Selection (ARS): — Fact that an ARS call was made — Calling extension number — FRL of the calling extension — Called number — TAC of trunk group used for the ARS call — Time of call completion — Call duration (how long the parties talked) — IXC code, if any If CDR is suppressed for the trunk group actually used on an ARS call, a CDR record is not generated; otherwise, Condition Code 7 applies. The ARS access code is recorded in the Access Code Dialed field and the trunk access code for the trunk group actually used is recorded in the Access Code Used field. If an AAR call is placed to a busy trunk group and CDR is suppressed for that trunk group, the user hears reorder tone and the CDR output shows an ineffective call attempt. If an ARS call is an attendant-assisted call, the CDR record shows the call with a Condition Code of 7 (ARS call) instead of a Condition Code of 1 (attendant-assisted call). This occurs because CDR is not notified until after the trunk is seized and, in this case, the trunk is not seized until the user dials the number. For FEAC, if a trunk group is accessed via ARS, the trunk group’s COR is not used to determine if an account code needs to be entered.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1280 Call Detail Recording 20 nAutomatic Callback When the Automatic Callback feature is used for an intraswitch call, no CDR record is generated for the first call attempt or the ringback. However, if the caller or extension being called is optioned for intraswitch CDR, a record of the actual call is output provided the call is answered and completed. nAutomatic Circuit Assurance ACA calls generate intraswitch CDR if the terminating extension is monitored by CDR. The originating extension for ACA calls cannot be administered for intraswitch monitoring. nAutomatic Wakeup No CDR intraswitch records are generated for wakeup calls. nBridged Call Appearance CDR does not record any information on the party who bridges onto a call. Instead, the number that was called appears in the Dialed Number field of the CDR record. The duration of the call is recorded when the last party drops off the call. This also applies for intraswitch calls. If the user originates a call over a bridged appearance, the call record contains the calling number of the bridged appearance extension and not the extension number of the original, calling station. nBusy Verification of Terminals and Trunks An attendant or user is never required to enter an account code when making a busy verification. nCall-by-Call Service Selection When a successful call is made on a Call-by-Call Service Selection trunk, the network specific facility used on the call is translated into an INS number and recorded in the INS field of the call record. If a Call-by-Call Service Selection call is unsuccessful because of an administered trunk usage allocation plan, the INS number is recorded in the INS field of the report with a condition code of “E.” nCall Coverage When an incoming or intraswitch call is answered by a covering extension, the extension number dialed by the originating party is recorded as the dialed number. If a call is covered to an off-net location, the dialed number is the number of the off-net location, the calling number is the number of the station that is covered to the remote location.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1281 Call Detail Recording 20 nCall Forwarding All Calls When a call is forwarded to another extension, the extension number dialed by the calling party is recorded as the dialed number. If a call is forwarded to an off-net location, the dialed number is the number of the off-net location, the calling number is the number of the station that is forwarded to the remote location. CDR generates one record for a forwarded intraswitch call. In this record, the dialed number is the same as the extension dialed by the originating party. For a trunk call to a station that is forwarded to a trunk, CDR generates two records. The first record shows an incoming trunk call to the station. The second record shows an outgoing trunk call from the station. For FEAC, calls cannot be forwarded to a destination where a user is required to enter an account code. nCall Park When a user parks an incoming or intraswitch call, that user’s extension is recorded as the dialed number in the CDR record. Call duration in CDR reflects the entire time the incoming trunk is busy (incoming) or until the call ends (intraswitch). nCall Pickup When an incoming or intraswitch call is answered by another user in the pickup group, the extension number dialed by the calling party is recorded as the dialed number. nCall Vectoring The CDR System Parameters form can be administered so that the VDN extension is used in place of the Hunt Group or Member extension. If administered to do so, this overrides the Calls to Hunt Group - Record option of CDR for incoming Call Vectoring calls. Outgoing vector calls generate ordinary outgoing CDR records with the originating extension as the calling number. For incoming calls to a VDN, the duration of the call is recorded from the time answer supervision is returned. — If answer supervision is returned by the vector (via an announcement, collect, disconnect, or wait with music command), and the call never goes to another extension, the VDN extension is recorded as the called number in the CDR record. — If the call terminates to a hunt group, the VDN, hunt group, or agent extension is recorded as the called number as per the administration discussed above.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1282 Call Detail Recording 20 — If the call terminates to a trunk, CDR generates the following two records: nAn incoming record with the incoming TAC as the dialed number. nAn outgoing record with the incoming TAC as the calling number and the digits dialed through the vector step as the dialed number. If “member extensions” is administered on the CDR System Parameters form and the call successfully completes to a station via the “route-to” command, the call record shows an incoming call to that station. Call Vectoring “route to” commands that are unsuccessful do not generate ineffective call attempt records. If a vector interacts with an extension or group that has Call Forwarding All Calls active, normal Call Forwarding/CDR interactions apply. Some calls may originally look like intraswitch calls, but result in trunk calls (for example, a call from a station administered for intraswitch CDR to a VDN, which ends up an outgoing call on an outgoing trunk). Such calls will not generate intraswitch CDR records; the CDR record will have a condition code A - outgoing. nCall Waiting Termination Call duration timing starts when the user answers an incoming call. nCentralized Attendant Services If a CAS attendant extends a call for a user, and CDR is not assigned to the RLT trunk group, the user’s extension is recorded as the originator of the call. If the RLT trunk group does have CDR administered, the RLT trunk is recorded. If a CAS attendant answers a call but does not extend the call, no CDR records are made. nCO Trunks All incoming and outgoing calls on a CO trunk group are recorded, if CDR is assigned to the trunk group and CDR is administered to record incoming calls. nConference For the purpose of CDR, a call is considered a conference call if it contains at least one trunk that is eligible for CDR plus two or more parties, or if it contains at least one party optioned for intraswitch CDR. Condition Code C applies to each CDR record made for a conference call.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1283 Call Detail Recording 20 For a conference call, a separate CDR record is produced for each outgoing/incoming trunk serving the conference call. If ITCS or OTCS is enabled, CDR produces a separate record for each internal party on the call as well. For the outgoing portion of a conference call involving multiple extensions, the extension that requested outside dial tone to bring an outside party into the conference is recorded as the calling party. For the outgoing/incoming portion of a conference call, the call duration in CDR reflects the entire time the trunk is on the conference call. A separate CDR record is produced for each trunk used in a trunk-to-trunk transfer. If ITCS is active, the incoming trunk record shows the duration of the entire call. If the originator of the conference call is optioned for intraswitch CDR, each time the originator dials a non-trunk party, a new CDR record is started. For example, Station A is optioned for intraswitch CDR and calls Station B. Station A conferences in Station C. Station A drops from the call. Station B or C drops from the call. Two CDR records are output with Condition Code C: one for the A to B call and one for the A to C call. If the originator is not optioned for intraswitch CDR, but one or more parties brought into the conference are, one record with Condition Code C is generated for each dialed intraswitch party. For example, Station A calls Station B, which is optioned for intraswitch CDR. Station A conferences Station C. Station A drops from the call. Station B or C drops from the call. One CDR record is output with condition code C for the A to B call. Intraswitch conference call CDR records are output when both the calling number (originator) and dialed number (terminator) of the call drop. The duration of the call will be from the time the terminator answers until both the originator and terminator drop from the call. If the attendant originates the conference, only the dialed numbers corresponding to intraswitch optioned extensions stimulate the creation of CDR records. nDCS Station information is not passed throughout the DCS network for CDR purposes. nDID trunks All incoming calls on the DID trunk group will be recorded if administered to record incoming CDR and if CDR is administered for this trunk group. nEmergency Access to the Attendant CDR does not generate intraswitch records for Emergency Access calls.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1284 Call Detail Recording 20 nExpert Agent Selection A logical extension can be assigned to an agent who can log into a phone using that extension number. On the CDR System Parameters screen, you can chose to record the agent’s logical extension as the called number rather than the hunt-group extension or hunt-group-member extension. nFX Trunks All calls made on an FX trunk group are recorded if administered to record CDR and if CDR is administered for this trunk group. nHotline Service The stored number used on an outgoing or intraswitch Hotline call is recorded by CDR the same as if it was manually dialed. nHunt Groups Either the hunt group extension number or individual hunt group member extension number is recorded as the called number. This is administrable on the CDR System Parameters form. nIntercept Treatment If an outgoing or tandem call is routed to Intercept Treatment, the number dialed by the calling party is recorded as the dialed number, and Condition Code F is recorded. nInter-PBX Attendant Calls If a user calls an Inter-PBX attendant and the trunk group used has CDR assigned, call records contain the following information: — Condition Code — A — Access Code Dialed — Blank — Access Code Used — Trunk access code of trunk used — Dialed Digits — Inter-PBX attendant access code nISDN When true answer supervision is received from the network, an indication is sent to the CDR device to this effect. If an ISDN call has been interworked, the call record shows this, and answer supervision may or may not be accurate. If you use unformatted or expanded record formats, the SID/ANI appears in the record, if sent. nLast Number Dialed The CDR access code and account code dialed are stored as part of the Last Number Dialed. However, some digits may be lost due to the limit on the number of digits stored for this feature.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1285 Call Detail Recording 20 nManual Originating Line Service If an attendant establishes an outgoing call for a user, designated as a Manual Originating Line, the CDR record for the call is the same as for any attendant-assisted outgoing call. The calling extension is recorded as the calling number, and Condition Code 1 applies. nMultiple LDNs If incoming call information is recorded, the called number recorded for LDN calls is the extension number or trunk group access code to which the attendant completes the call. If the call terminates at the attendant console only, the dialed number is the attendant extension. The attendant extension number is administrable (the default is 0). LDNs cannot be administered for intraswitch CDR. However, a call from an intraswitch optioned extension to a LDN produces an intraswitch CDR. nNight Service The extension number assigned to the attendants is recorded as the dialed number. The attendant extension number is administrable (the default is 0). nOff-Premises Station CDR data is recorded if the extension is involved in an outgoing/incoming trunk call or it (or the other terminal involved in the call) is optioned for intraswitch CDR. nPCOL trunks An outgoing PCOL call shows the dialed number in the Dialed Number field of the CDR record rather than a TAC. An outgoing PCOL call is recorded as a call from the originating extension number via the trunk group associated with the PCOL. On incoming PCOL calls the answering extension’s primary extension is recorded as the called number if incoming calls are recorded. nPlanned Interchange When a planned interchange occurs (either demand or scheduled), it is possible for the CDR records on calls ending within 10–20 seconds after the interchange to report as “invalid long duration calls” (duration of 9:59:9 and Condition Code other than 4). This is caused by deviations in the clocks between the two processors and the short duration of the calls. Consider these records invalid. nPrivate Network Access Private Network Access calls are recorded if CDR is assigned for incoming or outgoing tie trunks.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1286 Call Detail Recording 20 nRemote Access Remote Access calls are recorded if Remote Access is provided on a per trunk group basis (incoming destination is the remote access number), and those trunks are administered for CDR. The call record gives no indication that this is a remote access call, other than the trunk group access code. nRingback Queuing Condition Code 8 is recorded for an outgoing call which is queued for a trunk before completion. The length of time the call is queued is not recorded. When an outgoing call is queued for a trunk and is unsuccessful (the queue times out or the calling party does not answer the callback) a CDR record is not generated for the call. nSecurity Violation Notification SVN calls generate intraswitch CDR if the terminating extension is monitored. You cannot administer the originating extension for intraswitch monitoring. nService Observing No CDR records are generated for Service Observing calls. Tandem Tie-Trunk Switching The calling party on an incoming trunk can dial the CDR account code. The Calling Number field in CDR is the trunk access code for the incoming trunk group, the called number is the number dialed. nTemporary Bridged Appearance A CDR record is not affected by any second or subsequent use bridging a call. nTemporary Signaling Connections Cal-associated TSCs and TSC requests appear in the call record, provided the switch is administered to use ISDN layouts. Non-call-associated TSCs and TSC requests generate separate CDR records if the switch is administered to record them. In either case, the TSC Flag and Packet Count fields of the call record contain TSC data. nTie Trunk Access Tie-trunk calls are recorded if CDR is administered to record the trunk group and to record incoming calls.