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 
1497 Service observing 
20
Warning and conference tones
If you administer a tone to notify the parties on a call when they are being 
observed, you can choose between a warning tone and conference tone. If you 
select warning tone, a unique 2-second, 440-Hz warning tone plays before an 
observer connects to the call. While the call is observed, a shorter version of this 
tone repeats every 12 seconds. If you select conference tone, all parties will hear 
conference tone before an observer connects to the call. However, unlike warning 
tone the conference tone is not repeated.
Interactions
nAttendants
An attendant can be observed but cannot be an observer.
nBridged Appearances
You can only observe calls on primary extensions, not on bridged 
appearances. For example, let’s say you’re observing extension 3082 and 
this phone also has a bridged appearance for extension 3282. You can’t 
observe calls to 3282.
nBusy-Verification 
You can’t observe an extension that’s being busy-verified. You can’t 
busy-verify an extension that’s being observed.
nCall Coverage/Call Pickup
An observer cannot observe a call answered by a covering agent or a 
member of a pickup group unless the called agent bridges onto the call.
nCall Park
An observer cannot park the call they are observing. 
nCall Waiting
Incoming calls cannot wait on a single-line phone that is being observed.
nConference
Observers cannot initiate a conference while observing.
If an observed user starts a conference or enters a conference with fewer 
than 6 parties, the observer is placed in wait state until the call is connected. 
Then the observer observes the conference and is counted as one party in 
the conference. (Conference members are observed during a conference 
regardless of their COR setting.) In addition, the observer is bridged onto 
any calls the user makes or receives before the conference is complete. 
When the user leaves the conference, the observer also leaves and returns 
to observing the original call. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1498 Service observing 
20
nData Privacy
You can’t observe an extension on which Data Privacy is active. You also 
can’t observe an extension while it’s on a conference call with another 
extension using Data Privacy.
nData Restriction
You can’t observe an extension on which Data Restriction is active. You 
also can’t observe an extension while it’s on a conference call with another 
extension using Data Restriction.
nIntegrated Directory
Observers do not hear users dialing when the latter use this feature.
nDCS
To observe stations on another node (a DCS station extension), you must 
set up remote-access service observing. Service observing displays are not 
transmitted across DCS networks.
nHold
Observers cannot place calls on hold while they’re observing. If a user 
places a call on hold, the observer enters wait state. 
nLeave Word Calling
Parties on an observed call cannot use LWC.
nMusic-on-Delay/Music-on-Hold
If an observer is in listen/talk mode, neither caller nor observer hears 
music-on-hold. If an observer is in listen-only mode, the caller hears 
music-on-hold but the observer does not. 
nPrivacy — Manual Exclusion
You can’t observe an extension on which Privacy — Manual Exclusion is 
active. You also can’t observe an extension while it’s on a conference call 
with another extension using Privacy — Manual Exclusion.
nTransfer
Observers cannot initiate a transfer while observing.
If a user transfers a call, the observer is placed in wait state. The observer is 
bridged onto the call when the transfer is complete.
Related topics
Refer to ‘‘
Observing calls’’ on page 402 to administer service observing. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1499 Single-Digit Dialing and Mixed Station Numbering 
20
Single-Digit Dialing and Mixed 
Station Numbering
Single-Digit Dialing and Mixed Station Numbering allows easy guest access to 
internal hotel/motel services and provides the capability to associate room 
numbers with guest-room telephones.
Detailed description 
You must create a dial plan for hotel/motel services and room numbers. Some 
suggestions follow. Refer to ‘‘
Dial Plan Record’’ on page 607 for more 
information.
nAssign a single-digit extension to internal hotel/motel services such as 
room service. Assign single-digit extensions to individual-telephones or to 
a group of telephones (for example, to service the front desk).
nAssign a prefixed extension to guest rooms.
A prefixed extension is made up of a prefix and an extension up to five 
digits. The prefix identifies the call type. The switch collects dialed digits, 
removes the prefix digit, and uses the extension for further processing.
nMixed station numbering extensions can have from one to five digits and 
can begin with any digit from 0 to 9.
The first digit, in combination with the number of digits dialed, defines the 
call type. To differentiate between two numbers with the same leading digit 
but different lengths, the system monitors the interval after a digit is dialed 
and before the next digit is dialed. If the interval extends past the 
administered interdigit timeout, the system assumes that dialing is 
complete and calculates the number of digits dialed up to that point. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1500 Single-Digit Dialing and Mixed Station Numbering 
20
Examples
Dial plan 1 allows the following dial access:
nThe prefixed extensions do not show up on the Dial Plan table; they are 
implied by their absence. The prefixed extensions in the example are 
indicated by the 0 symbol.
nSingle-digit access to the hotel/motel attendant (0)
nTen dial-access codes (DACs) beginning with the digit 1 (10 through 19)
nSingle-digit access to five hotel/motel services (2, 3, 4, 6 and 7)
nNonprefixed access to as many as 100 hotel/motel staff extensions
(500 through 599)
nGuest room extensions for as many as 100 floors
— Access to floors 1 through 9 (prefix digit 6 + [100 through 999])
— Access to floors 10 through 99 (prefix digit 7 + [1000 through 
9999])
nToll-call access via DAC 8
Table 53. Sample Hotel/Motel Dial Plan 1
Length
First Digit12345
1 DAC
2EXT 00
3EXT 00
4EXT 00
5EXT
6EXT 0PEXT
7EXT 00PEXT
8DAC
9DAC
0ATTD
*FAC
#FAC 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1501 Single-Digit Dialing and Mixed Station Numbering 
20
nLocal calling via ARS DAC 9
n2-digit feature-access codes (FACs) [* or # plus another digit]
Dial plan 2 allows the following dial access:
nSingle-digit access to the hotel/motel attendant (0)
nSingle-digit access to seven hotel/motel services (extensions 1 through 7)
n2-digit access to 70 hotel/motel services (extensions 10 through 79)
nGuest-room extensions for floors 1 through 7 (extensions 100 through 799)
nToll-calling access via DAC 8
nToll-calling access via ARS feature access code 9
n2-digit FACs (* or # plus another digit)
Cancel timeout intervals if the user dials # after dialing all required digits.
Table 54. Sample Hotel/Motel Dial Plan 2
Length
First Digit 1 2 3 4 5
1 EXT EXT EXT
2 EXT EXT EXT
3 EXT EXT EXT
4 EXT EXT EXT
5 EXT EXT EXT
6 EXT EXT EXT
7 EXT EXT EXT
8 DAC 
9 DAC 
0 ATTD 
*FAC 
#FAC  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1502 Single-Digit Dialing and Mixed Station Numbering 
20
When using prefixed extension numbers, it is not necessary to include an entry for 
the real extension number in the dial plan. The server is able to complete a call 
using the prefixed extension number.  When dialing 7345 (where 7 is the prefix), 
the communications server will ring extension 345.
When using a dial plan like the one above, which includes both prefixed and 
non-prefixed extensions, dialing 567 instead of 4567 will ring an administrative 
extension instead of a room.
The dialing delays, which may not be perceived by hotel guests, will occur when 
dialing 6 and 7. The server must wait for the 3- to 9-second interdigit timeout to 
expire before the call will be sent. The user can preempt the timer by pressing the 
# key after the number has been dialed.
NOTE:
When using prefixed extensions, the extension that shows up on a 
display phone does not show the prefix. The prefix will not show up 
on CDR reports. If extension number 3315 is prefixed with a 6 and 
the dial plan shows 3xxx for extensions, it is possible to dial either 
3315 or 63315 to reach extension 3315. If the dial plan was changed 
to remove the entry for extensions in the 3xxx block, then 3315 could 
be reached only by dialing 63315.
Considerations
nMixed Station Numbering allows guest room numbers and room 
extensions to be the same.
nYou cannot assign prefixed extensions longer than five digits (including 
prefix) to intercom lists.
nA trunk access code (TAC) and an extension can share a first digit only if 
the extension is shorter than the TAC.
nAlthough extensions with the same first digit can have different lengths, 
data-channel extensions must have the maximum number of digits to avoid 
timeout problems for data calls that the switch automatically sets up, for 
example, via the Call Detail Recording (CDR) link.
nAn extension and a FAC can share the same first digit only if the extension 
is longer as long as they are not used for Automatic Alternate 
Routing/Automatic Route Selection (AAR/ARS) faxes. These extensions 
work only within the switch; they do not work as remote uniform dialing 
plan (UDP) extensions.
nYou should administer the Short Interdigit Timeout on the Feature-Related 
System Parameters screen to ensure that the delay between the end of 
dialing and call completion is not too long. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1503 Station Hunting 
20
Interactions
nAttendant Display and Telephone Display
Prefixed extensions display without the prefix. The return call button 
causes the prefix to dial, even though it does not display.
nProperty Management System (PMS)
Remove prefixes before messages containing the extension are sent to the 
PMS.
Five-digit extensions do not exchange with PMS until modifications are 
made to the PMS interface.
nUniform Dial Plan
The following limitations apply to a distributed communications system 
(DCS) environment:
— Extensions that differ in length from the UDP do not distribute to 
other switches.
— If the first two digits of an extension correspond to the floor number, 
floors cannot be serviced by more than one switch.
Station Hunting
Station Hunting routes calls made to a busy station down a chain of stations until 
one is found that is not active. 
Detailed description
To use Station Hunting, you create a station hunting chain that governs the order 
in which a call routes from one station to the next when the called station is busy. 
Each station in the chain links to only one subsequent station. However, any 
number of stations may link to one station.
The system updates the calling party’s display with “h” when the system begins 
checking the station-hunting chain. Likewise, the system updates the display of 
the station that is hunted-to (the station that takes the call) with an “h.” 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1504 Station Hunting 
20
Calls route through the chain as follows.
There is no limit to the number of extensions that can be in a station-hunting 
chain.
Station Hunting examples
In this example (Table 56
), extension 2 is the called extension. Because extension 
2 is busy, the system follows the station-hunting chain to find an idle extension. 
The system cannot find an idle extension so it returns busy tone to the caller. Note 
that the chain terminates with extension 5. This means that the system cannot 
route the call to extension 1 even though it is an idle extension in the chain.
Table 55. Station Hunting Characteristics
Condition Response
Encounters an idle extension  Rings extension
Encounters an active extension  Routes to next extension in chain 
Encounters an extension with a blank 
hunt-to station fieldReturns busy tone if no station was 
idle
Encounters any station a second time Returns busy tone
Has checked 30 stations in the chain, 
without finding an idle oneReturns busy tone
Table 56. Station-Hunting Chain — Example 1
Extension State Rings on extension
1Idle2
2Busy3
3Active4
4Active5
5Busy 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1505 Station Hunting 
20
In this example (Table 57), extension 2 is the called extension. Because extension 
2 is busy, the system follows the station-hunting chain to find an idle extension. 
The call is answered at extension 1.
In this example (Table 58), extension 2 is the called extension. Because extension 
2 is busy, the system follows the station-hunting chain to find an idle extension. 
The system encounters extension 3 a second time without finding an idle station. 
The system stops checking the station-hunting chain and returns busy tone to the 
caller. Notice that both extensions 5 and 2 link to extension 3.
Table 57. Station-Hunting Chain — Example 2
Extension StateRings on 
extension
1Idle2
2Busy3
3Busy4
4Active5
5Active1
Table 58. Station-Hunting Chain — Example 3
Extension StateRings on 
extension
1Idle2
2Busy3
3Busy4
4Busy5
5Busy3 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Features and technical reference 
1506 Station Hunting 
20
Station hunting options
You can administer the system to perform station hunting prior to sending calls to 
coverage. The Station Hunt Before Coverage option on the System-Parameters 
Call Coverage/Call Forwarding screen provides that when a call is made to a busy 
station, the switch checks to see if there is a hunt-to station assigned to the busy 
station. If there is, the switch tries to connect to the hunt-to station before going to 
coverage. If the hunt-to station is also busy, the switch continues hunting down the 
hunt-to chain. If all stations in the hunt-to chain are busy, the call goes to the 
dialed station’s coverage.
Administration commands
When you remove a station, the system attempts to maintain a station-hunting 
chain. Consider the following examples:
nStation 1 links to 2 and 2 links to 3. If you remove station 2, the system 
links 1 to 3.
nStation 1 links to 2. Station 2 does not link to another extension. If you 
remove station 2, 1 no longer links to another extension.
When you duplicate a station, the extension in the hunt-to station field is not 
copied into the duplicated station.
When you execute “
list usage extension xxxxx,” the system displays all stations 
that contain the station’s extension as their hunt-to station.
Interactions
Remember that the system checks the station-hunting chain only for idle and 
available extensions.
nAdjunct Switch Applications Interface
The system attempts Station Hunting when ASAI routes to an extension 
with a hunt-to station.
nAutomatic Call Distribution
An agent extension can be part of a station-hunting chain. The system 
hunts the agent’s chain only when the call is made directly to the agent’s 
extension. Calls distributed through hunt groups to an ACD agent do not 
hunt the agent’s station-hunting chain. Calls made to an extension for 
logical agents do not hunt the agent’s station-hunting chain.
nAutomatic Callback
The system does not hunt the chain of the called extension when the call is 
a callback-return call.