Change Descriptions
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
10.When BCMS was set to
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
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.
13.When an attendant extended a call to a principal with redirected
14.When a station had optioned Active Ringing to
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.
17.An EAS agent who logged in at a station that had a
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.
19.“Extension in” calls to EAS agents were not reported by the monitor bcms command.
