Lucent Technologies 03.0.042.2 - Manual (Page 12)

Change Descriptions
10 Release 8, Issue 3.0 (03.0.042.2)
55. When Cyclical Redundancy Check (CRC) errors occurred on BRI ports, the
ports were taken out of service and never put back into service.
56. It was not possible to change an ISDN trunk group to a non-ISDN trunk
group if there were many AAR/ARS patterns used in the system.
57. Some incoming trunk calls to the attendant incorrectly displayed “CALL
FROM ...” instead of the trunk group name.
58. The Route Type field appeared but was not administrable on the ip-route
form for the display, change, remove, and list functions.
59. An off-net coverage call could be answered by two different coverage
points, and all parties could be conferenced on the call. Only one coverage
point may now be on a coverage call.
60. If a QSIG diversion-rerouted call terminated to a station at the origination
PBX because of Call Forward - No Reply (CFNR), and the station was
busy, the original call at the forwarding station was dropped. The original
call to the forwarding station will now continue to ring at the forwarding
station.
61. The "list-trace station/tac" commands did not output MFC call-specific
information.
62. It was not possible to make or receive Roadwarrior calls if the system had
administered the maximum number of IP station and H.323 IP station.
63. When quickly transferring a call which was being service-observed to an
agent with auto-answer, and the agent was in a different port network
which was being observed by a different observer, both observers
remained on the call after the transfer had been completed. The second
service observer is now dropped from the call when the transfer is
completed.
64. When an incoming Direct Inward Dialing (DID) call was forwarded across a
Distributed Communications System (DCS) trunk, it would lose information
concerning its path.
65. Feature interactions between the group paging feature and certain traffic
measurements caused system traps and potentially system resets.
66. ISDN calls that were held or transferred were sometimes dropped by older
U.S. Central Office equipment because of a NOTIFY message that
DEFINITY sent to the network.
67. A transferred conference call did not invoke Enhanced Network Call
Transfer (ENCT) when the conferenced user dropped.
68. It was possible for a user to transfer an unstable (e.g. ringing) call to a
group page, thereby causing the group page to lockup in a busy state.
69. Trunk Access Code (TAC) calls that originated with measured ACD agents
reported digits to Call Management System (CMS)/Management
Information System (MIS) only if the digit timeout occurred before the call
was answered.