Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1227 Call Coverage 
20
nClass of Restriction and Controlled Restrictions
Users who normally may be restricted from receiving calls still can receive 
calls directed to them via Call Coverage.
nConference
The switch blocks users from conferencing another party onto a call which 
has routed off-net while that call is undergoing call classification. If any 
party on the call is on hold, the call routes off-net, but without undergoing 
call classification, even when the Coverage of Calls Redirected Off-Net 
field is 
y.
A call that covers to a VDN cannot be added to a conference while the call 
is in vector processing. For example, say user A calls user B. B wants to 
have a three-way conference call and calls C. C doesn’t answer, the call 
covers to a VDN, and from there enters a vector. Until vector processing 
has completed this call to some destination, the conference cannot be 
established.
nDirect Department Calling, Uniform Call Distribution, and Automatic Call 
Distribution
If a user has an Auxiliary Work button, and activates or deactivates Send 
All Calls, the Auxiliary Work function associated with DDC or UCD is 
activated or deactivated simultaneously.
If a user has no Auxiliary Work button, activating or deactivating Send All 
Calls still makes the user unavailable or available, respectively, for DDC 
and UCD calls, but Auxiliary Work is not activated or deactivated. The 
Auxiliary Work mode may be activated or deactivated using a feature 
access code.
Activating or deactivating the Auxiliary Work function does not activate or 
deactivate Send All Calls.
nDirect Outward Dialing (DOD)
Coverage of Calls Redirected Off-Net competes with DOD for call 
classifier ports when DOD uses Multi-Frequency Compelled (MFC) 
signaling. The Call Classifier - Detector port provides the MFC tones. 
Non-MFC DOD calls do not need the Call Classifier - Detector port for this 
purpose.
nGlobal Call Classification
To classify tones in countries not using the USA tone plan, time cadences 
and frequencies must be administered so they can be downloaded to the 
call classification circuit packs. You need a Call Classifier - Detector or 
Tone Clock with Call Classifier - Tone Detector circuit pack. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1228 Call Coverage 
20
nHold
If a covering user puts a call on hold, and the principal picks up on the call, 
the coverage appearance may or may not be dropped, depending on 
administration.
If any party is on hold when a coverage call routes off-net, that call does 
not undergo call classification, even when the Coverage of Calls 
Redirected Off-Net field is 
y.
nInternal Automatic Answer
If an internal call is redirected to another phone by a Call Coverage 
redirection criteria, then that call is eligible for IAA at that phone.
IAA does not apply to calls to the original called extension when:
— The called phone has activated Do Not Disturb, Send All Calls, or 
Cover All Calls
— The calling phone has selected Go To Cover before placing the call
Calls directed to a Coverage Answering Group are not eligible for IAA.
nISDN End-to-End Calls
When ISDN facilities carry an off-net coverage call entirely (end-to-end), 
call classification is accomplished through the ISDN protocol rather than 
by a call classifier port.
nLeave Word Calling
Call Coverage can be used with or without LWC. However, the two 
features complement each other. When a covering user activates LWC 
during a coverage call, a message is left for the principal to call the 
covering user. When a covering user activates Coverage Callback during a 
coverage call, a message is left for the principal to call the internal caller.
nNight Service
Calls routed to the night station via Night Service follow the coverage path 
of the night extension under all coverage criteria except Send All Calls.
nPrivacy — Manual Exclusion
When the primary or principal user bridges onto a call that went to 
coverage and has been answered at the coverage point, the user is not 
dropped when Privacy — Manual Exclusion is activated.
nR2-MFC Signaling
Coverage of Calls Redirected Off-Net competes with the R2-MFC 
Signaling feature for Call Classifier - Detector ports. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1229 Call Coverage 
20
nSimulated Bridged Appearance
Calls redirected to coverage maintain an appearance on the called phone if 
a call appearance is available to handle the call. The called party can bridge 
onto the call at any time. The system can be administered to allow a 
simulated bridged appearance of the call to either remain at or be removed 
from the covering phone after the principal bridges onto the call.
A simulated bridged appearance is maintained for calls covered by an 
off-net coverage point if the Coverage of Calls Redirected Off-Net feature 
is enabled. A simulated bridged appearance cannot be maintained for calls 
if the coverage point is linked to AUDIX.
Consult calls use the simulated bridged appearance maintained on the call. 
At the conclusion of a consult call, the bridged appearance is no longer 
maintained. If the principal chooses not to talk with the calling party, the 
principal cannot bridge onto the call later.
If a call that has, or has had, a simulated bridged appearance is conferenced 
or transferred, and redirects to coverage again, a simulated bridged 
appearance is not maintained at the conferenced-to or transferred-to 
extension.
nTenant Partitioning
The caller and called party must be able to access a coverage point. The 
caller is considered to be the covering user and the called party is 
considered to be the covered user. Both parties must be able to access the 
coverage point.
nTransfer
The switch blocks a user from transferring a call which has routed off-net 
to another party while that call is undergoing call classification. If any 
party on a call that has routed off-net is on hold, the call does route off-net 
without undergoing call classification, even when the Coverage of Calls 
Redirected Off-Net field is 
y.
Transfer s with Call Coverage as listed in the following table.
Source Transfer initiator Destination Coverage type
External Local station 
Local station 
Remote station 
Remote station 
Attendant
AttendantLocal station 
Remote station 
Local station 
Remote station 
Local station 
Remote stationExternal
External 
Internal
Internal 
External
External 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1230 Call Coverage 
20
NOTE:
The coverage criteria for transferred DID calls depends upon the 
External Treatment For Transferred Incoming Calls field on the 
Feature-Related System Parameters
 screen.
Related topics
Refer to ‘‘
Coverage Answer Group’’ on page 563 for information about and field 
descriptions on the Coverage Answer Group screen.
Refer to ‘‘
Coverage Path’’ on page 565 for information about and field 
descriptions on the Coverage Path screen.
Refer to ‘‘
Feature Access Code’’ on page 633 for information on activating or 
deactivating sending calls to coverage.
Refer to ‘‘
System Parameters Call Coverage / Call Forwarding’’ on page 923 for 
information on setting the system-wide parameters for call coverage and call 
forwarding.
Refer to ‘‘
Hunt Group’’ on page 708 for information on sending calls to a hunt 
group extension.
Refer to ‘‘
Remote Call Coverage Table’’ on page 875 for information about and 
field descriptions on the Remote Call Coverage Table screen.
Refer to ‘‘
Station’’ on page 894 for information on assigning feature buttons.
Refer to ‘‘
Terminating Extension Group’’ on page 971 for information on 
assigning a coverage path to a Terminating Extension Group.
Refer to ‘‘
Time of Day Coverage Table’’ on page 974 for information about and 
field descriptions on the Time of Day Coverage Table screen.
Refer to ‘‘
Trunk Group’’ on page 980 for information on specifying internal 
ringing and coverage for incoming calls.Internal Local station 
Local station 
Remote station 
Remote station 
Attendant
AttendantLocal station 
Remote station 
Local station 
Remote station 
Local station 
Remote stationInternal
Internal
Internal
Internal 
External
External
Source Transfer initiator Destination Coverage type 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1231 Call Detail Recording 
20
Refer to ‘‘Setting up basic call coverage’’ on page 129 for instructions on 
administering basic call coverage.
Refer to ‘‘
Setting up advanced call coverage’’ on page 133 for instructions on 
administering advanced call coverage.
Call Detail Recording
CDR tracks call information on a per-trunk-group or station-to-station basis. For 
every trunk group (including auxiliary trunks) that you administer for CDR 
reports, the system keeps track of incoming, outgoing and tandem calls. You can 
also receive reports on temporary signaling connections (TSCs) that involve 
trunks, and calls made using loudspeaker paging or code calling access.
Detailed description
You can also ask the system to report on ineffective call attempts. This may 
greatly increase the number of calls recorded, but may also help you to increase 
security, since the system records call attempts that are blocked because of 
insufficient calling privileges. This can also let you know if your users are not able 
to make calls because all trunks are busy.
Some call accounting systems do not support all of the information offered by 
CDR. See your Lucent Technologies representative for details.
Account Code Dialing
Account Code Dialing allows certain calls to be associated with a particular 
project or account number. To do this, users enter account codes when they place 
certain types of outgoing calls. These account codes then appear on the call 
record, which you can use for accounting or billing purposes. Account code 
dialing can be optional or mandatory (forced).
To associate an account code with a particular call, a user first dials the CDR 
account code access code that you have established, then dials the desired account 
code. Next, the user dials the desired trunk access code, or ARS access code, 
followed by the phone number.
The call record contains the account code, TAC or ARS access code, and the 
phone number. It does not contain the account code FAC. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1232 Call Detail Recording 
20
Forced Entry of Account Codes
You can force your users to enter account codes on a system-wide, per-trunk or 
per-user basis, or on the basis of the digit string the user dials. If you have this 
feature in place, the system rejects any call that requires an account code where 
one is not supplied. To maximize system security, it is recommended that you use 
Forced Entry of Account Codes (FEAC).
!SECURITY ALERT:
DEFINITY ECS does not verify account codes. As long as the user enters a 
digit string of the appropriate length, the system allows the call. You must 
use Authorization Codes if you want the system to determine if the user is 
authorized to make the call.
You can assign FEAC in the following ways:
nAll calls marked for FEAC on the Toll Analysis table
If you activate this CDR system parameter, all users must dial an account 
code when the digits dialed match a digit string with FEAC=y. This 
includes calls made by ARS or TAC.
nToll calls made by users with a specific class of restriction (COR)
If FEAC is assigned to a specific COR, any telephone user assigned that 
COR must dial an account code before making calls that are administered 
forced entry of account codes.
nAll calls made over a trunk group with FEAC in COR (TAC calls)
Users cannot access a trunk group that is assigned a COR with FEAC until 
they dial an account code. If a call is routed via ARS, the system does not 
check for FEAC in the trunk group’s COR. Therefore, if you want your 
users to enter account codes for ARS calls, you must administer this in the 
Toll Analysis table.
If an account code is required for a call and the user does not enter one, the system 
responds with intercept tone.
The following types of calls never require an account code:
nAttendant originated call
nBusy verification of a trunk by an attendant or telephone user
nDCS (unless required by the trunk group’s COR)
nPersonal CO Line
nRemote access without barrier codes
nTrunk-to-trunk connections 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1233 Call Detail Recording 
20
Call Splitting
Call splitting keeps track of calls where more than two parties are involved. These 
can be calls that are transferred, conferenced, or where an attendant becomes 
involved. If you have call splitting activated and any of these situations arise, 
CDR produces a separate record for each new party on the call.
You can administer call splitting for both incoming and outgoing trunks, and both 
can have attendant calls recorded separately.
Incoming trunk call splitting
If incoming trunk call splitting is enabled, CDR starts a new record whenever an 
incoming trunk call is conferenced or transferred. Whenever a user drops from the 
call or the call is successfully transferred, CDR produces a record relevant to this 
user’s participation. These call records show the amount of time each party was on 
the call, the incoming trunk access code, the dialed number and the condition 
code, as well as the other fields specified in the record format.
For incoming trunk calls that are conferenced, CDR creates a new record 
whenever a new party comes on the call. The duration field in these records shows 
how long each party participated on the call. Conference calls produce records 
with duration fields that overlap. The duration of a transferred call begins when 
the transferring party presses the 
TRANSFER button for the second time, so there is 
no overlap.
If ITCS is enabled and an incoming trunk call is conferenced or transferred to a 
local extension that is optioned for Intraswitch CDR, the call produces an 
incoming trunk call record. It does not produce an Intraswitch record.
To enable this option, set the Incoming Call Splitting field to 
y on the CDR 
System Parameters screen, and make sure that Record Outgoing Calls Only = n.
ITCS examples
The following scenarios depict calls made with ITCS active. The tables that 
follow do not show all fields, only those that may change due to call splitting. Call 
durations are approximate.
Caller A (TAC 123) makes an incoming trunk call to switch party B (5657890). 
They talk for 2 minutes. B then conferences in C (ext. 54321), and D (ext. 59876). 
The entire group talks for another 8 minutes, at which point B drops off the call. 
This produces a record for segment A–B. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1234 Call Detail Recording 
20
A, C and D continue to talk for another 5 minutes. All remaining parties drop, 
producing two more records; A–C and A–D. Note that each record shows the 
incoming trunk ID as the calling number.
A (TAC 123) calls Station B (5657890). They talk for 1 minute, then B transfers 
the call to C (54321). CDR generates a record for segment A–B. A and C talk for 
5 minutes. CDR generates a record for segment A–C. 
A (TAC 123) calls switch party B (5657890), they talk for one minute. B transfers 
the call to public-network party C (5665555), they talk for 4 minutes. Note that 
the duration of the original incoming trunk call includes the time after the call was 
transferred to an outgoing trunk, until all trunk parties drop. 
Outgoing trunk call splitting
If outgoing trunk call splitting is active, CDR creates records of transferred 
outgoing calls as described above for incoming trunk call splitting. For 
conferenced calls, the originator of the conference will be charged until he or she 
drops from the call, at which point CDR begins a second record for the 
conferenced user. Records for parties on a conference do not overlap; they are 
split. To enable this option, set the Outgoing Call Splitting field to 
y on the CDR 
System Parameters screen.
Table 17. ITCS conference
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
A–B 0:10:0 C 123 5657890
A–C 0:13:0 C 123 54321
A–D 0:13:0 C 123 59876
Table 18. ITCS transfer
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
A–B 0:01:0 9 123 5657890
A–C 0:05:0 9 123 54321
Table 19. ITCS transfer to outgoing trunk
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
A–B 0:05:0 9 123 5657890
A–C 0:04:0 9 345 123 5665555 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1235 Call Detail Recording 
20
OTCS examples
In the next example, switch party A (57890) calls B(7771234), talks for 5 
minutes, then conferences in C (7775678). They all talk for another 5 minutes, at 
which point all parties drop.
Switch party A (51234) calls public-network party B (5659999). They talk for 5 
minutes. A then transfers the call to switch party C (54444). 
Attendant call recording
Both incoming and outgoing call splitting give you the option of recording the 
attendant portion of calls that are transferred. To enable this option, set the 
Incoming and/or Outgoing Attendant Call Record field to 
y.
If either incoming or outgoing trunk call splitting is enabled, the attendant portion 
of a conference call always produces a separate record.
Attendant call recording examples
Public-network party A (TAC 123) calls the attendant (Attd), and asks to be 
transferred to switch party B (58888). 
Table 20. OTCS conference
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
A–B 0:10:0 C 345 57890 7771234
A–C 0:05:0 C 345 57890 7775678
Table 21. OTCS transfer
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
A–B 0:01:0 A 345 51234 5659999
C–B 0:05:0 A 345 54444 5659999
Table 22. Attendant transfer incoming trunk
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
A–Attd 0:01:0 9 123 Attd
A–B 0:05:0 9 123 58888 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1236 Call Detail Recording 
20
The attendant (Attd) dials switch party A (59999), then transfers the call to 
public-network party B (4445678).
Intraswitch CDR
Intraswitch CDR generates call records for calls to and from users on the local 
switch. For the system to generate an intraswitch CDR record, one of the 
extensions involved in a call must have intraswitch CDR assigned.
If a station is optioned for Intraswitch CDR, and ITCS is also enabled, ITCS 
overrides Intraswitch CDR. That is, incoming trunk calls involving the station 
produce trunk call records, not Intraswitch CDR records.
The output for intraswitch CDR follows the same format you have established for 
other call records. Certain fields do not appear on intraswitch call records, because 
they do not pertain to internal calls. For example, an intraswitch record does not 
contain trunk access codes or circuit IDs, since these do not apply. 
Some calls may seem to be intraswitch CDR calls, but actually result in trunk 
calls. For example, a station-to-station call to an extension that is forwarded to an 
outgoing trunk produces only a trunk CDR record, regardless of whether or not 
either station has intraswitch CDR assigned. 
You can assign intraswitch CDR to terminating extension groups (TEGs), stations, 
data modules, VDNs, PRI endpoints, access endpoints, or hunt groups. The 
number that appears in the dialed number field depends on whether you have 
administered CDR System Parameters to record hunt group/member or VDN 
information. You cannot assign intraswitch CDR to attendant consoles or 
CallVisor ASAI stations. 
NOTE:
If an extension with intraswitch CDR is neither the originator of the call nor 
the dialed number of the call, the system does not produce a call record, 
even though the extension might be a party on the call (via Call Pickup, Call 
Forwarding, etc.).
Table 23. Attendant transfer outgoing trunk
Segment DurationCondition 
CodeAccess 
Code UsedCalling 
Number Dialed 
Number
Attd–B 0:01:0 A 345 Attd 4445678
A–B 0:05:0 A 345 59999 4445678