Call dropped. Call not queued at stop step

Vector processing ended without the call being queued to a split and, as a result, the call cannot be answered. This implies that some default condition was not programmed or that the vector was designed to not always answer the call. Also, call was subsequently dropped.

High short is a vector number

Low short is a step number

Call ID

Vector with no steps

The call encountered a vector with no steps administered.

High short is a vector number

Low short is a step number

Call ID

10,000 step executed

This can occur due to the following:

• Incorrect vector programming, for example, including a series of goto steps that point to one another.
• Excessive repetition of a programmed loop during a single call. Fr example, recurring announcement-wait loop.

High short is a vector number

Low short is a step number

Call ID

Administration change

High short is a vector number

Low short is a step number

Call ID

Call dropped by vector disconnect timer

The call was still in vector processing when the vector disconnect timer expired. The call dropped.

High short is a vector number

Low short is a step number

Call ID

Attd Vec Mismatch-VDN/Vec

There is a mismatch between Attendant Vectoring and Call Vectoring between the VDN and the vector.

Attd Vec Mismatch-CR/Vec

There is a mismatch between Attendant Vectoring and Call Vectoring between the incoming call and the vector.

Retrying announcement

During an announcement step, a collect digits step that contains an announcement, or a disconnect step, the announcement was not available, and the announcement queue was full. The step is retried at regular intervals.

High short is a vector number

Low short is a step number

Call ID

No announcement available

During an announcement step, a collect digits step that contains an announcement, or a disconnect step, the announcement was not available for one of the following reasons:

High short is a vector number

Low short is a step number

Call ID

Call cannot be queued

A queue-to split, messaging split, or check split command failed to queue the call.

High short is a vector number

Low short is a step number

Call ID

Queued to three splits

The call attempted to queue to four splits. Multiple split queuing allows the call to queue to a maximum of three splits simultaneously. If the call queued to more than one splits and if the call must now be dequeued from the splits and then queued elsewhere, one solution is to route the call to a station, which can be administered without hardware. Once this happens, the call is forwarded to the VDN that controls the next stage of the call.

High short is a vector number

Low short is a step number

Call ID

Attd Vec: Cannot requeue

Applies to Attendant Vectoring and indicates that the call is in the attendant queue and another attempt is made to queue the call to an attendant or hunt group, or the call is in the hunt group queue and an attempt is made to queue the call to an attendant or too many attempts are made at queuing to the hunt group.

High short is a vector number

Low short is a step number

Call ID

No TTR available

A collect digits command failed because:

• TN744 port is not available.
• All queue slots are occupied.

High short is a vector number

Low short is a step number

Call ID

Dial-ahead discarded

Previously entered dial-ahead digits are discarded using access of an adjunct routing link, converse-on, route-to number, or messaging split step.

High short is a vector number

Low short is a step number

Call ID

Prompting buffer overflow

The prompting digit buffer already has the maximum of 24 digits when additional dial-ahead digits are entered by the caller. The additional digits are not stored.

High short is a vector number

Low short is a step number

Call ID

ced digits left behind

A collect ced digits step collected digits from a UEC IE and more than 16 digits are sent from the network.

High short is a vector number

Low short is a step number

Call ID

cdpd digits left behind

A collect cdpd digits step collected digits from a UEC IE and more than 16 digits are sent from the network.

High short is a vector number

Low short is a step number

Call ID

ced digits not available

A collect ced digits step collected digits from a UEC IE and no digits are sent from the network, or no digits are present in the UEC IE.

High short is a vector number

Low short is a step number

Call ID

cdpd digits not available

A collect cdpd digits step collected digits from a UEC IE and no digits are sent from the network, or no digits are present in the UEC IE.

High short is a vector number

Low short is a step number

Call ID

collect digits for variable error

• Failed to put the local variable value in the local linked list of collect variables for the call. This implies that the system variable limit is reached.
• Failed to put the global variable value in the Variables for Vectors table due to messaging issue with Communication Manager.
• Unknown or invalid variable type defined in the collect vector step.

High short is a vector number

Low short is a step number

Call ID

Variable not defined

High short is a vector number

Low short is a step number

Call ID

Invalid table number

A variable used as a table entry has an invalid assignment.

High short is a vector number

Low short is a step number

Call ID

Messaging step failed

A messaging step failed because the Messaging Adjunct is not available.

High short is a vector number

Low short is a step number

Call ID

Messaging ext invalid

The messaging extension contains a variable with an invalid value of none or #. Vector event 38 is also generated.

High short is a vector number

Low short is a step number

Call ID

Route -to step failed

A route-to step failed to reach the intended destination.

High short is a vector number

Low short is a step number

Call ID

No digits to route-to

The route-to digits step is unable to route the call because the previous collect digits step failed to collect any digits. This can result from an error in vector programming, for example, a route-to digits step appears without a preceding collect digits step. More often, however, this results because the caller is unable to enter the required digits, that is, the caller is using a rotary telephone, or because the caller is not provided with enough information to do so, as can be the case for auto-attendant applications.

High short is a vector number

Low short is a step number

Call ID

No available trunks

A route-to command is unable to reach the specified off-switch destination due to a lack of available trunks.

High short is a vector number

Low short is a step number

Call ID

Route-to step failed

The step is unable to seize a trunk because of a hardware problem or glare.

High short is a vector number

Low short is a step number

Call ID

LAI retry

Look Ahead Interflow route-to step failed because of glare. The route is retried once.

High short is a vector number

Low short is a step number

Call ID

Double coverage attempt

Coverage option on route-to step is ignored because double coverage is not allowed. This can happen when the call has covered to a VDN.

High short is a vector number

Low short is a step number

Call ID

Call not in queue

Route to step with interflow-qpos condition not executed because call was not queued at a split.

High short is a vector number

Low short is a step number

Call ID

Deny vector-initiated MSO

The vector cannot add an observer because SRVOBS_MAX=2 is reached.

High short is a vector number

Low short is a step number

Call ID

Deny observing observer

The vector cannot observe the agent because the vector is already an observer.

High short is a vector number

Low short is a step number

Call ID

Variable invalid value

The adjunct route link ID for GAZ (1-8) or MIPSLX (1-64) is invalid.

High short is a vector number

Low short is a step number

Call ID

Adjunct route failed

An adjunct route failed for one of reasons indicated in event types 61 through 66.

High short is a vector number

Low short is a step number

Call ID

Invalid destination

The adjunct routing link command returned digits that do not represent a valid destination.

High short is a vector number

Low short is a step number

Call ID

Adjunct route cancelled

The adjunct routing link step is cancelled because another routing step such as a queue-to split step, is encountered in the vector.

High short is a vector number

Low short is a step number

Call ID

Queue before route

The adjunct routing link command is skipped because the call has already queued using a queue-to split or a check split command.

High short is a vector number

Low short is a step number

Call ID

Adjunct link error

The adjunct routing link command is cancelled due to the following reasons:

• Link to the adjunct is down.
• ASAI protocol violation prevents call completion.
• Software resources to complete the call are unavailable.

High short is a vector number

Low short is a step number

Call ID

Software resources to complete the call are unavailable.

A direct agent call is made to an agent who is not logged in to the relevant split. Used for adjunct routing request only.

High short is a vector number

Low short is a step number

Call ID

Agent not member of split

A direct agent call is made to an agent who is not a member of the relevant split. Used for adjunct routing request only.

High short is a vector number

Low short is a step number

Call ID

Invalid direct agent

A direct agent call is made to an invalid agent extension. Used for adjunct routing request only.

High short is a vector number

Low short is a step number

Call ID

Adj route via NCR failed

NCR routing failed and a tandem trunk-to-trunk routing cannot be done.

High short is a vector number

Low short is a step number

Call ID

Adj rte fail-link not adm

The adjunct CTI route link ID is within range but not administered.

High short is a vector number

Low short is a step number

Call ID

Busy step for CO trunk

A CO trunk call reaches a busy step in a vector without having previously received answer supervision. As a result, the caller continues to hear ringback rather than the busy tone.

High short is a vector number

Low short is a step number

Call ID

Time not set

A goto step with a time-of-day conditional is processed, but the Communication Managertime is not set.

High short is a vector number

Low short is a step number

Call ID

No digits collected

No digits are collected and a comparison is requested against a digit string or in-table. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

The holiday table empty

The holiday table is empty

Vector Number, Step Number

Service-hours table empty

The service-hours table is empty. The table must be administered.

High short is a vector number

Low short is a step number

Wait step music failed

A wait-time step with music is accessed, but music is not connected. Check if music is administered correctly.

High short is a vector number

Low short is a step number

Call ID

Wait step ringback failed

A wait-time step with ringback is accessed, but ringback is not connected.

High short is a vector number

Low short is a step number

Call ID

Redirect unanswered call

The call is sent to an agent using a vector, but due to RONA, the call is redirected.

High short is a vector number

Low short is a step number

Call ID

Redirect of call failed

The call is sent to an agent using a vector, but due to RONA, the call was redirected. The call is not be redirected.

High short is a vector number

Low short is a step number

Call ID

Converse no ANI digits

On a converse-on step with passing type ani, no information is available to populate the field.

High short is a vector number

Low short is a step number

Call ID

Converse no qpos digits

On a converse-on step with passing type qpos, no information is available to populate the field.

High short is a vector number

Low short is a step number

Call ID

Converse no prompt digits

On a converse-on step with passing type digits, no information is available to populate the field.

High short is a vector number

Low short is a step number

Call ID

Converse drop during data

On a converse-on step, the converse agent hangs up while data is being passed. This can indicate a port failure.

High short is a vector number

Low short is a step number

Call ID

SA8835 Conference to VDN failed

SA8835 Conference to VDN failed due to not meeting vector step or ASAI monitor/control rules.

High short is a vector number

Low short is a step number

Call ID

ASAI transfer converse

ASAI attempts transfer of a call that is active at a converse step. The transfer fails and vector processing continues at the next vector step.

High short is a vector number

Low short is a step number

Call ID

Converse transfer denied

Transfer of a call that is active at a converse-on step is attempted. The transfer either fails or is denied, and vector processing continues at the next vector step.

High short is a vector number

Low short is a step number

Call ID

Agent drops converse

While active on a converse-on step, an agent became available in a split associated with a queue-to split or check split step. The call is delivered to the non-converse agent and the converse agent is dropped.

High short is a vector number

Low short is a step number

Call ID

Cannot RONA to VDN during converse

Already in a vector processing in converse step, do not allow RONA to VDN. If you want to go to another VDN, then you should write your vector to goto vector when the converse step fails rather than use RONA in the converse hunt group.

High short is a vector number

Low short is a step number

Call ID

Data return no digits

On a converse-on step, the converse agent activated data return but did not return any digits.

High short is a vector number

Low short is a step number

Call ID

Data return time-out

On a converse-on step, the converse agent activated data return but timed out while waiting to return digits. Vector processing continued at the next vector step.

High short is a vector number

Low short is a step number

Call ID

Coverage conference denied

Coverage to a VDN in a coverage path is denied because more than one party is active on the call.

High short is vector number provided by dial plan

Low short is 0

Invalid EAS hunt group used in the vector step

Either the skill hunt group is removed or is a non-ACD hunt group.

High short is a vector number

Low short is a step number

Call ID

Skill indirection used improperly

Either no VDN skills are administered or the vector command has skill indirection and EAS is not enabled.

High short is a vector number

Low short is a step number

Active VDN extension

No vector steps, ANI sent

ANI is sent to CMS for a call that reached a VDN that accessed a vector with no steps defined.

High short is a vector number

Low short is a step number

Call ID

uui sent to CMS, but there were no steps in the vector

A call is directed to a VDN associated with a vector that has no steps.

High short is a vector number

Low short is a step number

Call ID

ASA - invalid VDN

A check or goto test requested a comparison of ASA for a VDN that has been removed since the vector was programmed. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

ANI not avail - digits

A goto test requested a comparison of ANI against a digit string and ANI is not available for the call. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

Routing table not assigned

A goto test requested a comparison with a vector routing table that is not assigned or is removed since the vector was programmed. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

No entries in routing table

A goto test requested a comparison with a vector routing table that has no entries. This is a non-match.

High short is a vector number

Low short is a step number

Call ID

ANI not avail - table

A goto test requested a comparison of ANI against in-table and ANI is not available for the call. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

No digits in variable

In-table is administered, but the variable does not contain any digits on which to search.

High short is a vector number

Low short is a step number

Call ID

EWT call not queued

A goto test for a call or converse data passing requested EWT for a call not in queue. In this case, the wait time is treated as infinite and the comparison is based on EWT > largest possible threshold.

High short is a vector number

Low short is a step number

Call ID

EWT not sent to VRU

The EWT wait time for the call is not sent to the VRU for a converse-on passing wait vector step because the call is not queued or the splits/skills that the call is queued to is unstaffed.

High short is a vector number

Low short is a step number

Call ID

System clock change

The system clock has changed, therefore any calculations involving time, that is, ASA and EWT is inaccurate.

0

0

II-digits not avail - digits

A goto test requested a comparison of II-digits against a digit string and II-digits are not available for the call. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

II-digits not avail - table

A goto test requested a comparison if II-digits against in-table and II-digits are not available for the call. The comparison test is false and the next step in the vector is executed.

High short is a vector number

Low short is a step number

Call ID

Call is not incoming ISDN

Occurs when a reply-best command in a status poll vector receives and tries to process a non-ISDN call. Processing in the status poll vector terminated is without a reply being sent.

High short is a vector number

Low short is a step number

Call ID

No best location found

A queue-to best, check-best, or reply-best command fails because the call vector is unable to calculate a best value or because no local best exists. Vector processing continues at the next step. Vectors in multisite BSR applications do not attempt to interflow calls.

LAI attempt failed

Interflow of the call fails since: no trunk was available, LAI denial, or some other problem. Vector processing continues at the next step. In BSR applications, polling of this resource is temporarily suppressed.

No BSR app num in VDN

A queue-to best, check-best, or consider location command fails because the active VDN for the call as determined by VDN override has no BSR application number assigned. Processing continues with the next vector step. Only occurs in multisite BSR applications.

No BSR application plan administered

A queue-to best, check best, or consider location command fails because the application number assigned to the active VDN does not have an application plan assigned. Processing continues at the next step.

Location not on BSR screen

A consider command fails because the command refers to a location number that is not in the BSR Application screen assigned to the active VDN. Vector processing continues at the next step.

Status Poll VDN field is blank

A consider command fails because the entry for this location on the BSR Application screen does not contain a routing number for the status poll VDN.

Interflow VDN field is blank

A queue-to best or check-best command fails because the entry on the BSR Application screen for the relevant location does not contain a routing number for the interflow VDN.

Agent status info invalid

A consider location command fails because the status poll returns invalid data for an available agent (AIT, skill level, or occupancy is missing or out of range). Vector processing continues at the next step. Polling of this location is temporarily suppressed.

BSR status info invalid

A consider location command fails because the status poll returns invalid EWT data. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

No BSR data in response

A consider location command fails because the status poll does not return data in the DISCONNECT message. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

No response from status poll

A consider location command fails because the status poll does not respond within the time allowed or because the status poll cannot be performed. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

Bad resp from status poll

A consider location command fails because the command receives an invalid response from the status poll such as an LAI acceptance message ( ALERT or CONNECT). Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

BSR EWT is infinite

A consider command fails because the EWT for the referenced split or skill is infinite. This can be because all agents are logged out, in the Aux work mode, or because no queue slots are available. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

BSR status poll attempt failed

A consider location command fails because the status poll attempt failed. See other events for the specific reason. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

BSR poll no trunks

A consider location command fails because there are no available trunks. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

BSR poll seize fail

A consider location command fails because the status poll is unable to connect to a trunk due to a hardware problem. Vector processing continues at the next step. Polling of this location is temporarily suppressed.

High short is a vector number

Low short is a step number

Call ID

BSR poll glare retry

The first status poll attempt for a consider location command is unable to connect to a trunk due to a race condition. The same trunk being seized for the outgoing call has an incoming call from the remote end. This status poll is attempted once more. A second attempt failure results in event 282.

High short is a vector number

Low short is a step number

Call ID

BSR interflow retry due to glare

BSR interflow step failed because of glare. The route is retried once.

High short is a vector number

Low short is a step number

Call ID

Invalid status polling destination

An attempt is made to perform BSR polling over ISDN without B-Channel over a tandem trunk configuration that combines QSIG TSCs and AT&T; TSCs. Avaya's ISDN protocol does not support this type of interworking.

High short is a vector number

Low short is a step number

Call ID

BSR Poll: TSC not administered

The Trunk Group screen does not contain a trunk member administered for purposes of TSC.

High short is a vector number

Low short is a step number

High short is a vector number

Low short is a step number

BSR: Adjust-by invalid

The consider location adjust by command contains a variable with an invalid value of none or #. Vector event 38 is also generated.

NAA/NWA ratio (Number of available agent to Number of working agent ratio)

290

BSR: bad naa/nwa ratio

BSR: bad naa/nwa ratio (number of available agent to number of working agent ratio)

High short is a vector number

Low short is a step number

Call ID

BSR: Location invalid

The consider location command contains a variable with an invalid value of none or #.

High short is a vector number

Low short is a step number

Call ID

Data dropped by other app

The network does not support the transport of all user data, so some user data is not sent. You can prioritize the user data on the Shared UUI Feature Priorities page of the Trunk screen.

High short is a vector number

Low short is a step number

Call ID

No room for reply-best information

The network or shared trunk setting does not support the transport of all data for the best resource. This is unlikely under normal circumstances since only 12 bytes of user information are required. Also see event 298.

High short is a vector number

Low short is a step number

Call ID

No room for in-VDN time

The network does not support the transport of all user data. You can prioritize the user data on the Shared UUI Feature Priorities page of the Trunk screen.

High short is a vector number

Low short is a step number

Call ID

No room for collected dgt

High short is a vector number

Low short is a step number

Call ID

No room for VDN Name

High short is a vector number

Low short is a step number

Call ID

No room for other LAI

High short is a vector number

Low short is a step number

Call ID

Reply-best got bumped

The network or shared trunk setting does not support the transport of all data for the best resource. No other applications share user data included in a DISCONNECT message.

High short is a vector number

Low short is a step number

Call ID

In-VDN time got bumped

The network does not support the transport of all user data. You can prioritize the user data on the Shared UUI Feature Priorities page of the Trunk screen.

High short is a vector number

Low short is a step number

Call ID

Collected dgts got bumped

High short is a vector number

Low short is a step number

Call ID

VDN Name got bumped

High short is a vector number

Low short is a step number

Call ID

Other LAI got bumped

High short is a vector number

Low short is a step number

Call ID

Block: send reply-best

The transport of the best data for a reply-best command is denied because the trunk group is neither supplementary service b nor shared UUI.

High short is a vector number

Low short is a step number

Call ID

No enhanced info is sent

During the execution of a queue-to best or check best steps, information forwarding transport over the trunk is denied because the trunk group is neither supplementary service b nor shared UUI. This event is not logged for LAI, for example, in execution of a route-to step, in order to permit backward compatibility.

High short is a vector number

Low short is a step number

Call ID

A BSR local treatment vector pulled a remotely queued call back to the local switch to route it elsewhere

If a queue-to best step is followed by steps that use commands other than announcement, wait, or goto, the trunk to the remote queue is dropped. This functionality can be exploited to allow the local server to take back calls that are interflowed to a remote location after a specified time limit is exceeded. To implement this strategy, a wait step with a specified time interval is included in the interflow vector on the local server, followed by more than one route-to step that redirects the call to an alternate call center locations.

High short is a vector number

Low short is a step number

Call ID

NCR: Invoke trunk not ISDN

Check that only ISDN trunks are executing the vector steps where NCR is being invoked.

High short is a vector number

Low short is a step number

VDN extension

Bad NCR trunk admin

Check that all Trunk Group screen and Signaling Group screen fields related to the NCR feature are correct.

High short is a vector number

Low short is a step number

VDN extension

NCR: No NCT service

Check that the service provider has activated the NCT feature for the trunk being used for NCT call redirections.

High short is a vector number

Low short is a step number

VDN extension

NCR: No NCT outgoing trk

Check that the trunk group is administered as a two-way trunk group and that the Usage Allocation settings for the trunk have been set up correctly.

High short is a vector number

Low short is a step number

VDN extension

NCR: NCT outgo trk drop

Shows that the second leg of the NCT call is dropped due to a trunk hardware problem, or that a vector step is executed that returned and ISDN DISCONNECT message such as a busy vector step.

High short is a vector number

Low short is a step number

VDN extension

NCR: PSTN NCT invoke err

The PSTN switch has not accepted the NCT invocation attempt. Check that the PSTN network switch complies with the NCT standards.

High short is a vector number

Low short is a step number

VDN extension

NCR: NCT netwrk err

Communication Manager has accepted the NCT invocation attempt, but has rejected it due to some error condition within the network Communication Manager. Check that the Network Call Redir field on the Trunk Group screen is administered correctly. Make a request to the service provider for troubleshooting assistance.

High short is a vector number

Low short is a step number

VDN extension

NCR: Used NCT trk-to-trk

NCT has not been successfully invoked, but the incoming call is still active as a switch trunk-to-trunk connection, this is, only an informational message.

High short is a vector number

Low short is a step number

VDN extension

NCR: No NCD service

Check that the service provider has activated the NCD feature for the trunk being used for NCD call redirections.

High short is a vector number

Low short is a step number

VDN extension

NCR: invalid nmbr

Communication Manager has detected that the number used for the NCR invocation that is administered in the ~r route to number vector step or in the BSR Application Table’s VDN Interflow Number field is an invalid number, the correct number used through Communication Manager administration.

High short is a vector number

Low short is a step number

VDN extension

NCR: NCD call connect err

The vector step is executed before the vector step invoking NCD that sends an ISDN CONNECT message to the PSTN.

High short is a vector number

Low short is a step number

VDN extension

NCR: PSTN NCD invoke err

The PSTN has not accepted the NCD invocation attempt. Check that the PSTN network switch complies with the NCD standards. Make a request to the PSTN service provider for troubleshooting assistance.

High short is a vector number

Low short is a step number

VDN extension

NCR: netwrk err

Communication Manager has accepted the NCD invocation attempt, but has rejected it due to some error condition within the network Communication Manager. Make a request to the service provider for troubleshooting assistance.

High short is a vector number

Low short is a step number

VDN extension

NCR: PSTN NCD max redirs

PSTN has detected that the call is redirected by NCD more than the public network maximum number of call deflections limit allows. Modify vector processing to reduce the number of NCD attempts.

High short is a vector number

Low short is a step number

VDN extension

NCR: Internal system err

Communication Manager problem with call processing for the NCR invocation attempt. Alternately, for NCT, the first vector step at the redirected-to endpoint is possibly not programmed with a call treatment vector step such as wait hearing ringback, wait hearing music, or announcement. Do not use vector steps such as wait hearing silence or wait hearing i-silence, for the first vector step at the redirected Communication Manager endpoint.

High short is a vector number

Low short is a step number

VDN extension

No ETSI ECT linkID

The PSTN switch has returned a FACILITY message to the local Communication Manager that includes the following reject component: LinkIDNotAssignedByNetwork. In this case, the local Communication Manager leaves the calls in a trunk-to-trunk transfer state.

High short is a vector number

Low short is a step number

VDN extension

NCR: Caller not SIP trk

Check that only SIP trunks are executing the vector steps where NCR is being invoked.

High short is a vector number

Low short is a step number

VDN extension

BBP: No task extension

No background task ext for Background BSR Polling

High short is a vector number

Low short is a step number

Call ID

BBP: Vectoring stopped

Background BSR Polling Vector processing stopped

High short is a vector number

Low short is a step number

Call ID

BBP: Background task not active

Background task not active for Background BSR Polling

High short is a vector number

Low short is a step number

Call ID

BBP: Data update error

Error in updating data for Background BSR Polling

High short is a vector number

Low short is a step number

Call ID

BBP: VDN appl mismatch

Background BSR Polling VDN appl mismatch

High short is a vector number

Low short is a step number

Call ID

BBP: Invalid route-to

Invalid route-to for Background BSR routing

High short is a vector number

Low short is a step number

Call ID

BBP: BBP task started

No Background BSR routing data for first call since BBP task was just started

High short is a vector number

Low short is a step number

Call ID

BBP: Avail agt mismatch

BSR Available Agent Strategy mismatch for Background BSR routing

BBP: BSR Available Agent Strategy mismatch

Call ID

No return destination

The return command fails and continues to the next step because no return destination data exists for the call.

High short is a vector number

Low short is a step number

Call ID

Results Truncated

A set command executed with operator CATL or CATR. The result is truncated because it is higher than 16 digits.

High short is a vector number

Low short is a step number

Call ID

Negative Result

A set command attempts to execute. A negative result is converted to # (underflow) during the processing.

High short is a vector number

Low short is a step number

Call ID

Divide by Zero

A set command attempts to execute with operator DIV. The operation specified by operand 2 divided by zero and results in a # (underflow) assignment.

High short is a vector number

Low short is a step number

Call ID

Assignment not allowed

A set command attempts to execute. The assignment field contains an invalid system-assigned variable. The variable is invalid because the variable is not a user-assigned variable or a digits buffer.

High short is a vector number

Low short is a step number

Call ID

Can't set, no lcl var

A set command attempts to assign a value to a user-assigned variable when the 8000 system limit is reached.

High short is a vector number

Low short is a step number

Call ID

Return destination stack error

A goto vector command is executed with a full return destination stack for the call. The return destination is not saved.

High short is a vector number

Low short is a step number

Call ID

Operand Overflow Underflow

A set command attempts to execute with operator ADD, SUB, MUL, or DIV. One of the operands has a # value or a value greater than 4294967295.

High short is a vector number

Low short is a step number

Call ID

Overflow Error

A set command executes and obtains one of the following results:

• A value greater than 4294967295 with a ADD or MUL operator.
• A number assigned to a variable from an arithmetic operation has exceeded the length definition. For example: set A = none ADD 1000 If variable A is defined as having a length of 3, A is set to # and this vector event is generated.

High short is a vector number

Low short is a step number

Call ID

370

VDN conf skip adj-rte

SA8835 - Skip Adjunct-Route step

High short is a vector number

Low short is a step number

Call ID

371

VDN conf skip conv-on

SA8835 - Skip Converse-On step

High short is a vector number

Low short is a step number

Call ID

372

VDN conf skip msging

SA8835 - Skip Messaging step

High short is a vector number

Low short is a step number

Call ID

VDN conf skip collect

Skips the collect step for Video Conference.

High short is a vector number

Low short is a step number

Call ID

Suspend vectors in ovld

When the processor occupancy of Communication Manager exceeds 92.5%, the system suspends the vectors for 6 seconds. The system re-checks the processor occupancy and if the processor occupancy has not still reduced, the system continues to suspend the vectors processing after every 6 seconds.

Overload flag(bit map)

0

Resume vectors after ovld

When the processor occupancy of Communication Manager reduces, the system resumes the vectors processing.

Overload flag(bit map)

0