Lucent Technologies DEFINITY Enterprise Communications Server Release 8, Issue 2.0 (02.0.034.2) Description Manual

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
17  
79. A TN767 could not be hot-swapped with a cost-reduced TN2313 circuit 
pack when trunks were administered.  “Conflict” would appear on the “list 
circuit-pack” display. Now, A TN767 with trunks can be hot-swapped with a 
TN2313, and vice versa.  The correct TN code displays on the “list 
circuit-pack” screen.
80. If more than 65,535 ACD calls were answered in any interval or day for a 
single VDN, the Basic Call Management System (BCMS) data was 
incorrect (i.e., off by 65,536). Now, the only limit is 99,999 imposed by the 
5-digit field size.
81. The system could reset if attendant directed calls on the branch switch 
route to the backup extension and are not answered for several minutes. 
82. If a user attempted to originate a call using an autodial button and the 
system was in an overload condition causing the call to be blocked, the 
digits translated for that button where cleared. Now, for this scenario, the 
digits translated for the autodial button are preserved. 
83. After an endpoint re-registered from another PC and was on a call, the call 
dropped if the user clicked ‘OK’ on the first PC after the call was established 
on the second PC.
84. With more than 256 announcements administered and a block of 
un-administered announcements within this range, a command of “display 
announcements” or “change announcements” resulted in the error 
message “Entry is bad”.  
85. When DEFINITY was connected to a public network via Signaling System 
7 (through a converter board), calls dropped four seconds after being 
answered if the SS7 network was heavily loaded.
86. If the customer had more than 255 best-service-routing application-location 
pairs administered, then vector processing would try to access the wrong 
data and calls could be routed to random locations. Now, it is safe for the 
customer to administer all 1000 application-location pairs.
87. Display Capacity did NOT show the correct accounting for Used, Available, 
and System Limit values for Recorded Announcement Analog Queue 
Slots.
88. The reply-best information carried by DISCONNECT message for Best 
Service Routing (BSR) polling calls overwrote the entire shared 
User-to-user information (UUI), including ASAI UUI, stored with the original 
call.
89. When merging or un-merging an IP Softphone, if an ACD or EAS agent 
was logged-in, the agent would become corrupted and not be able to do 
subsequent log-ins or log-outs. Now, when merging or un-merging a IP 
Softphone, any logged-in agent associated with the operation, is 
successfully logged-out.
90. The Status Station command did not consistently format group number and 
work mode pairs by separating them with a “slash” character. 
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
18  
91. If the name of the TN802B node was changed, the board did not reboot to 
take the new name.
92.The “did-view” button (hospitality only) allowed changing an automatically 
assigned DID number but it did not allow removal of the DID number.
93. Two-line display terminals did not display 27 characters names with 
extensions. Now, the display shows calling and called par ty names and 
extensions on both lines of the display.
94. Using the speakerphone to do a PSA associate of an extension to a digital 
station required the user to press the speakerphone button three times 
before getting connected to dialtone to make a call. 
95. Unplugging the CLAN cable did not drop active IP trunk calls.
96. The system-parameters coverage-forwarding form displayed a field titled 
“External Coverage Treatment for Transferred Incoming Calls?” The field  
title has been changed to “External Cvg Treatment for G3 Transferred Calls 
to G2 Suppor ting AUDIX?”.
97. When trying to remove an ethernet data-module, the error messages 
“Remove all IP routes that use the old node name as a gateway on its 
C-LAN” displayed. Now, the error message reads “Remove this ethernet’s 
dependent gateway on the ip-route form first”.
98. It was possible to remove an H.323 IP station even if it was administered as 
a Media Complex Ext of another Station. Now, the attempt is blocked with 
the error message “Cannot remove; extension assigned as Media Complex 
Ext of another station” 
99. Stations of type 515 had an IP SoftPhone? field. Now, IP SoftPhone? 
field does not appear for station type 515. 
100. After the system performed a system level 2 reset the night console could 
no longer receive night service calls.  
101. 8411D set could be administered as an IP Softphone even if it had a data 
option.
102. An R2-Multi-Frequency Code (MFC) call did not cover to the Vector 
Directory Number (VDN) extension correctly if an announcement extension 
was in the vector step.  
103. In-band Dual-Tone Multi-Frequency (DTMF) Automatic Number 
Identification (ANI) was lost after a converse step on the vector processing. 
104. In a telecommuter application call, if the IP Softphone voice path was 
through a trunk, when another party called the IP Softphone, the caller’s 
display showed the name of the trunk. Now, the caller’s display shows the 
name of the IP Softphone.  
105. When an incoming call was made to an IP solutions telecommuter 
application endpoint, both the softphone GUI and the associated telephone 
alerted. Both devices had to be answered to achieve a talk path.  
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
19  
106. IP softphones in telecommuter or road warrior mode did not hear VOA 
announcements.  
107. If an R6 or R7 system had TN2238 ATM boards translated, upgrading to a 
later release resulted in possible translation corruption. Now, only the 
TN2238 translation records are lost.
108. A problem in the Australian ISDN protocol caused incoming ISDN calls that 
redirected to a remote forwarding destination over an ISDN-Primary Rate 
Interface (PRI) facility to fail, apparently because of a PROGRESS 
message being automatically sent to cancel the T310 timer on the 
upstream switch. Now, PROGRESS messageare no longer sent 
automatically for remote forwarding/coverage calls.
109. Downloading of button information to the endpoint was inefficient. A more 
robust algorithm has been implemented, requiring the IP Softphone to be 
upgraded to version 0.97 or greater.
110. During duplication of a multimedia station, on the second page of the form, 
the title of the media complex was “MM data”. Now, the title is “Media 
Complex”.
111. The commands “status-station” and “status-trunk” failed with the error 
message “Port not assigned”, if one of the connected por ts belonged to a 
9600 series wireless station.
112. When a telecommuter application with a permanent service link 
unregistered, the service link remained connected.  
113. Auto callback only worked with an IP softphone if auto-call back was 
activated more than 10 seconds after the destination started to ring. 
114. Endpoints unregistered for some time were then no longer be able to 
re-register. A popup box stated that the IP address may be incorrect or the 
network may be congested.
115. Erroneous MAPD alarms appeared in the alarms log.
116. External unanswered calls to a night station were logged via the Log 
External Calls feature (External LWC). Now, external unanswered calls to a 
night station are NOT logged.
117. External calls that covered to a Remote AUDIX were not logged via the Log 
External Calls feature (External LWC). Now, external calls that cover to a 
Remote AUDIX ARE logged.
118. If duplicate IP routes were administered, when the “extra” route was 
removed, the sessions that were dependent on that route might not come 
into service or might be dropped.
119. An IP Softphone or IP agent never heard a ZIP tone when receiving an 
incoming call.
120. If a user answered a call by pressing a busy indicator button, and then 
originated a new call from another line appearance without going on hook, 
the user did not get a dial tone but instead placed a call to the station of the 
busy indicator.  
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
20  
121. If an endpoint and DEFINITY did not have matching codecs, a road warrior 
application call would hang for 15 seconds without a talk path, and then 
drop. Now, the call drops immediately. 
122. When all circular hunt group members were busy, the next hunt group call 
caused a system reset. 
123. It was previously possible to administer a TN802 as TN802B, even if the 
board suffix was not B or later for TN802. Now, it is no longer possible. 
124. TN802/TN802B reserved slots were not being blanked out when the 
TN802/TN802B board slot was administered. 
125. Bellcore Facility messages containing calling name were not tandemed 
correctly, if the incoming trunk group had the “delayed display update” field 
set to “n(o)”. Now, Bellcore Facility messages containing calling name are 
tandemed regardless of the delayed display update field on the incoming 
trunk group.
126. In France, running “test board” on a TN2185 resulted in the BRI trunks 
going out of service/near end.  
127. In France, performing a busy/release of a TN2185 BRI trunk did not bring 
the trunk back into service (non-stable layer 1).
128. When a call covered to a final CCRON point, and the “Activate Answer 
Detection on Final CCRON Cvg Point” field on the System 
Coverage/Forwarding form was set to ‘n’, and the call was redirected over 
an ISDN facility that became interworked, then when the call was answered 
there might not be a talk path.
129. It was possible to administer a TN802/TN802B board in a slot even if the 
two slots before it were not empty. Now, this is no longer possible, and the 
attempt generates an error message.
130. When Best-Service-Routing attempted to poll over a BRI network that was 
down, the DEFINITY switch tried to bring up the network, but the 
Best-Service-Routing software became confused.  Instead of waiting for 
the BRI to come up, it erroneously attempted to interflow the call (rather 
than just polling).  The end result was that the caller was dropped from 
vector processing, heard a busy tone, and the call was lost.  This is a 
common problem in some networks where the BRI layers are brought down 
when the last call on the interface clears.
131. The title “Enabled” on the IP-interfaces form was confusing, because it did 
not apply to all the links on the board, only to Ethernet links. Now, the title 
has been changed to “Enabled Ethrnt” 
132. When connectivity was lost to the packet bus from the NETPKT (TN794), 
no error was raised. 
133. A bridged station’s display truncated the last digit or two from the calling 
party number of an incoming call.   
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
21  
134.International customers had no ability to change the handling of the “star” 
and “pound” digits by the “collect” vector step, so that the use of these 
digits to indicate “clear all collected digits” and “end-of-dialing” could be 
reversed.  Some international mobile phone systems require this reversal, 
since their phone user normally enters a “star” to indicate “end-of-dialing” 
to immediately dial an entered number.  
Now, the addition of the “Collect Step Star/Pound Reversal?” y/n field on 
page 8 of the “SystemParameters - Features” form allows any DEFINITY 
customer (domestic or international) to reverse the handling of the “star” 
and “pound” digits by the “collect” vector step for DEFINITY R8.2 (and 
later) releases.
135. If calls to an attendant in night service were directed to a remote Voice Mail 
hunt group with QSIG-NWI signaling, and all the QSIG trunks were either 
busy or out-of-service, then the system would reset. Now, the caller will 
hear a busy tone and the system does not reset.
136. ATM-NTWK alarms could persist indefinitely after all problems were 
resolved. Now, ATM-NTWK alarms are cleared when all problems causing 
them are resolved.
137. On certain transferred calls that went to a CCRON destination, the call 
failed to redirect to a subsequent coverage point. Now, those transferred 
calls sequence through all coverage points.
138. CMS pump-up aborted if it encountered a corrupted VDN translation.
139. There was no way to know how many ACD agents were logged into IP 
Softphones. Now, there is a count on the “display capacities” form.
140. Executing a system-reset-1 command with multiple active Automatic Call 
Back (ACB) buttons could cause another system reset under rare 
circumstances, which could escalate to a cold1. Now, executing a 
system-reset-1 will not cause another system reset. 
141. H.323 IP signalling groups could get into a “hung” state, if a warmstart 
occurred at the same time that a Transmission Control Protocol (TCP) 
connection for Q.931 signaling was failing (timing out).  In such a “hung” 
state, the signalling group was unusable for incoming or outgoing calls. 
Now, if such a race condition occurs, it is cleaned up.
142. The customer was infrequently unable to break dial tone when using 
whisper page in an ATM PNC multiport network environment.
143. The user received an error message when attempting to remove a 
Computer Telepphony Interface (CTI) station after turning off TTI. This no 
longer occurs.
144. External unanswered calls to local coverage points were not logged via the 
Log External Calls feature.  
145. If monitor BCMS split X for 7 pages of agents was followed by monitor 
BCMS split Y for 6 pages of agents, via the Operations Support Systems 
Interface (OSSI), some of the agent data would be lost. Now, all agent data 
is relayed to OSSI in this case. 
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
22  
146. Under certain circumstances, incoming DS1 trunk calls provided priority 
ringing, instead of following the coverage path.
147. Sometimes the TN802B board would not come up in the correct state 
without several reboots. Now, the TN802B application is run after as little 
as 2 reboots of the board.
148. When an incoming DID call into switch A tandemed over a Distributed 
Communications System (DCS) tie trunk to a station on switch B that 
forwarded to a local station that did not answer, the call was subsequently 
blocked from covering offnet.
149. When changing a hunt group from non-AAS to AAS (Auto-Available 
station), an incorrect error message, “Cannot add because maximum 
number of agents already logged-in”, displayed.
150. If an internal measured trunk was conferenced with an external measured 
trunk and then the external measured trunk dropped out of the call, CMS 
aborted tracking the call.  
151. If a member of a Personal Central Office Line (PCOL) group originated a 
PCOL call coincident with an incoming call on the PCOL trunk, 
occasionally the PCOL button on the station would lockup. 
152. H.323 IP resources occasionally took 15 minutes to come into service. 
Now, they come into service when the board has been initialized 
successfully.
153. An extension on a DCP set could not receive calls after PSA from a 
registered endpoint until a call was originated from the DCP set.  
154. When running “save trans rem” without the removable media in the 
removable media drive, the error message “MSS device is out of service” 
displayed. Now, the following error message displays:
“No removable media in removable media drive” 
155. For attendant extended trunk calls, caller id terminals received the 
attendant name and number. Now, they receive the trunk calling party 
information if available or the TAC and the trunk name. 
156. When the switch transmitted VDN translations to CMS, the BSR plan 
number was incorrect or missing.  
157. Using the “release” button to exit Abbreviated Dial programming may cause 
subsequent calls not to send Touch Tone digits. Now, using a “release” 
button to exit Abbreviated Dial programming is not allowed.
158. It was possible to disable and change an IP-interface in one step. Now, you 
have to disable an IP-interface, submit the form, bring up the form again, 
and make any changes needed. 
159. For DWBS stations, the field “mobility trunk group” in the station form 
defaults to 1 and blanks are allowed. Now, the field defaults to a blank and 
is a required non-blank field. This is necessary to guarantee correct 
administration of the “mobility trunk group” for use in registration.  The 
former default of 1 was usually incorrect and needed to be changed. 
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
23  
160. Calls routed over an ISDN trunk using Extended Trunk Access (ETA) was 
not considered when checking the numbering format field of the route 
patttern.  
161.The command “list usage button crss-alrt” showed only stations that had a 
crisis alert button administered. Now, the command shows all administered 
crisis alert buttons in the system, both stations and attendants.
162. If a processor channel was disabled, the “last failure” field of the “status 
processor-channel” form printed “none”. Now, the field shows “Processor 
channel disabled”.
163. When attempting to administer a Caller ID set type as an analog bridge, the 
user received the error message, “extension must bridge onto an analog 
station”. Now, the error message does not display, and this administration 
is allowed.
164. It is now possible to use two terminals with customized format; maximum 
number of digits has been increased 23; condition code T added for calls 
that tandem thru DEFINITY with no billing.
165. An H.323 IP extension registered as a Native H.323 that was also the 
media complex extension for a DCP extension was not allowed to make 
calls. Now, the H.323 IP extension is denied registration.
166. Certain ASAI adjunct applications became non-functional when the reset 
shift call feature was used. 
167. If a user whisper-paged on another call and then disconnected, the paged 
user’s display failed to update to the original display.
168. When an IP Softphone logged into the switch, the command “status 
station” failed to show the right far end port of the IP Softphone.  
169. No warning message displayed when disabling an IP-interface on the 
IP-interfaces form. Now, the message “WARNING: Disabling an 
IP-interface will cause interruption in service” displays.
170. Adding and removing busy indicators using either the feature access codes 
or feature buttons could cause a system reset.
171. Best Service Routing over H.323 IP trunks was not working. 
172. After an upgrade, the TN802B port remained in an out-of-service state. 
Now, the TN802B port is in service if no alarms are present.
173. A node name used on the IP-interface form could also be defined on the 
data module form ppp. Now, cross validation is performed between the 
IP-interface and the data module form. If there are duplicate node names 
on these forms, the following error message displays: 
“Node Name currently assigned to  another interface or link”
174. For certain types of calls, Incoming Call Line IDentification (ICLID) did not 
display on caller id terminals. Now, for all calls, ICLID displays on 
BELLCORE compliant caller id terminals. 
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
24  
175. If one of two or more TN802B boards in a system is disabled, it would 
remain out-of-service when re-enabled due to an incorrect alarm state.
176.The ‘list trace ewt’ command did not properly display data for columns 
Agents Working (AgtWk) and Agents Available (AgtAv).
177. When using the ‘list trace vdn’ command to trace a VDN/vector, which does 
a ‘reply-best’ step, the value for skill-level was decremented by 1. 
178. A station with any of the following buttons could not be duplicated:
cpn-blk 
cpn-unblk
mm-basic
mm-call
mm-datacnf
mm-multnbr
mm-pcaudio
179. A call routed to the attendant via a vectoring route-to step would not queue 
if the attendant was busy. Now, the call is queued and remains in queue 
until the attendant is idle.
180. If the attendant selected a hundreds group button with a four digit value, 
the system would reset. 
181. DWBS Global did not support music on hold if the DWBS station flashed to 
place a call on soft hold. Now, DWBS Global supports music on hold for 
soft held calls due to a flash.
182. Under certain circumstances, moving agents from one split to another 
using the move agent feature caused a system reset.  
183. The BCMS interval was corrupted if a system reset 3 was executed in the 
second half hour of an hour.  
184. Unanswered transferred calls redirected to the attendant failed to provide 
audible alerting at the attendant console.  
185. A service observed call with an invisible single-step-conference station did 
not drop, even when there was only one regular station left in the call.
186. Calls to trunk groups controlled by the attendant were not redirected to 
attendant vectoring.  
187. The message waiting icon did not display when a DWBS WT or a DWBS 
station reentered the system, after having received a message via LWC or 
AUDIX, while the set was out of the system. Now, the message waiting icon 
displays and clears correctly if LWC activity occurs while the set moves out 
of the system. 
188. The feature “cvg of calls redirected off-net” on the customer options form 
was not available to offer B customers. Now, it is now available to both offer 
A and B customers. 
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
25  
189.The ”Port Not Fnd” message is returned when doing a traceroute 
command to a CLAN board and a port was specified, but a bad location 
was used.
190. Attempting to add duplicate IP routes on a C-LAN board is now blocked.
191. The “Route Type” field on the ‘add ip-route’ form was administrable. Now, 
that field is not administrable.  The route type is determined automatically 
by the subnet mask and the class of the destination’s IP address.
192. The “list mct-history” command truncated the last character that specified 
the recorder port used. 
193. An administrator was blocked from changing or removing a station or 
attendant console with an active timer button. Now, after a warning 
message is displayed, on first entry, the second entry is successful.
194. If the field “roundtrip Propagation Delay (ms) low:” was set to “10” on the 
system parameter maintenance form, the PBX never came out of the 
“by-pass” mode.
195. The “list multi-media ip-softphones” command did not display ports. Now, 
each port of each station displays. 
196. On the “list measurements ip-sig-grp” form, the average latency was 
sometimes calculated incorrectly.  
197. Unpluging a DCP set usable as an IP Softphone, and then registering an IP 
Softphone using the same extension of the DCP set caused the IP 
Softphone to disconnect.
198. Busying an active H.323 IP trunk placed the trunks in an incorrect state, 
and the command “status trunk tkgrp/#” received the error message “Entry 
is bad”.
199. If the last member of a circular hunt group is busy on a call and there are 
free members in the group, a new call received a busy tone. Now, a new 
call is routed to the first free member of the group. When all members are 
busy, then the call receives busy treatment, if no redirection is activated for 
the hunt group.
200. The display for incoming redirected calls in international format (i.e., no 
dashes in the number) had no blank spaces between the number and the 
word “to”. There is now at least one space between the number and the 
word “to”.
201. The number 1719 formerly could not be entered in the field signaling group 
near-end listen por t.  Now, the field allows 1719,1720, and 5000-9999. 
202. The SYSAM Test #913 was changed from a MAJOR to a MINOR alarm. 
203. Using TTI to associate an extension, already assigned a port to a second 
port, locked up the second por t. Now, the user is blocked from associating 
extensions with hardware using TTI. 
204. After a switch upgrade, the TN802B por ts were taking 15 minutes or longer 
to go into service. 
						

							DEFINITY Enterprise Communication Server Release 8, Issue 2.0 (02.0.034.2) 
Change Description  555-233-411  Issue 1
April 2000
Change Descriptions 
26  
205. PASTE data has been changed to include some missing Feature Access 
Codes (FACs) and button types for the Centre Vu (CV) Agent PC phone 
application.
206. Authorization codes of length 7 or less were not output in the Call Detail 
Recording & Reporting (CDR) repor t. 
207. The default settings in the system-parameters maintenance form, page 3, 
were incompatible with the settings required for the US Robotics Sportster 
external modem that was being shipped with csi systems. 
208.A “list multimedia ip-softphone” command could result in an “Error 
Encountered, Cannot Complete Request” (EECCR) message. 
209. When a large number of VDN notifications were aborted at one time, switch 
performance was degraded.
210. Calls over BRI trunks often failed in countries outside the USA.
211. Attempting to execute an add/change/display/remove test-schedule 
command with an invalid test-schedule number could result in an “Error 
encountered, cannot complete request” message.  Now, invalid numbers 
result in an “Identifier invalid” error.
212. If a voice mail system did DCP port emulation (i.e. Octel), digits signaled 
out of band, such as AD buttons, or hybrid sets, would not be deleted by 
the voice mail system. 
213. Digital Signal Level 1C (DS1C) remote EPNs could reuse a fiber slot before 
all elements of the center stage had released the fiber slot, resulting in 
incorrect connections.
214. You will get an error message if you try to administer an H.323 IP signaling 
group on por t 1719/1720, and there is already a signaling group on 
1720/1719, respectively.
215. A non-vector, non-ISDN, call to a hunt group with a forced first 
announcement could cause the switch to reset. 
216. It was possible to have enabled both “LRQ Required?” and “Calls share IP 
Signaling connection?” fields on the Signaling group form for H.323 IP 
signaling groups. Now, an error message is displayed.
217. With LookAhead Interflow (LAI) administered, calls routed to Audix via the 
audit, resulting in the loss of DCS transparency. 
218. The feature “Extended Cvg/Fwd Admin” on the customer options form was 
not available to offer B customers. It is now available to both offer A and B 
customers. 
219. IP-interfaces that had a data module associated with them could not be 
changed without first removing the data module.
220. Executing a “download translation” on G3r ONLY did not ensure that a 
subsequent “reset sys 3” or higher on the G3r would boot from the 
translations just downloaded.