Lucent Technologies 108286063 User Manual
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 Redirected Off-Net and Answer Supervision by
Call Classification features were active on an off-net call, the call did not
further redirect to subsequent coverage points.
further redirect to subsequent coverage points.
10. When BCMS was set to half-hourly reporting, and when the list bcms
<object> command reported BCMS data, executing the list bcms
<object> time <start> <end> command sometimes caused the report to
show "no data in system to list.”
<object> time <start> <end> command 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 ringing at the agent and the agent didn't
answer so the call was requeued to 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.
answer so the call was requeued to 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 trying to redirect a call on no answer to a VDN while processing 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 call to a
VDN are blocked if the call is in vector processing of a "converse on"
vector step. A new vector event is generated, "RONA to VDN in converse.
tried to route call to the RONA VDN. Now, attempts to RONA a call to a
VDN are blocked if the call is in vector processing of a "converse on"
vector step. A new vector event is generated, "RONA to VDN in converse.
13. When 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 Call timer expired.
Return Call 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 answered by pressing the call appearance button.
the call was answered by pressing the call appearance button.
15. Upgrades from G3V4 07.0.077 to R6.2 could have incorrect defaults 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 displayed on the list bcms skill report rolled over
from 65,535 to 0, indicating that far fewer ACD calls had been received
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 point a string of "*****" indicates that the number of ACD calls
received exceeds 99,999.
from 65,535 to 0, indicating that far fewer ACD calls had been received
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 point a string of "*****" indicates that the number of ACD calls
received exceeds 99,999.
17. An EAS agent who logged in at a station that had a 2-line display with the
"user_defined" option administered did not see the skill numbers and
levels of the agent displayed correctly.
levels of the agent displayed correctly.
18. VDN Override rules regarding displays were not followed when a call
redirected on no answer. The first agent to receive the call had a correct
display showing the dominant VDN. However, subsequent agents who
received the same call did not have a display showing the correct VDN.
display showing the dominant VDN. However, subsequent agents who
received the same call did not have a display showing the correct VDN.
19. “Extension in” calls to EAS agents were not reported by the monitor bcms
command.