Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1437 Multiappearance Preselection and Preference 
20
Preference dictates whether a user connects to the ringing call appearance 
or to an idle call appearance. If there is no call, users automatically connect 
to an idle call appearance when they lift the handset, regardless of which 
Preference option is assigned.
Considerations
nMultiappearance telephones can have from 2 to 10 call appearances. One of 
these call appearances is reserved for placing calls or for receiving a 
Priority Calling call. If a telephone has 2 call appearances and one of them 
is active, a nonpriority call cannot access the other call appearance, even if 
the call appearance is idle. The default number of call appearances is 3.
nThe reserved call appearance is not a fixed-position button; it is just the 
last-idle call appearance. For example, if a telephone has 10 call 
appearances, any 9 can be in use, but the tenth (last) is reserved.
Interactions
nAutomatic Incoming Call Display
Incoming calls are not displayed if Idle Appearance Preference is activated.
nCall Coverage
If you administer Cover All Calls as the redirection criterion for a 
telephone, administer Idle Appearance Preference for the telephone. The 
called party can then lift the handset without accidentally connecting to a 
call that should be screened.
nIntegrated Services Digital Network — Basic Rate Interface
When an ISDN-BRI telephone (with Select Last Used Appearance 
enabled) transfers a call while off-hook by using the handset, the user hears 
dial tone on the last-used call appearance. Users of other telephone types 
hear silence in this case.
Related Topics
For more information, refer to ‘‘
Station’’ on page 882. You administer this feature 
with the following two fields:
nIdle Appearance Preference
nSelect Last Used Appearance 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1438 Multifrequency Signaling 
20
Multifrequency Signaling
Multifrequency (MF) signaling is a form of address signaling used between 
switches and the central office (CO). It is similar to dual-tone multifrequency 
(DTMF) signaling in that tones convey the dialed number.
With MF signaling, the signal is typically a combination of two frequencies from 
a group of 5 or 6 frequencies (2/5 or 2/6). The origination switch and destination 
switch exchange tones that have specific meanings according to the MF protocol.
Detailed description
DEFINITY ECS supports two frequency groups:
nR2-multifrequency compelled signaling (R2-MFC) frequency
nR1 frequency (for Spain and Russia)
R2-MFC is a version of MFC recommended by the International 
Telecommunication Union (ITU). It provides signaling between a CO and a 
switch over analog or digital CO, Direct Inward Dialing (DID), or Direct Inward 
and Outward Dialing (DIOD) trunks. It also provides signaling between 2 
DEFINITY switches.
DEFINITY ECS provides MF signaling that complies with ITU regulations and 
national regulations for specific countries. It provides these types of MF signaling: 
Multifrequency Espana (MFE), MF Shuttle, and multifrequency compelled 
(R2-MFC). These protocols signal the called number, the calling party’s number 
(automatic number identification (ANI)), and information about the type of call or 
type of caller (category).
DEFINITY ECS allows prefix digits for ANI sent on outgoing calls to be defined 
per PBX or per the originator’s class of restriction.
If a call is a tandem call and the incoming and outgoing trunk use different 
protocols, the switch makes no attempt to convert between the various protocol’s 
meanings for category. Instead,
nthe PBX uses the incoming trunk’s Class of Restriction (COR) assigned 
category if the outgoing trunk is Russian or R2-MFC, and
nthe PBX uses ARS call types if the outgoing trunk is MFE.
DEFINITY ECS provides the incoming ANI to all features on the switch that need 
to identify the calling party. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1439 Multifrequency Signaling 
20
MFE
MFE, for Country code 11 (Spain), uses R1 frequency and compelled signaling. It 
is available on CO and DID trunk groups. There are four kinds of MFE signaling:
nPublic 2/5
nPublic 2/6
nIbercom 2/5
nIbercom 2/6
MF Shuttle
MF shuttle signaling, for country code 15 (Russia), uses R1 frequency and 
noncompelled signaling. With MF shuttle signaling, it is possible to change to 
decadic rotary pulse in the middle of address signal exchange. MF shuttle 
signaling is available on CO, DID, and DIOD trunk groups.
Also, automatic number identification (ANI) transmission, for Country code 15, 
uses a gapless R1 MF signal and is completed within 800ms. This is available on 
an outgoing CO trunk group.
R2-MFC
R2-MFC permits each country to define the meanings of the R2 frequency 
combinations. Specific frequency combinations for different countries are 
described in the DEFINITY ECS Application Notes for Type Approval.
R2-MFC Considerations
nBoth non-group II signaling and group II signaling are supported on 
incoming MF signaling calls. The group II signaling protocol has an extra 
signal that provides caller-category information. Only group II signaling is 
supported on outgoing MF signaling calls.
nMF signaling also can be used in tandem trunk groups. After address 
signals are collected from an incoming group II MF signaling call, the call 
can route to a group II MF signaling trunk.
nBoth incoming and outgoing MF signaling calls support ANI. The terminal 
displays ANI information and the Call Detail Recording (CDR) record 
records it.
nWhen DEFINITY ECS uses an open numbering plan, the end-of-dial 
signal must be defined in the incoming Group I signal administration. After 
sending all address digits, the CO sends the end-of-dial signal to 
DEFINITY ECS.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1440 Multifrequency Signaling 
20
nIf DEFINITY ECS makes an outgoing call to the CO that uses an open 
numbering plan, the CO should send the signal A.1 to DEFINITY ECS 
after sending the last address digit to the CO. Then, the CO should timeout 
and send a pulsed signal A.3 to DEFINITY ECS requesting the Group II 
signal.
Guidelines for administering MF signaling
To administer MF signaling, first you identify the origination switch and the 
destination switch. (The switch making the call is the origination switch; the 
switch answering the call is the destination switch.) 
nThe origination switch creates forward signals, classified as group I and 
group II signals. 
nThe destination switch creates backward signals, classified as group A and 
group B signals. 
Group I and group A signals comprise the basic signaling for the dialed number. 
More elaborate signaling requires Group II and group B signals. Signal meanings 
and timer values can be administered.
The sequence below shows a typical interaction between the origination (forward 
group I and group II signals) and destination switch (backward group A and group 
B signals).
Forward Backward
Group I digit -->






						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1441 Multifrequency Signaling 
20
Second, you assign the correlation between signal codes and their meanings.
1. Assign a code to every message. The code consists of a group category, like 
group II or A, and a number.
nFor example, you might assign code A.1 to the message 
“next-digit.” 
2. Assign a signal to each identifying code. 
nIn every country, the frequencies (levels may differ by country) 
assigned to the identifying codes are the same. However, the 
messages assigned to the identifying codes may be different. 
For example, in Switzerland the B.6 code and its associated signal 
convey the free message, while in Thailand, free is conveyed by the 
B.1 code and its associated signal. But in both Switzerland and 
Thailand, the frequency associated with the B.1 code is the same.
As another example, you might assign the signal “busy” to the B.1 
code.
To receive Russian incoming ANI:
nOn the DID or DIOD trunk group screen, set the Country field to 15 and 
the Protocol Type field to 
inloc.
nOn AAR and ARS Digit Analysis Table screen, set the ANI Rq field to y or 
on AAR and ARS Digit Conversion Table screen, set the ANI Req field 
to
y.
Interactions
nASAI
ANI collected from incoming R2-MFC signaling can be used with ASAI.
nAbbreviated Dialing
Although calls dialed automatically from an abbreviated dialing privileged 
list complete without class of restriction (COR) checking, ANI prefix and 
ANI truncation still apply.
nAttendant Console
If the attendant assists or extends a call for a station via Straightforward 
Outward Completion and Through Dialing, and if the attendant has not yet 
released the call when the request for ANI comes in from the far end, the 
attendant’s COR is used to select the ANI for the call. If the attendant has 
already released the call when the request for ANI comes in from the far 
end, the attendant’s COR is used to select the ANI for the call. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1442 Multifrequency Signaling 
20
nAuthorization Codes
The COR of the authorization code as administered on the 
authorization-code form is not used for ANI prefix determination, even if 
the originating endpoint enters an authorization code before call processing 
for an outgoing call seizes an outgoing trunk. If the originating endpoint is 
an extension, the extension’s ANI is used. If the originating endpoint is an 
incoming trunk, the ANI for PBX is used.
nBridging
The ANI of a telephone’s primary extension also applies to calls originated 
from a bridged call appearance of that extension on another terminal. ANI 
prefix and ANI truncation will still apply to the primary extension number 
of bridged call appearances.
nCall Detail Recording
CDR records ANI collected from incoming MF signaling.
For India MFC, on incoming calls, ANI digits may be appended with 
zeroes if the actual ANI digits are less than the administered ANI-length; in 
those cases, the zero-digits appear on CDR.
nCall Redirection
A call is redirected if any of the following are active: Call Forwarding, Call 
Coverage, Send All Calls, or Night Service.
nCall Vectoring
Call Vectoring can now use ANI collected from incoming MFC signaling.
The ANI of a call vector is not used when a call vectoring route-to 
command routes a call over an outgoing trunk. Instead, the ANI of the 
originating party is sent.
nDID No Answer Timer
DID No Answer Timer is applied to MF signaling DID calls.
nDistributed Communications System (DCS)
In a DCS arrangement, the ANI sent to the CO is determined by the ANI 
for PBX on PBX_B, but the category sent to the CO is determined by the 
Category for MF ANI field on the Class of Restriction form for the 
incoming DCS trunk or by the type of call.
nExpert Agent Select (EAS)
For ANI, the EAS agent’s login extension number and COR overrides the 
extension number and COR of the physical terminal where the agent is 
logged in. ANI prefix and ANI truncation apply to logged in EAS agents. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1443 Multifrequency Signaling 
20
nHunt Groups and Automatic Call Distribution (ACD) Splits
For ANI, a physical terminal’s extension number and COR overrides the 
extension number and COR of the hunt group or ACD split that the 
terminal is a member of or logged into. ANI prefix and ANI truncation 
apply to terminals that are members of hunt groups or logged into ACD 
splits.
nIntercept treatment
For DID MF signaling calls that are denied, you can administer whether the 
corresponding B.x signal or intercept tone should be sent to the CO. The 
default is to send the administered DID/TIE/ISDN Intercept Treatment. If 
the option to send the B.x signal is set, then:
— For Group II calls, the B.x signal for the intercept is sent to the CO.
— For non-Group II calls, if the CO dials an invalid number, the trunk 
is locked (regardless of this option). If the CO dials a number that is 
valid but not assigned, intercept tone is sent to the CO.
nMultimedia Call Handling (MMCH)
For call origination, multimedia complexes use the COR assigned to their 
telephones. ANI prefix and ANI truncation will apply to the telephones 
assigned to multimedia complexes.
nOff-Net Call Coverage or Call Forwarding
If the originating endpoint is an extension, the extension’s ANI is used. If 
the originating endpoint is an incoming trunk that can supply ANI, the ANI 
received from the incoming trunk is used. If the originating endpoint is 
neither of the above, the ANI for PBX is used.
nPersonal Station Access (PSA)
For ANI, the PSA extension number and COR overrides the extension 
number and COR of the physical terminal where the PSA extension 
number is associated. ANI prefix and ANI truncation will apply to 
associated PSA extension numbers.
nRemote Access
The COR of a remote access barrier code is not used for ANI prefix 
determination when the originating end point dials a remote access 
extension and then places a call. If the originating endpoint is an extension, 
the extension’s ANI is used. If the originating endpoint is an incoming 
trunk, the ANI for PBX is used.
nStation Set Displays
When no ANI is possible, if station sets are equipped with display option, 
they do not display the ANI digits. Instead, the trunk group name displays. 
When ANI is possible, ANI displays on the station set. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1444 Night Service 
20
For India Only. If ANI digits are padded with “zero,” then zeroes also are 
displayed along with ANI digits.
nTandem / Offnet Calls
If ANI digits are received on incoming MFC calls, the ANI digits are sent 
to outgoing tandem/off-net calls.
For Russia Only. The ANI is requested on incoming trunks only when all 
the address digits have been collected. When the incoming trunk on a 
tandem call is a Russian incoming local trunk administered to collect ANI, 
the PBX collects all ANI digits before seizing the outgoing tandem trunk. 
This happens even if ARS is administered with a “min” value low enough 
that it would be possible to determine an outgoing route through digit 
analysis.
For India Only. On an outgoing tandem-call, the default operation is to 
send the ANI-Not-Available forward signal if ANI is not available from the 
incoming trunk. However, in order to support this operation, leave the ANI 
for PBX field blank, and define the ANI-Not-Available signal.
Related topics 
For administration settings, see ‘‘
Multifrequency-Signaling-Related System 
Parameters’’ on page 823. 
To establish MF Signaling for a trunk group, see ‘‘
Trunk Group’’ on page 967, 
(CO, DID, DIOC, TIE) - Incoming and Outgoing Dial Type.
To set up MFC ANI, refer to ‘‘
AAR and ARS Digit Analysis Table’’ on page 451, 
‘‘
AAR and ARS Digit Conversion Table’’ on page 455, and ‘‘Class of 
Restriction’’ on page 520.
Night Service
DEFINITY ECS provides the following Night Service features:
nHunt Group Night Service
nNight Console Service
nNight Station Service
nTrunk Answer from Any Station
nTrunk Group Night Service 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1445 Night Service 
20
Hunt Group Night Service
Hunt Group Night Service allows an attendant or a split supervisor to assign a 
hunt group or split to Night Service mode. All calls for the hunt group then are 
redirected to the hunt group’s designated Night Service extension (NSE). When a 
user activates Hunt Group Night Service, the associated button lamp lights.
Night Console Service
Night Console Service directs all calls for primary and daytime attendant consoles 
to a night console. When a user activates Night Console Service, the Night Service 
button for each attendant lights and all attendant-seeking calls (and calls waiting) 
in the queue are directed to the night console.
To activate and deactivate this feature, the attendant typically presses the Night 
button on the principal attendant console or designated console.
Night Station Service
Night Station Service directs incoming calls for the attendant to designated 
extensions. Attendants can activate Night Station Service by pressing the Night 
button on the principle console if there is not an active night console. If the night 
station is busy, calls (including emergency attendant calls) receive busy tone. They 
do not queue for the attendant.
When Night Station Service is active, incoming calls to the attendant route as 
follows:
nDID Listed Directory Number (LDN) calls route to a designated DID-LDN 
night extension.
nInternal calls route to the DID-LDN night extension (unless you administer 
the system so only DID-LDN calls can route to the LDN night extension).
nNon-DID calls route to the night destination that you specify for the trunk 
group or for the individual trunk. If you do not specify a night destination, 
the calls route to the DID-LDN night extension.
You can assign a unique extension as the night destination for each incoming 
central-office, foreign-exchange, or 800-Service trunk group. Both the extension 
assigned as a trunk group’s night destination and the DID-LDN night extension 
can be phones or answering groups (such as DDC group, UCD group, or TEG). 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1446 Night Service 
20
Trunk Answer from Any Station
Trunk Answer from Any Station (TAAS) allows phone users to answer all 
incoming calls to the attendant when the attendant is not on duty and when other 
phones have not been designated to answer the calls. The incoming call activates a 
gong, bell, or chime and a phone user dials an access code to answer the call.
Users can activate TAAS if each of the following conditions is met:
nThe attendant has pressed the Night button on the primary console or a user 
(if the switch has no attendant) pressed the Night Service button on the 
designated Night Service phone.
nA night console is not assigned or is not operational.
nNight Station Service is not active.
Trunk Group Night Service
Trunk Group Night Service allows an attendant or a designated Night Service 
phone user to assign one or all trunk groups to Night Service mode. When a user 
activates Night Service, trunk groups that are assigned a Trunk Group Night 
Service termination change to Individual Trunk Night Service mode so that calls 
coming into the trunk group are redirected to the group’s designated Night Service 
extension (NSE). Incoming calls on trunk groups that are not assigned to Trunk 
Group Night Service are queued in the attendant queue. If the call remains 
unanswered during the Night Service Disconnect Timer interval, the incoming 
trunk disconnects.
In addition, a user can assign all the trunk groups to the night service mode at the 
same time. Then all the trunk groups are in the System Night Service mode. Any 
incoming calls made on the trunk groups are redirected to their designated NSE. 
To assign all the trunk groups to System Night Service, the user presses the 
System Night Service button on the principal attendant console or the Night 
Service button on a designated phone. You can assign a Night Service button to 
only one phone.
You can activate Night Service for specific trunk groups (Trunk Group Night 
Service) by pressing the individual Trunk Night Service buttons on the attendant 
console or on a phone. You can assign Trunk Night Service buttons on more than 
one phone.