Lucent Technologies DEFINITY, DEFINITY 6 User Manual

DEFINITY

®

Enterprise Communications Server

Release 6, Issue 2.1 (02.1.125.1)
Change Description

555-233-402
Comcode 108286063
Issue 2
May 19 98

Copyright  1998, Lucent Technologies
All Rights Reserved
Printed in U.S.A.

Notice

Every effort was made to ensure that the information in this book was com­plete and accurate at the time of printing. However, information is subject
to change.

Your Responsibility for Your System’s Security

Toll fraud is th e unauthorized use of your telecommunications system by

an unauthorized party, for example, persons other than your company’s
employees, agents, subcontractors, or persons working on your company’s
behalf. Note th at there may be a risk of toll fraud associated with your tele­communications system and, if toll fr aud occurs, it can result in substantial
additional charges for your telecommunications services.

You and your system manager are responsible for the security of your sys­tem, such as programming and configuring your equipment to prevent
unauthorized use. The system manager is also responsible for reading all
installation, instruction, and system administration documents provided
with this p ro du ct i n o rd er to f ull y u nd e rst and the features that can i ntr od uce
risk of toll fraud and the steps that can be taken to reduce that risk. Lucent
Technologies does not warrant that this product is immune from or will
prevent unauthorized use of common-carrier telecommunication services
or facilities accessed through or connected to it. Lucent Technologies will
not be responsible for any charges that result from such un authorized use.

Lucent Technologies Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need
technical support or assistance, call Technical Serv ice Center Toll Fraud
Intervention Hotline at 1 800 643-2353.

Federal Communications Commission Statement
Part 15: Class A Statement. T his equipment has been tested and found to

comply with the limits for a Class A digital device, pu rsuant to Part 15 of
the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commer­cial environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in acco rdance with the
instruction manual, may cause harmful interference to radio communica­tions. Operation of this equipment in a residential ar ea is likely to cause
harmful interference, in which case the user will be required to correct the
interference at his own expense.

Part 68: Network Registration Number. This equipment is registered
with the FCC in accordance with Part 68 of the FCC Rules. It is identified
by FCC registration number AS593M -13283-MF- E.

Part 68: Answer-Supervision Signaling. Allowing this equipment to be
operated in a manner that does not provide proper answer-supervision sig­naling is in violation of Part 68 rules. This equipment returns answer­supervision signals to the public switched network when:

• Answered by the called station

• Answered by the attendant

• Routed to a recorded announcement that can be administered
by the CPE us er

This equipment returns answer-supervision signals on all DID calls for­warded back to the public switched telephone network. Permissible excep­tions are:

• A call is unanswered

• A busy tone is received

• A reorder tone is received

Canadian Department of Communications (DOC)
Interference Information

This digital apparatus does no t exceed the Class A limits for radio noise
emissions set ou t in the radio interference regulations of the Canadian
Department of Communications.

Le Pr

ésent Appareil Nomérique n’émet pas de bruits radioélectriques

d

épassant les limites applicables aux appareils numériques de la class A

pr

éscrites dans le reglement sur le brouillage radioélectrique édicté par le

minist

ére des Communi cation s du Canada.

Trademar k s

DEFINITY is a registered trademark of Lucent Technologies in the United
States and throughout the world.

Ordering Information
Call: Lucent Technologies BCS Publications Center

Voice 1 800 457-1235 International Voice 317 322-6791
Fax [phone] International Fax [phone]

Write: Lucent Technologies BCS Publications Center

2855 N. Franklin Road
Indianapolis, IN 46219

Order: Document Number: 555-233-402

Comcode 108286063
Issue 2, May 1998

You can be placed on a Standing Order list for this and other documents
you may need. Standing Order will enable you to automatically receive
updated versions of individual documents or document sets, billed to
account informatio n that you provide. For more information on Standing
Orders, or to be put on a list to receive future issues of this document,
please contact the Lucent Technologies Publications Center.

Europ ean Uni on Declaration of Conform ity

The “CE” mark affixed to the DEFINITY equipment described in this doc­ument indicates that the equip ment conforms to the following European
Union (EU) Directives:

• Electromagnetic Compatibility (89/336/EEC)

• Low Voltage (73/23/E EC)

• Telecommunication Terminal Equipment (TTE)
i-CTR3 BRI and i-CTR4 PRI

For more information on standards compliance, contact your local
distributor.

Comments

To comment on this document, return the comment card at the front of the
document.

Acknowledgment

This document was prepared by the Product Documentation Development
group, Lucent Technologies, Denver, CO.

Issue 2 May 1998 1

Highlights

This change description document describes the changes incorporated in
DEFINITY Enterprise Communications Server (ECS), Release 6, Issue 2.1
(02.1.125.1).

Platform

Offer Category

For R6.2, two offer categories are supported. Category A is used for DEFINITY
ECS R6 and DEFINITY ProLogix Solutions systems. Category B is used for
DEFINITY BCS Issue 4.0 and GuestWorks server Issue 4.0 systems. See

DEFINITY ECS R6 Administration and Feature Descrip tion

, 555-230-522, Issue 3

for admin istration details. See

DEFINITY ECS R6 System Description Pocket

Reference

, 555-230-211, Issue 2.0 or later for details ab o ut which features and

hardware are allowed with each offer cat egory.
In R6, I ssu e 2.1, c hanges were made to allow execution of mtce, list, and

display commands, as well as ad m inistration of an externa l modem prior to
admini stration of the category.

Highlights of Features and Enhancements

Abbreviated Dialing (AD)

Using an abbreviated dialing button for end-to-end signaling was possible only
from the originating station or after a trunk flash when the call included a single
trunk that was administered to support trunk flash. Now, a terminating station can
use an abbreviated dialing button to do end-to-end signaling on any facilities that
can generate the tones.

2 Issue 2 May 1998

Announcement Boards

The list configuration command did not display translated but uninserted
announcement boards properly.

AUDIX Transfer

AUDIX transfers di d not c om plete when the number of outstand in g calls was
greater than 31. Now, AUDIX transfers complete when the number of outstanding
calls is 32. Also, for Intel mac hines, the max imum number of AUDIX ports
allowed is now 64.

Call Center

When trying to redirect a call on no answer to a VDN while processin g a failed
"conv erse on" vector step, the call went into limbo as c al l processing tried to
route call to the RONA V DN. Now, attempts to RONA a call to a VDN are blocked
if the call is in vector processing of a "converse on" v ector step. A new vec to r

event is generated, "RONA to VDN in converse.”

Call Classi fica tio n

There was no way to administer dB adjustment for the Call Classifier. Now, a new
field, Global Classifier Adjustment (dB), on pag e 1 of the system-parameters
ocm -call-c l as sification form allows for ad m ini stration of d B adjustment for the
Call Classifier when using the OCM feature.

Call Coverage/Call Forwarding/Coverage of Calls
Redirected Off-Net (CCRON)

When an off-net cov erage or forwarded call cannot find an availab le trunk, the
call is redirected back to the original principal.

When an off-net cov erage or forwarded call could not find an availa ble trunk,
busy tone was played back to the calling party, effectively ending the call . Now,
the call is redirected back to the original principal whenever possible.

If a user forwarded a station to a remote number for which the length of the
number (including an ARS or AAR feature acc ess code) was 16 d igits, and the
number required an interdig it timeout (typic al ly, an international number, for
examp le, 88+0 11-44-7197 10089), the number was acc epted. But when a c all
was forwarded, the system waited indefinitely for the end-of-dialing timeout or a
pou nd sig n (#). (Note that a pound sign is stored with the number when the
number of digits is less than 16.) Now, Call Forwarding works correctly for any
number of digits up to, and including, 16. Call Forwarding cannot store more than
16 digits at present.

Issue 2 May 1998 3

When a brid ge of the orig in ating party d r opped out of a c all that had routed
off-net with call c lassification on a non-ISDN end-to-end trunk, the c all was torn
down. Now, the call is not torn down, but call classification is terminated, the call
is left off-net, and it is not redirected to subsequent coverage.

If both CCRON and Answer Supervision by Call Classification features were
active on an off-net c al l, the call di d not further redirect to subseq uent coverage
points.

When an attendant extended a call to a prin cipal with red irec t ed off-net via the
CCRON feature, the call did not return to the attendant when the Return Call timer
expired.

Integrated Services DIgital Net work (ISDN)

To increase the T.305 timer for the Nortel DMS COs, a new protocol version for
the US (country code 1) was created. This new protocol version option is labeled

as “c.” The new cou ntr y code/p rotocol version is automatically assigned a
30-second value to the T.305 timer.

Terminal Translation Initialization (TTI)

Turning off TTI removes ports that are administered b y TTI on cabinets that have
bee n removed.

Upgrades

Upgrades from G3V4 07.0.077 or greater to R6.2 have correct defaults for new
R6 PPM fields on the DS1 form.

4 Issue 2 May 1998

Issue 2 May 1998 5

Feature or category See item numbers Feature or category See item numbers

A

AAR Analysis For m 53
Abbreviated Dialing ( AD) 40
Active Ringing 14
Adjunct Swi tch Application Interface (ASAl)53
Adjuncts 39, 53
Administration 6

, 15, 17, 20, 21, 26, 32, 33,

34, 39, 40, 46, 51, 52, 54

Administration Without Hardware (AWOH)6, 26
Agents 11

, 17, 18, 19, 32, 35, 45, 47,

51, 56

Analog Stations 39
Announcements 2, 14, 21
Answer Supervision 9
Attendants 13, 30
AUDIX 8, 25, 28, 57
Authorization Codes 46
Automatic Alternate Rout ing (AAR )48, 53
Automatic Call Distribution (ACD)11

, 12, 16, 18, 41, 45,

47, 51

Automatic Circuit Assurance (ACA)44
Automatic Number Identification (ANI)24
Automatic Route Selection (ARS)22, 31, 48
AVD 29

B

Basic Call Management System (BCMS)10, 16, 19
Basic Rate Interface (BRI) 2, 46, 55
Bridg i ng 4, 46

C

Call App e a r an ces 14

Call Classification 4, 9, 33
Call Coverage 1

, 3, 4, 5, 8, 9, 13, 31, 32, 47,

49

Call Detail Rec or d i ng (CDR)27
Call Forward ing 1, 5, 6, 9, 13, 38, 48, 49
Call Management System (CMS)10, 19
Call Vectoring 14, 18, 23
Calls Redirect ed Off-Net 4, 9
Capac ities 41, 45
Cause V alues 2, 22, 55
Central Office (CO) 38, 59
Circuit Packs 37, 52, 54
Class of Restriction (COR) 32
Conference 3
Conversant 24
Corruption 7, 26, 34
Coverage of Calls Redirected Off-Net (CCRON)1

, 9, 13,

31

D

Day Ser vice 30
Direct Agent 32
Direct Inward Dialing (DID) 38
Display Capacity Form 41
Displays 3

, 17, 18, 25, 32, 35, 43, 45,

46, 47, 51, 52, 57
Distributed Communications System (DCS)3, 36, 47, 50
DS1 15, 37

E

Electronic Tandem Network (ETN)50
Error Messages 10, 43

Index of Changes

The following lists the item numb ers of the features and c ategories that are affected by the
c hanges, modifications, and enhancements that are described in the next section.

6 Issue 2 May 1998

Feature or category See item numbers Feature or category See item numbers

Index of Changes

Ex pansion Port Networks (EPNs)7
Ex pert Agent Selection (EAS)19, 32, 47, 56

F

Fe ature Access Codes (FACs)48, 56

H

Hunt Groups 11, 58

I

Incoming Trunk Calls S plitti ng (ITCS)27
Initialization 6, 26
Integrated Services Digital Network (ISDN)4

, 22, 47, 53,

58, 59

L

Logins 17, 32, 45, 47, 51
Lookahead Intraflow (LAI) 22

M

Maintenance 21, 54
Message Server 43
Multifrequency-Compelled (MFC) Calls23
Multifrequency-Compelled (MFC) Signaling23

N

Night Service 30

O

Outbound Call Management (OCM)33

P

Pr ocedure Errors 31

Q

QSIG 25
Queues 11, 35, 41

R

R2-Multifrequency-Compelled (MFC) Sig naling 24
Redial 46
Redirect on No Answer (RONA)11, 12, 18
Redirection 1, 4, 9, 12, 13, 31
Remote Access 3, 5, 29, 48

Return Call Timer 13
Routing 22, 31, 48, 49, 53

S

Se nd All Calls (SAC) 32
Service Observing 27, 29
Signaling 23, 24, 25, 40
Skills 16, 17, 51, 56
Splits 11, 16, 35
System Access Terminals (SATs)43, 54
System Capacity Forms 45
System Restarts/Resets 30, 44
System-Parameters OCM Call-Classification Form33

T

Terminal Translation Initialization (TTI)6, 7, 26, 34
Timers 13, 59
T N 767 Cir cuit P acks 37
T N 790 Cir cuit P acks 52
T N 798 Cir cuit P acks 52
T ones 1, 2, 31, 37, 40, 49
T ransfer 8, 24, 25, 27, 28, 38
Transfer Out of AUDIX 25, 57
Translations 7, 31, 32, 34, 60
Trunk Answer Any Station (TAAS)42
Trunks 1

, 4, 22, 24, 25, 29, 31, 37,

38, 40, 42, 44, 47, 49, 57

U

Upg rades 15, 60

V

VDN of Origin Announcement (VOA)14
VDN Overri de 18
Ve ctor Directory Numbers (VDNs)1 2, 18, 23
Vectors 8, 12, 14, 18, 20, 23
Voice Mail Integration (VMI) 39
VuStats 51

Issue 2 May 1998 7

Change Descriptions

The following prob lem s are corrected and addressed in DE F INIT Y Ent erprise
Communic at ions Server (ECS), Release 6, Issue 2.1 (02.1.125.1).

1. When an off-net coverag e or forwarded call could not find an av aila ble
trunk, bu sy tone was played back to the c alling party, effectively ending
the call. Now, the call is redirected back to the original principal whenever
possible.

2. A customer with a BRI terminal that is capable of seeing cause values saw

“Nor m al Call Clearing” when listening to any announcement or tone when
it timed out or c om pleted. Now, if that user is listening to reord er, busy or
Intercept tone and the tone times out, that user sees a cause value that
represents the reason for the tone, that is¨ “User Busy” or “Call Rejected.”

3. Assume that station A called station B, station B conferenced station C,
and station C c overed through DCS to a remote station D. After B
dropp e d, station C displayed its own name. Now, after station B drops , C
displays station A's name and station A displays station C' s name.

4. When a bridg e of the originating p arty dropped out of a call that had
routed off-net with call classification on a non-ISDN end-to-end trunk, the
call was torn down. Now, the call is not torn down, but call classification is
terminated, the cal l is left off-net, and it is not redi rected to subsequent
coverage.

5. Station A had a remote c ov erage p oint and the sta tion was forward ed to
station B. When a call was placed to station A when station B was ac tive,
the call did not go to the coverage point.

6. When TTI was turned on and a station was call forwarded, a user could
remove the call forward ed station and ad d a new station with the new
station be ing forwarded to the destination of the removed station.

7. Remo ving an EPN cabinet without first turning off TTI caused translation
corruption.

Change Descriptions

8 Issue 2 May 1998

8. Transferring into AUDIX when AUDIX was not explicitly in the coverage
path or if a vector was active failed on Intel machines.

9. If both Coverage of Calls Redirec t ed Off-Net and Answer Supervision by
Call Classification features were act ive on an off-net cal l, the call did not
further redirect to subsequent coverage points.

10. When BC MS was set to half-hourly reporting , and when the list bcms

<object> c ommand reported BCMS data, executing the list b c m s
<object> time <star t> <end > comman d sometimes caused the report to

show "no data in system to list.”

11. When an ACD agent was logged into multiple splits, and a call redirected
on no answer (an ACD call was ring i ng at the ag ent and the agent didn' t
answer so the call was requeued t o the hunt group ), sometimes not all of
the agent's aux-work mode buttons lit up, and the agent was still available
in some splits.

12. When try ing to redi rect a call on no answer to a VDN while processin g a
failed " converse on" vector step, the call went into limbo as call processing
tried to route call to the RONA VDN. Now, attempts to RONA a c all to a
VDN are blocked if the call is in vector p rocessing of a "converse on"
vector step. A new vec tor event is g enerated, "RONA to VDN in converse.

13. W hen an attendant extended a call to a principal with redirected off-net via
the CCRON feature, the call did not return to the attendant when the
Return C all timer expired.

14. When a station had optioned Active Ringing to silent-if-busy or
continuous and answered a call with VOA, the station continued to ring if
the call was answe red by pressing the cal l app e arance button.

15. Upg rades from G3V4 07.0.077 to R6 .2 could have inc orrect d efaults for
new R6 PPM fields on the DS1 form.

16. If a split or skill received more than 65,535 ACD calls in one day , the
number of ACD calls di splayed on the list bcms skill report rolled over
from 65,535 to 0, indicating that far fewer ACD c al ls had been rece ived
than was the actual case. Now, the list bcms skill report displays
accurately the number of ACD calls received, up to 99,999 calls, after
which p oint a string of "*****" indicates that the number of ACD calls
received exceed s 99, 999.

17. An EAS agent who logged in at a station that had a 2-line display with the
"user_de fi ne d" optio n adm inistered did not see the s k ill nu m be rs a nd
levels of the agent displayed correctly.

18. VDN Override rules regarding d isplays were not followed when a call
redirec ted on no answer. The first agent to receive the call had a correc t
display showing the dom inant VDN. However, subsequent agents who
received the same call did not have a d isplay showing the correct VDN.

19. “Extension in” calls to EAS agents were not reported by the monitor bcms
command.

Issue 2 May 1998 9

20. A goto time-of-day vector step allowed a combination of “all” with a

specific day.

21. The list configuration command did not display translated but uninserted
announcement boards properly.

22. LAI routing did not continue down the list of trunks in the route pattern
when it received a release complete message immediately following the
setup message, even if the correct cause value for LAI routing was
present.

23. Non-group II MFC calls did not term inate at VDN extensions correctly.

24. When a Conversant port transferred an incoming R2-MFC call to an
outgoing R2-MFC trunk blindly, the ANI that was received on the incoming
side was not sent out to the outgoing side.

25. Transferred calls Out of AUDIX over a QSIG trunk showed an inc orrect
disp lay.

26. TTI software corruption would cause problems with station administration,
resulting in error conditions.

27. A CDR rec ord was generated with the service ob serv er extension on a
blind transfer when ITCS was enabled. Now, the transfer-to party is output
in the CDR record if a transferred call is being observed.

28. AUDIX transfers did not complete when the number of outstandin g calls
was greater than 31. Now, AUDIX transfers complete when the number of
outstanding calls is 32. Also, for Intel machines, the maximum number of
AUDIX ports allowed is now 64.

29. A remote service observer using an AVD trunk could only observe in the
listen-talk mode. Now, the observer can also use the listen-only mode.

30. The reset system 2 c om ma nd caused the attend ant service mode to
toggle between day and night. Now, this c om m and causes the attendant
service mode to always be set to night.

31. A call to a principal that redirected off-net on an ARS routing pattern for
which no preferences (trunk groups) were assigned resulted in the calling
par t y hearing intercept tone while a p revious local c overage point could
be ringing. The calling party was unable to pi ck up the call . Now, the
calling party hears intercept tone, but all other parties are dropped from
the call.

32. A personal EAS (a call to an EAS login ID in which the calling and called
parties did not both have their COR Direct Agent Calling? option set to y)
that went to coverage due to the called agent's station having SAC active,
showed f rather than s for the call's reason code at the covered-to
station's display.

33. T her e was no way to administer dB adjustment for the Call Classifier. Now,
a new field, Global Classifier Adjustment (dB), on page 1 of the
system-param et ers ocm-call-classificat ion form allows for administration
of dB adjustment for the Call Classifier when using the OCM feature.

Change Descriptions

10 Issue 2 May 1998

34. Turning off TTI did not remove ports that were ad m inistered b y TTI on
cabinets that had been removed, causing translation corruption.

35. Automatic caller information was not displayed if the agent was not in the
first split that the call was que ued to.

36. DCS transparency was lost because DCS calls saved all proces sed
messag e buffers for the duration of the call, c ausing a shortage of DCS
messag e buffers in the switch. Now, the number of messages saved p er
DCS calls is limited so that more messages are available for other c alls,
thereby red ucing the c hances of running out of message buffers resulting
in a loss of DCS transparency.

37. Some voice calls on TN767 DS1 circui t pac k s were randomly c ons idered
as data calls, so data tone was connected on these calls and cut-through
trunk operation was not allowed.

38. CO-to-CO calls (DID calls that forwarded off-net or that were transferred
off-net) could have a transmission level that was too high. This caused
instability on these calls at some customer sites.

39. The Adjunct Supervision field did not work correc tly when it was set to a
VMI set type.

40. Using an abbreviated dialing button for end-to-end signaling was possible
only from the originating station or after a trunk flash when the c all
included a single trunk that was administered to support trunk flash. It did
not work from a terminating station under other circumstances. Now, a
terminating station can use an abbreviated dialing button to do end-to-end
sig naling on any fa cilitie s th a t can ge ne ra te the tones.

41. Pag e 5 of the disp lay cap acity form showed an incorrect system limit for
the queue-status buttons.

42. A trunk caller was blocked from picking up another trunk call using TAAS if
both trunks were in the same trunk g roup.

43. The message "Entry is bad" was disp layed on the SAT when executing a
clear-amw-all-extension command. Now, the message "Command
succ es s fully completed" is displ aye d if the clear-am w-all-ex tension
com ma nd is succ es sful. Otherwise, the message "Error encountered,
can’t complete request" i s displayed.

44. If there wer e about 200 or more long holding-time trunk calls in the system,
ACA caused a system restart.

45. The logged-in agent count in the d i splay-system-capacity form was
sometimes higher than the numb er of agents actually logged in. Now, the
count always reflects the ac tual number of agents log ged in.

46. When the "Display Authorization Code?" field was se t to n, using an
authorization code from a bridged appearance caused other bridged BRI
stations to lose these dial keypad functions: touch-tone feedback, local
dialed digit display, and retention for redial. Now, these functions are only

Issue 2 May 1998 11

disabled for the stations actually on a call requiring an authorization code,
and are reenabled when the dialing of the authorization code is completed
or abandoned.

47. When a call c ov ered from an EAS agent login ID extension to a station on
another DEFINITY ECS over an ISDN DCS+ trunk, the displa y at the
covered-to station showed the physic al station nam e (rather than the
agent’s login ID extension name) where the EAS agent was logged in.
Now, the d isplay correc tly shows the agent’s login ID extension name.

48. If a user forwarded a station to a remote number for which the length of the
number (including an ARS or AAR feature acc e ss code) was 16 digits,
and the number requ ired an interdigit timeout (typically, an international
number, for example, 88+011-44-719710089), the number was accepted.
But when a call was forwarded, the system waited indefinitely for the
end -of-dialing timeout or a pound sign (#). (Note that a pound sign is
stored with the number when the numb er of digits is less than 16.) Now,
Call Forwarding works c orrectly for any numb er of digits up to, and
including, 16. Call Forwarding cannot store more than 16 digits at present.

49. T he calling party on an incoming trunk call that was routed to coverage or
a forwarded-to des tination off-net d id not always hear ringback tone.

50. Some DCS calls were not transp arent (they had double burst ring i ng
instead of single burst ringing), meaning that they were treated as external
calls.

51. VuStats disp lays were not upd ated following an agent login or
add/remove skills ac t ion until the data displa ye d changed (the VuStats
lamp was on indicating that VuStats was active but the display showed the
age nt’ s skill se t rather than the VuSt ats display).

52. The list configuration comm and incorrectly displaye d circuit pack su ffix
higher than suffix A for the TN790 and TN798 circuit packs.

53. Calls that used ad junct routing t hat rec eived A AR analysis in which the
value in the Min field did not equal the value in the Max field on the AAR
Analysis form, could fail to route out.

54. The list mmi comma nd d isplayed the cab i net number of the b o ard
location to the SAT based on its por t network number. On the G3r, these
numbers are not always the same.

55. Users of BRI terminals had 127 as a cause value in cases in which a BRI
terminal was disco nnected. The value of 127 is cause unknown that is
really not true because the switch is aware of the Layer 1 status of a data
module. Users of a BRI terminal could see some feedback that was
somewhat ambiguous. Now, users of BRI terminals have 18 as the cause

value that maps to “No User Responding.” On the tested ter m inals "No
Answer" cam e up as the user feedb ack at a BRI data terminal. This value
is more aligned with the actually physical cause.

Change Descriptions

12 Issue 2 May 1998

56. Agents could not remove themselves from a skill (using the feature access
code for remove ag ent skill) without g oin g directly back to the auto-in
mode. Attempts to go into th e aux-work mode failed and went to the
auto-in mode instead.

57. Only the calling trunk inf o rmation was displa y ed at the call e d stat ion for
trunk calls transferred out of AUDIX. Now, the AUDIX port name, followed
immediately by the calling trunk information, is displayed.

58. Two simultaneous ISDN data calls to a hunt group of dat a endpoints
resulted in the second call not completing.

59. To inc rease the T.305 timer for the Nortel DMS COs, a new p rotocol
version for the US (country code 1) was created. This new protocol version

option is labeled as “c.” The new country code/protocol version is
automatically assigned a 30-second value to the T.305 timer.

60. Customers who had larg e sw i tch translations for upgr ades could
experience problems saving translations during and/or after the
upgrades.