1st Skill

To assign a skill number. Valid entries are from 1 to 8000. You can leave this field blank.

This field is applicable if:

• The Expert Agent Selection (EAS) field on the System-Parameter Customer-Options screen is active for the system.

• The field option in the Meet-me Conferencing field on the Vector Directory Number screen is n.

2nd Skill

3rd Skill

Acceptable Service Level (sec)

To determine the number of seconds within which agents must answer all calls to the Vector Directory Number (VDN). Basic Call Management System (BCMS) tracks the percentage of calls answered within the administered time.

Valid entries are from 0 to 9999 seconds. You can leave this field blank.

This field is applicable if:

• The BCMS/VuStats Service Level field on the System-Parameter Customer-Options screen is active for the system.

• The field option in the Measured field on the Vector Directory Number screen is internal or both.

Allow VDN Override

To determine whether to change the active VDN for a call. Valid entries are y and n.

If you select n, the routed-to VDN does not replace the active VDN. This field option is the default.

If you select y, the routed-to VDN replaces the active VDN and the VDN parameters associated with the call use the routed-to VDN.

This field is applicable if the field option in the Meet-me Conferencing field on the Vector Directory Number screen is n.

Apply Ringback for Auto Answer Calls

To prevent ringback to the caller for a call that Communication Manager delivers to an agent in the auto-answer work mode.

Valid entries are y and n. The default is y to provide ringback to the caller.

This field is applicable if the field option in the Auto Answer field on one of the following screens is y:

• Station

• Agent LoginID

Attendant Vectoring

To use the VDN as an Attendant Vectoring VDN. Valid entries are y and n.

If you select y, Communication Manager deletes all call center-related fields, such as skills and Best Service Routing (BSR).

AUDIX Name

To type the name of the AUDIX™ messaging system if the VDN is associated with an AUDIX™ vector.

You must type the name of the messaging system as is available on the Adjunct Names screen.

BSR Application

To use multisite BSR with a VDN. You can assign a 1-digit to 3-digit number to specify an application plan for the VDN.

This field is applicable if the Lookahead Interflow (LAI) and Vectoring (Best Service Routing) fields on the System-Parameter Customer-Options screen are active for the system.

BSR Available Agent Strategy

To determine the BSR agent selection strategy for identifying the best split or skill for a call.

Valid entries are:

• 1st-found: BSR stops agent selection when a consider series finds an available, that is, idle agent.

• EAD-LOA: BSR selects the least occupied agent with the highest level for the skill.

  EAD-LOA is Expert Agent Distribution-Least Occupied Agent.

• EAD-MIA: BSR selects the most idle agent with the highest level for the skill.

  EAD-MIA is Expert Agent Distribution-Most Idle Agent.

• UCD-LOA: BSR selects the least occupied agent.

  UCD-LOA is Uniform Call Distribution-Least Occupied Agent.

• UCD-MIA: BSR selects the most idle agent.

  UCD-MIA is Uniform Call Distribution-Most Idle Agent.

The EAD-LOA and EAD-MIA field options are available with EAS.

The UCD-LOA field option is applicable if the Least Occupied Agent field or the Business Advocate field is active for the system.

This field is applicable if:

• The Vectoring (Best Service Routing) field on the System-Parameter Customer-Options screen is active for the system.

• The field option in the BSR Tie Strategy field on the Vector Directory Number screen is system or alternate.

BSR Local Treatment

To provide local audio feedback to interflow calls in a queue. You can administer this field on local and remote VDNs.

BSR Tie Strategy

To determine the BSR selection strategy when a tie occurs for calls from the same VDN.

Valid entries are:

• 1st-found: BSR uses the previously selected best choice as the best skill or best location.

• alternate: BSR alternates the selection algorithm during a tie between Expected Wait Time (EWT) calculations and Available Agent Strategy.

  For every tie, BSR selects the consider series with the tie to send the call instead of the first selected split/skill or location. This field option balances call routing when the cost of routing to remote locations is not a concern.

• system: BSR uses the BSR Tie Strategy field option on the Feature-Related System Parameters screen.

  This field option is the default.

This field is applicable if the Vectoring (Best Service Routing) field on the System-Parameter Customer-Options screen is active for the system.

COR

To assign a Class of Restriction (COR) to the VDN. Valid entries are from 0 to 995.

You cannot leave this field blank.

Daylight Saving Rule

To define the Daylight Saving Time (DST) rule.

You can apply the DST rule and the time zone offset to the goto time-of-day commands in the vector that you assign to the VDN. The time-of-day (TOD) calculations depend on the local time of the receiving call VDN.

The assigned rule number applies start rules and stop rules that you administer in the Daylight Saving Rule field for that rule number.

Valid entries are:

• 0: The DST rule is inapplicable. If the system time has a daylight saving rule, the system deletes this rule before evaluation of the goto if time-of-day conditional.

• 1–15: To use the rule as defined in this field.

  When you use a number other than 0 (zero), the system does not use the rule associated with the main server clock display time and the main server offset. The offset and rule assigned to the active VDN for the call are applied to the operating system standard time so that local time for the VDN is used to test the TOD step.

• system: To use the same DST rule as the system clock shown in the display/set time field.

Destination

To indicate whether calls are routed using a vector number or a policy routing table.

Valid entries are Vector Number and Policy Routing Table.

Display VDN for Route-To DAC

To display the VDN for routed-to direct agent calls. Valid entries are y and n.

You can use this field when the following vector commands with the Coverage field option as y route EAS direct agent calls:

• adjunct routing

• route-to number or route-to digits

Extension

To view the extension associated with the VDN. The extension is a number that begins with a valid first digit and conforms to the length defined by the system dial plan.

Measured

Associated field: Report Adjunct Calls as ACD

To collect measurement data for the VDN. BCMS, Call Management System (CMS), or Avaya IQ collect data for reporting purpose.

Valid entries are:

• both

• external

• internal

• none

The field options both and internal are applicable if the BCMS field on the System-Parameter Customer-Options screen is active for the system.

You can administer a CMS release on the Feature-Related System Parameters screen to change the field options to both or external.

The system displays the Report Adjunct Calls as ACD field if the Measured field is present on the Vector Directory Number screen.

To determine whether adjunct routed calls are identified in SPI messaging as ACD calls to the indicated skill when the call is adjunct routed. This feature is administered per VDN basis and the default value is no.

Valid entries are and .

• y: Adjunct routed calls are identified in SPI messaging as ACD calls. Therefore, an adjunct routed call is also counted as an ACD call for a skill in reports.

• n: Adjunct routed calls are not counted as ACD calls. This is the default value

If you set the Report Adjunct Calls as ACD field to yes then you must set the value of the the Measured field to either external or both.

Meet-me Conferencing

To determine whether to use the Meet-me Conferencing feature. Valid entries are y and n.

This field is applicable if the Meet-me Conference field is active for the system.

Name

To assign an alphanumeric name of up to 27 characters that identifies the VDN. You can leave this field blank.

When users press the new VDN-INFO button on H.323 or DCP phones, Communication Manager displays the complete VDN name of the active call.

Observe on Agent Answer

To determine when Communication Manager must connect an observer to a call.

Valid entries are:

• y: Communication Manager connects the observer to a call after delivering the call to an agent.

• n: Communication Manager connects a non-Observe by Location observer to a call at the beginning of vector processing. This field option is the default.

Reporting for PC or POM Calls

Associated field: PC Predictive Reports Skill

To assign the VDN for Proactive Outreach Manager (POM) or Proactive Contact (PC) outbound calling.

Valid entries are y and n.

If you have switch-classified outbound calling with PC, use this field and the associated skill field to activate the improved integration with the PC feature.

If you have a POM system, use this field to activate the VDN for indication to reporting of a POM call to the VDN.

This field is applicable if the field option in the Measured field on the Vector Directory Number screen is external or both.

This associated field is applicable if you administer the following fields as y:

• The ASAI Link Plus Capabilities field or the Computer Telephony Adjunct Links field on the System-Parameter Customer-Options screen.

• The Reporting for PC or POM Calls field on the Vector Directory Number screen.

If you assign a skill number, the VDN option applies to PC reporting. If you leave this field blank, the VDN option applies to POM calls.

Return Destination

Associated field: Call Origin

To assign the VDN extension number to which an incoming trunk call is routed if the call returns to vector processing after an agent drops the call.

You can leave this field blank.

This associated field is applicable if you assign a VDN extension in the Return Destination field.

Use this field to administer the types of calls that Communication Manager must redirect to the extension in the Return Destination field.

Valid entries are:

• both: To apply VDN Return Destination (VRD) to external or internal calls.

• external: To apply VRD only to incoming external trunk calls directly to the VDN. This field option is the default.

• internal: To apply VRD only to internal calls that have not been through vector processing. Internal calls for this purpose include trunk calls that are transferred, forwarded, or covered to the VDN or Adjunct Switch Application Interface (ASAI) routed.

Send VDN as Called Ringing Name Over QSIG

To determine whether to display the VDN name to the receiver when the phone is ringing. Valid entries are y and n.

Service Objective (sec)

To determine the service level for the VDN. Valid entries are 1 to 9999. The default value is 20 seconds.

This field is applicable if the Business Advocate field on the System-Parameter Customer-Options screen is active for the system.

This field activates the Dynamic Queue Position (DQP) feature, which is also referred to as Service Objective by VDN. With DQP, you can place calls from multiple VDNs in a single skill queue, while maintaining different service objectives for each VDN.

TN

To assign a Tenant Partition number.

Valid entries are 1 to 250.

Used for BSR Polling

To prevent Communication Manager from sending polling-related messages to CMS or Avaya IQ for unmeasured calls.

Valid entries are y and n.

Use this field for unmeasured VDNs that route to vectors with a BSR reply-best command.

The field is applicable for unmeasured VDNs assigned to a vector with no queue-to command, but with consider steps terminated by the reply-best command. The trunk groups that are used to route calls to the VDNs are also unmeasured.

You can use this field if the field option in the Measured field on the Vector Directory Number screen is none.

The field is applicable when you use Best Service Routing (BSR) and Look Ahead Interflow (LAI).

Use VDN Time Zone For Holiday Vectoring

To determine whether to use VDN Time Zone with Holiday Vectoring. Valid entries are y and n.

If you select y, Communication Manager uses VDN Time Zone with Holiday Vectoring. If you select n, Communication Manager uses the system time with Holiday Vectoring.

VDN of Origin Annc. Extension

To type the extension of the VDN of Origin Announcement (VOA). You can leave this field.

This field is applicable if the VDN of Origin Announcements field on the System-Parameter Customer-Options screen is active for the system.

VDN Override for ASAI Messages

To determine whether to send the called number as the active VDN for ISDN Trunk ASAI messages.

If you select n in the Meet-me Conferencing field, this field follows VDN Override Rules when the system changes the active VDN for a call.

Valid entries are:

• all: To allow VDN Override Rules for the ASAI messages so that Communication Manager can use the active VDN for the called number for all types of calls to the VDN, including local or internal calls and external incoming ISDN trunk calls.

• ISDN Trunk: When an incoming ISDN trunk call is routed to the VDN, the called number information sent in the ASAI event and adjunct route request ASAI messages is the active VDN extension that becomes associated with the call based on the VDN Override Rules. This field option is not applicable to local or internal calls.

• no: The called number information sent for the Call Offered, Alerting, Queued, and Connect ASAI event notification messages and the adjunct-request message is always the called VDN extension in the called number Information Element (IE) sent in the incoming ISDN SETUP message or the called number of the local call and does not change after routing to the called VDN and subsequent routed-to VDNs.

This field is applicable if:

• The ASAI Link Core Capabilities field on the System-Parameter Customer-Options screen is active for the system.

• The G3 Version field on the System-Parameter Customer-Options screen is V10 or later.

VDN Timed ACW Interval

Associated field: After Xfer or Held Call Drops

To assign an After Call Work (ACW) interval for auto-in agents who receive calls from this VDN.

If you administer this field, Communication Manager places an auto-in agent who receives a call from this VDN in the ACW mode after the agent releases the call.

When the administered interval is complete, Communication Manager makes the agent available to receive calls.

The field has priority over the Timed ACW Interval field on the Hunt Group screen.

For incoming ACD or direct agent calls, Communication Manager places an auto-in agent in the Timed After Call Work (TACW) mode, instead of making the agent available, if the held caller drops or the agent transfers the call.

Use this associated field for the agents in a hunt group or for calls delivered from a VDN when the Timed ACW Interval field is administered to a non-zero value.

VDN Time-Zone Offset

To apply VDN Time Zone Offset to the Communication Manager clock when a TOD vector command is executed. The Communication Manager clock handles the DST changes by using the existing operation.

The syntax is +HH:MM, that is, [+ or -] [0 - 23] : [0 - 59]

Valid entries are:

• + or -: Use the minus (-) sign if the VDN local time is earlier than the server local time.

  Use the plus (+) sign if the VDN local time is later than the server local time.

• 0 - 23: Time in hours

• 0 - 59: Time in minutes

The default is +00:00. When the default is set, the Communication Manager time is used without modification.

VDN variables

Var

To assign up to nine VDN variables from V1 to V9.

Description

To type up to 15 alphanumeric characters to describe each VDN variable.

Assignment

To assign unvalidated decimal numbers of up to 16 digits to each VDN variable.

You can leave this field blank to assign no decimal numbers to the VDN variables.

VDN Override Rules means that the parameters that are associated with each VDN can change based on the field settings of the next VDN that the call routes to.