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

The call encountered a vector with no steps administered.

• 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. For example, recurring announcement-wait loop.

The administration of this step occurred while the step was being executed. The call flow for this call is unpredictable. Do not change vectors when calls are active.

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

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

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

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.

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:

• Announcement was not recorded.

• Analog announcement was busied out.

• Integrated announcement board was not installed.

• Integrated announcement ports were busied out.

• Integrated announcement was being recorded or restored.

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

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.

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.

A collect digits command failed because:

• TN744 port is not available.

• All queue slots are occupied.

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

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.

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

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

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.

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.

• 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.

• The variable conditional that is tested is not defined in the Variables for Vectors table.

• A command or the messaging extension contains a variable with an invalid value of none or #.

• An agent variable is used with the converse-on command in non-VDN Return Destination (VRD) vectors.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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.

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

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

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

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

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

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

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

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

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

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.

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.

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.

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

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.

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

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

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

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

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

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.

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.

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.

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

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.

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

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.

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.

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

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.

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.

The active VDN for the call, as determined by VDN override, does not have a BSR Available Agent Strategy.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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

No longer used.

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.

For more information, see Avaya Aura® Call Center Elite Feature Reference.

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.

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.

For more information, see Avaya Aura® Call Center Elite Feature Reference.

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.

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.

For more information, see Avaya Aura® Call Center Elite Feature Reference.

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.

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.

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.

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

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

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

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.

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.

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

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.

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.

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

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.

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

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.

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.

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.

The PSTN switch has not disconnected the trunk after performing the NCD or NCT call redirection. Make a request to the PSTN service provider for troubleshooting assistance.

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.

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.

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

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

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

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

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

• 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.

• The ASAIUUI can only be set with the contents of the agent variable in VRD vectors.

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

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

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.

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.

A queue-to split, check split, or messaging split command is executed, but the call did not queue to the split because the queue is full. To prevent this condition, use a goto step...if calls queued in split...>... before each queue-to split or check split step so that an alternative treatment can be provided for such cases.

The split accessed by a queue-to split or check split command is not vector-controlled. As a result, the step is skipped.

A queue-to split, check split, or messaging split command is executed on an AAS, but the call did not queue to the split because all the agents are logged out by RONA.

Messaging system cannot be accessed using a messaging split command because the messaging-system link is down. As a result, the step is skipped.

The split administered for the messaging split command is not a messaging split, that is, the split does not have a messaging type administered. As a result, the step is skipped.

The call at the head of the queue cannot be connected to an idle agent.

A check or goto test requested a comparison of ASA for a split or skill that has no staffed agents. The comparison was based on ASA > largest possible threshold.

A goto test requested EWT for a split or skill that has not yet acquired history. The wait time is the default value.

A goto test requested EWT for a split or skill that has no queue. The wait time is treated as infinite. The comparison is based on EWT > largest possible threshold.

A goto test requested EWT for a split or skill, the queue, of which, is currently full. The wait time is treated as infinite. The comparison is based on EWT > largest possible threshold.

A goto test requested EWT for a split or skill that has no agents logged in or all logged in agents are in the Aux work mode. The wait time is treated as infinite and the comparison is based on EWT > largest possible threshold.

A goto test requested EWT for a split or skill that is currently locked. The wait time is treated as infinite. The comparison is based on EWT > largest possible threshold.

A goto test for a call or converse data passing wait requested EWT for a call that is queued only to splits or skills that have no agents logged in or that have all logged in agents in the Aux work mode. In this case, the wait time is treated as infinite and the comparison is based on EWT > largest possible threshold.

Check authorization on calling and called parties for non-PCOL calls.

A BSR polling over ISDN without B-Channel attempt has resulted in an illegal TSC interaction. Either an AT&T TSC was routed to a QSIG interface, or vice versa. The call is dropped and the denial event is logged.

A BSR polling over ISDN without B-Channel attempt is denied for one of the following reasons:

• The terminated administered TSC endpoint is disabled.

• The incoming nca-tsc call arrives at the wrong signaling group.

• The maximum number of nca-tsc is set to 0.

The station that is attempting to change the value type variable with a Facility Access Code (FAC) does not have console permission.

There is no Variable Access Code (VAC) administered for the variable in the Variable for Vector Table.

While attempting to change the value type variable to a new assignment, an invalid DTMF digit, for example #, is entered. You can enter zero to nine digits or an asterisk (*) sign.

The user changing the access code allowed the call to time out to intercept treatment. The access code is not changed.

The user changing the access code entered too many digits. The access code is not changed.

The user changing the access code did not enter a valid extension.

The user changing the access code entered a non Meet-me Conference VDN extension.

The user changing the access code did not enter the correct access code. The access code is not changed.

An administrator is making changes to the Meet-me Conference VDN, so the user cannot change the access code using an FAC. Try again later.

A user tries to access an existing Meet-me Conference call and is denied.

A user tries to service observe a Meet-me Conference call. This is not allowed.

A user tries to access a Meet-me Conference call that is already full.

A user trying to access a Meet-me Conference call dialed the wrong access code.

The station attempting to change the access code does not have console permissions COS.

The VDN that was called is not a Meet-me Conference VDN.

If controlling extension is filled in and the station and controller do not match.

The trunk used to access the Meet-me Conference is not a remote access trunk.

Controlling extension is blank and the station type is invalid.

A user cannot conference or transfer another call into a Meet-me Conference call.