Avaya™ Interaction Center Release 6.0 Agent Data Unit Server Programmer’s Guide DXX-1015-01 Issue 1.
2002, Avaya Inc. All Rights Reserved Notice Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change. Preventing Toll Fraud Ordering Information Avaya Publications Center Voice: +1 800 457 1235 International Voice: 410 568 3680 Fax: +1 800 457 1764 International Fax: 410 891 0207 Email: totalware@gwsmail.
CONTENTS BEFORE YOU BEGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1 THE ADU SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Start-up Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Cooperation of ADU Servers .
Contents Setting Event Monitoring Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Monitoring Criteria: Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Relational Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Boolean Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BEFORE YOU BEGIN Typographical Conventions This guide uses the following font conventions: Font Type Meaning code This font signifies commands, information that you enter into the computer, or information contained in a file on your computer. italics This font is used to add emphasis to important words and for references to other chapter names and manual titles. It also indicates variables in a command string. jump Blue text in online documents indicates a hypertext jump to related information.
3 Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. 4 If you continue to have a problem, contact Avaya Technical Support by: Logging in to the Avaya Technical Support Web site (http://www.avaya.com/support/qq). Calling or faxing one of the following numbers from 8:30 a.m. to 8:30 p.m. (Eastern Standard Time), Monday through Friday (excluding holidays): Toll free in the U.S.
Educational Services Printed Documentation You can purchase printed copies of these manuals separately. For details, see on the back of this manual’s title page. License to Print the Electronic Documentation Online copies of documentation are included on the CD-ROM that accompanies every software release.
Agent Data Unit Server Programmer’s Guide
CHAPTER 1 THE ADU SERVER Overview The Agent Data Unit (ADU) Server is responsible for tracking the state of agents at the contact center. Agents are also referred to as customer service representatives, or CSRs. The term “agent” is used throughout this book to signify a customer service representative. When an agent logs in the Avaya Interaction Center (Avaya IC), the ADU Server creates a record of the agent's session on the system. This record is called an Agent Data Unit or ADU.
Chapter 1 The ADU Server Cooperation of ADU Servers When a new ADU Server is added to Avaya IC, existing ADU Servers must be made aware of the new server through use of the IC Manager. Refer to IC Administration Volume 1: Servers & Domains for information on updating servers. When the ADU Servers have been made aware of each other, they can make requests of each other. This is most significant in the area of the Assign method.
CHAPTER 2 THE AGENT DATA UNIT Definition of an ADU When an agent logs in to Avaya IC for the first time, a record called an Agent Data Unit (ADU) is created. The ADU contains information about the agent’s activities during the session. A typical ADU might contain the time the agent logged in, the various states the agent entered (InCall, WrapUp, and so on..), and the time when the agent last entered each state. Note: When an agent logs back into Avaya IC, a new ADU is not created.
Chapter 2 The Agent Data Unit Any application that wants to interact with an ADU has to request it by its unique identifier, the ADUID. Upon request, the ADU Server passes the ADUID out to other processes, thus enabling applications to request access to individual ADUs. The ADU Server also honors requests to watch for ADUs that contain certain values. If any ADU matches the monitoring criteria, the ADU Server issues event messages (which contain the ADUID) to “interested” clients.
The ADUID -u user name to log in as (often Admin) -p password of user No space between -x and the text that follows. Example: listadu -iBostonADU -uAdmin -pDaphnie There are defaults for all of these, but if a login error occurs, always specify -u and -p. The ADUID When an ADU is created, it is automatically given an identification number (ADUID) that uniquely defines the agent's Avaya IC session.
Chapter 2 The Agent Data Unit Names are restricted to non-empty strings of less than 35 characters. (Container names may contain more than 35 characters. Refer to “Container Names and Special Tokens,” on page 22 for information on container names.) Names may contain letters (a..z, A..Z), digits (0..9), and the underscore character (_). Data element names are case sensitive: “foo”, “Foo”, and “FOO” refer to three different data elements.
ADU Contents Core ADU Fields The following ADU fields are used by both agents and queues on Avaya IC. Field Name Description Set By adu_id A string that uniquely identifies the ADU. ADU Server createtime The date and time the ADU was created in yyyy-mm-dd hh:mm:ss format. ADU Server createtimet The time_t of the ADU creation. ADU Server duration Historical field.
Chapter 2 The Agent Data Unit Agent ADU Fields The following ADU fields are used by agents on Avaya IC. Field Name Description Set By auxwork..detail A code that describes the reason that the agent entered this state. Blender Server auxwork..endtime The time that the agent exited this AuxWork state. Blender Server auxwork..starttime The time that the agent entered the current AuxWork state. The is the increment time that agent enters into a different AuxWork state.
ADU Contents Field Name Description Set By .contactsoffered The total number of contacts that arrived since the agent logged into this media channel. IC Manager computes handled contacts by taking the difference between .contactsoffered and .abandoned. Media Connector Server .currentload The current task load assigned to the agent for this media channel. This is used to throttle delivery of ADUs. Workflow Server .
Chapter 2 The Agent Data Unit Field Name Description Set By ..state The current media contact state. Normalized contact states are: Alerting Active On-Hold Wrap-up Completed Media Connector Server ..state.. starttime The time that the media channel state started. Media Connector Server modifier This field identifies the login id or uuid of the user who caused the event. It is inserted into each event that is sent to reporting packages.
ADU Contents Field Name Description Set By ts..equip Equipment number. Definity Telephony Server ts..starttime Time (time_t) that the client assigned to the TS. Definity Telephony Server voice.acdname The name of the ACD the TS is serving. Telephony Server voice.connector voice.connectorname (Sheet 4 of 4) Voice Data Containers The following table lists the call containers in which end point events and attributes are stored.
Chapter 2 The Agent Data Unit Name Value Explanation voice.X.leg_id unique id (UUID) Unique leg_id of the current leg of the call. voice.X.loginid loginid Login id of client at end point X. voice.X.origin phone number Phone number (ANI) at other end of end point X. voice.X.queue delta time The elapsed time in seconds between the creation of an EDU and the time at which the switch reports the call as queued. voice.X.
Containers Field Name Description Set By contactsoffered The total number of contacts received by the queue. The number of handled contacts is computed by IC Manager by taking the difference between contactsoffered and abandoned. Media Connector Server id The media channel specific id of the queue. The id must be unique for a media channel in a specific site. Media Connector Server media The type of media channel over which the queue is receiving contacts: voice, email, or web.
Chapter 2 The Agent Data Unit For example, within each ADU, the Telephony Server creates a container called ts, and within the ts container it creates a subcontainer for each of the agent's logical phones (ts.1, ts.2, and so on). Each data item pertaining to that logical phone takes a private subtree of the container–ts.1.phone, ts.1.ptype, and so on. Values for a second logical phone are written in fields ts.2.phone, ts.2.ptype, and do not interfere with values written for the first logical phone.
Containers ! The ! token expands into a numeric token that belongs to the client. Tokens that belong to a given client are created via a special use of the + token. Essentially, a subcontainer created with + is assumed to belong to a caller (usually the one who created it), and the ! token will find it. To create a subcontainer for another client, add the loginid of the client after the + token that creates it, as follows: “agent.
Chapter 2 The Agent Data Unit Container Configurations The following TS configuration parameters were agreed upon with regards to containers: Parameter Type Default Description aducon bool false Turns ADU Containers on/off tscon bool false Turns EDU Containers on/off containers_56_style bool false Determines if “state” statistics in the old style (5.6) are written. containers_60_style bool true Determines if “state” statistics in the new style (6.0) are written.
Containers EDU Values written if tscon is set to true: voice.1.loginid voice.1.leg_id voice.1.agent_key voice.1.destination voice.1.origin voice.1.direction voice.1.connect voice.1.holdtime voice.2.loginid voice.2.leg_id voice.2.agent_key voice.2.destination voice.2.origin voice.2.direction voice.2.connect voice.1.exit_reason voice.2.transfer voice.2.ringtime voice.2.queuetime voice.2.talktime voice.2.exit_reason Issue 1.
Chapter 2 The Agent Data Unit ADU and EDU values written if containers_56_style is set to true: voice.1.state (value="alerting") voice.1.state.alerting.starttime voice.1.state (value ="incall”) voice.1.state.incall.starttime voice.state.incall.total voice.1.state (value="hold") voice.1.state.hold.starttime voice.state.hold.total voice.2.state (value="incall") voice.2.state.incall.starttime voice.1.state (value="disconnected") voice.1.state.disconnected.
CHAPTER 3 EVENT MONITORING ADU Event Monitoring This chapter describes the events that are sent by the ADU Server. This chapter also explains how to assign a request on behalf of a client and how to establish monitoring criteria. The ADU Server continuously monitors the contents of ADUs for changes, and reports those changes to interested clients through event messages.
Chapter 3 Event Monitoring Event Description Message ADU.end The ADU has been terminated. The server passes an ADU.end message to all monitoring applications. All of the data elements in the ADU. ADU.transfer The ADU has been transferred. The new client and the ADUID. (Note that ADUs are not generally transferred. This event is relatively rare.) ADU.watch The ADU matches the monitoring criteria. All of the data elements in the ADU.
Setting Event Monitoring Criteria Assigning to the ADU Server and monitoring an ADU do not add a client's name to the internal list of ADU-modifying clients. (The internal list of clients is described in “ADU Termination,” on page 12.) Assigning allows the client to watch the activity of an ADU. The client does not have to issue an ADU.Terminate() for each ADU being watched. By default, a client's assign criteria is distributed to all ADU servers.
Chapter 3 Event Monitoring Example: ADU.Assign "loginid=Joe & ts.1.s=wrapup" In the above example, the client has assigned to the ADU Server, asking it to watch for any ADU that contains the following two values: “Joe” in the field loginid “wrapup” in the ts.1.s field. In other words, notify the client every time Joe is in the wrapup state. An example of a selection criteria string when making an ADU monitor request: //[ADU.
Setting Event Monitoring Criteria This assign criteria watches all EDUs in the system because all EDU IDs are longer than empty strings. Change events that do not reflect a change in the loginid, any matching data.*, or any subcontainer of the call container are also suppressed. Change events that not suppressed are trimmed to list only the names that are provided on the projection list. The duid, time, and modifier fields are also provided.
Chapter 3 Event Monitoring Boolean Operators Boolean comparisons that return evaluations of true or false can be performed between two values. The two boolean operators are described below. Symbol Definition Description & and Both expressions must be true. | or True if one or both expressions are true. For example: ts.1.s=Available | ts.1.s=WrapUp selects all ADUs in which the agent state is either Available or WrapUp. Terms may also be grouped with parentheses for more complex expressions.
Setting Event Monitoring Criteria Monitoring Criteria: Examples The following examples demonstrate how to instruct the server to monitor ADUs that fulfill specific criteria. As you can see, there is flexibility in specifying monitoring criteria. Choose the method that best fits the current circumstances. Criteria Example Description ts.*.phone = "1234" or ts.*.phone : "1234" Monitor all calls for agent extension 1234. ts.*.phone > "0999" & ts.*.
Chapter 3 Event Monitoring 34 Agent Data Unit Server Programmer’s Guide
CHAPTER 4 ALARMS IC Manager provides system administration tools for monitoring alarm events. Visual and sometimes auditory alarms (beeps) are triggered whenever the system detects problems that require human intervention, such as server failures. Alarms are categorized as Emergency, High, Low, or Informational. (For more information about monitoring alarms, refer to IC Administration Volume 1: Servers & Domains.
Chapter 4 Alarms Cause/Recommended Action Alarm Name Priority Description FailADUCon High Connection to closed; n dropped watchers [reason] A connection to a remote server has failed. The UUID of the remote server is reported, as is the number of clients that were assigned to the server. The reason is often ADU.ServerFailed. LostADUEvents High n events lost due to network congestion or error Event handling requests are timing out.
CHAPTER 5 ADU SERVER CONFIGURATION System Considerations The Max Active Adus configuration parameter, described below, should be set with consideration for system capability. The number of ADUs that can be effectively handled by the ADU Server is proportional to the system's available memory and processor speed. A typical ADU requires 40K in memory. Active agent sessions might require 60K or more. Memory can be conserved by using the same data names in many ADUs.
Chapter 5 ADU Server Configuration Label Description No User Interval (nouserinterval) Minimum number of seconds an ADU may linger in memory when there are no users active for it. Default is 60 seconds. Minimum is 1 second, maximum is 90 minutes. Random Kill Interval (randomkillinterval) Maximum number of seconds an ADU stays in memory after the usual timers have expired. The default is 30, the range is 1 to 180 seconds.
Configuration Parameters Label Description DUStore (dustore) Enables the use of the DUStore Server. Check the check box to enable or uncheck to disable. DUStore ADU Batch Size (maxkills) The maximum number of ADUs that are sent to the DUStore Server in one set. The minimum is 1 and the default is 60. Poll Wait (pollwait) Sets the interval for the Toolkit's Select() method, in hundredths of a second. The default value is 5 (50 milliseconds). Low values increase CPU utilization.
Chapter 5 ADU Server Configuration Label Description DUindex Info2 (duindex.info2) The name of one of the fields used to identify the ADU in the DUStore Server. Used with the Find method. The default value is media. DUindex Info3 (duindex.info3) The name of one of the fields used to identify the ADU in the DUStore Server. Used with the Find method. The default value is site. Adudata Alarm Priority (adudata.alarm.priority) An alarm priority used when raising an alarm related to the ADUDATA feed.
Configuration Parameters The following configuration parameters are not presented on the ADU tab in IC Manager. You can set them on the Config tab of the ADU Server Editor dialog. Name Description filter (filter) Sets the filter for determining which ADU events are sent to the HISTMAP server (the Report Server). The event types are start, change, delete, transfer, user, and data. A plus sign (+) marks the event type for storage, a minus sign (–) excludes the event type from storage.
Chapter 5 ADU Server Configuration The following settings are on the Debug tab of the ADU Server Editor. Name Description logfilesize The maximum size of the log file. The default log file size is 2,560,000 bytes. The minimum is 1000 bytes and the maximum is 50,000,000 bytes. Ping Interval pingtimer The number of seconds between messages that are sent to a server to determine if it is running. The default is 60 seconds and the minimum is 1 second.
CHAPTER 6 IDL SPECIFICATION The Interface Definition Language (IDL) is defined within CORBA standards. It is used to create interfaces that are called by client objects and provided by object implementations. The following is the IDL description of the ADU Server. The virtual interface is inherited by both the EDU Server and the ADU Server. Several of the methods listed are specific to the ADU Server, and are therefore omitted from the method descriptions in Chapter 7.
Chapter 6 IDL Specification ORBStatus SetValuesExtended( in string vdu_id, in SeqCouple data, out SeqString newnames ); ORBStatus DeleteValues( in string vdu_id, in SeqString names ); ORBStatus DeleteOneValue( in string vdu_id, in string name ); ORBStatus DeleteSubTree( in string vdu_id, in string name ); ORBStatus SetAndTerminate( in string vdu_id, in SeqCouple data ); void GetUserSessions( in string vdu_id, out SeqString users ); //Server ONLY ORBStatus RemoteWatcher( in unsigned long handles, in string
CHAPTER 7 ADU SERVER METHODS Method Objectives Clients request Avaya IC servers to perform various functions by issuing server-specific method invocations. These methods behave in a similar fashion across all servers. For example, when you invoke any of the various ADU Server Set methods, existing values are overwritten. Values that did not previously exist are created. With the exception of the Delete methods, all of the ADU Server methods generate change events to indicate changes or additions.
Chapter 7 ADU Server Methods You are not a server Cannot find subcontainer for that owner First token must be normal here No match (or illegal usage) Cannot access invalidated member Routing Requests In an environment with several ADU Servers, any method that accepts an ADUID routes the request to another ADU Server if the ADU named is not local to the first server. ADUIDs contain location data, so a server can identify which system owns each ADU.
Method Overview ADU.GetUserSessions Returns the sessions of all clients believed to have an interest in the ADU. ADU.GetValues Retrieves all of the values of an ADU. ADU.GetValueHistory Returns everything that is known about the named field's values in an ADU. ADU.GetValuesHistory Returns everything that is known about all values in an ADU. ADU.
Chapter 7 ADU Server Methods Methods The following sections describe the ADU Server methods. ADU.Assign IDL Syntax ORBStatus Assign( in string monitorcriteria ) ; Description Create a session with the ADU Server. When a session is created, events are sent to the assigned Avaya IC client. When multiple ADU Servers are in use, Assigns watch all calls in the domain of the ADU Servers and notify the client with events when they occur. This makes Assign a relatively expensive operation.
ADU.Deassign Output Parameters aduid Agent Data Unit Identifier. VESP_SUCCESS Request was successful. VESP_ERROR Internal error in ADU Server.
Chapter 7 ADU Server Methods If used with a container name (“a.b”), you only delete that one name, a.b. However, the ADU Server methods are not able to address names “below” that point. Although a.b.c may still exist, the ADU Server cannot find it, even though GetSubTree on “a” still sees them. Resolving a.b.c depends on resolving a.b, which does not exist anymore. Callers should generally not delete elements from non-leaf positions. Input Parameters aduid Agent Data Unit Identifier.
ADU.EventsIn ADU.EventsIn IDL Syntax ONEWAY EventsIn(in string vdu_id, in SeqEvent events); Description This function adds a user-defined ADU event to an ADU. Values in the ADU are updated to reflect the names and values in the event. Input Parameters Returns aduid Agent Data Unit Identifier. event The event information. Each event must include an event name to describe the event. Requests without an event name are rejected. No return value. One way requests do not have any returns.
Chapter 7 ADU Server Methods Input Parameters search_criteria Criteria to be used for the search, consisting of names and values. If values contain spaces or anything other than letters and numbers, they must be enclosed in double quotes. If the value contains a \ or " character it must be quoted by a \ character. scope Can be one of the following. Note that the "no_os" designation is for consistency with the EDU Server. ADU_NO_OS Check the local ADU Server only.
ADU.FindOrCreate status = Vesp_Request( "ADU.FindByKey", callback, 0x2132, session, "key", "1137", &aduid ); ADU.FindOrCreate IDL Syntax ORBStatus FindOrCreate( in SeqCouple match, in SeqCouple, oncreate, out string vdu_id) ; Description This method searches the local server for an ADU that exactly matches all names and values in the match. It does not support wildcards. If a match is not found on the local server, it searches other ADU servers. If a match is found, it returns the id of the ADU.
Chapter 7 ADU Server Methods Description This method is reserved. ADU Servers use this method to pass events to each other. Client applications should not call this method. ADU.GetActive IDL Syntax ORBStatus GetActive( out SeqADU_ID aduseq ) ; Description This method finds all the active ADUs at the time the call is made. Note that only ADUs currently in memory are found. Output Parameters aduseq A list of active ADUs. VESP_SUCCESS Request was successful.
ADU.GetSomeValues Returns VESP_SUCCESS Request was successful. VESP_ERROR ADUID or name not found. C Program Example Get the value of “myfavoriteelement” from the ADU named by aduid. char *value; status = Vesp_Request( "ADU.GetOneValue", callback, 0x2132, session, aduid, "myfavoriteelement", &value ); ADU.GetSomeValues IDL Syntax ORBStatus GetSomeValues( in ADU_ID aduid, in string name, out SeqCouple matches) ; Description This function returns all names and values matching a container name.
Chapter 7 ADU Server Methods Output Parameters matches All names and values in the container or subcontainer. ADU.GetValues IDL Syntax ORBStatus GetValues( in ADU_ID aduid, out SeqCouple values ) ; Description This method retrieves all of the values of an ADU. Input Parameters aduid Agent Data Unit Identifier. Output Parameters values A sequence to contain ADU information. VESP_SUCCESS Request was successful. VESP_ERROR ADUID was not found.
ADU.GetValuesHistory Input Parameters aduid An ADUID of an existing ADU. name The name of a field. Output Parameters values A list of values to which the named field has been set. when When the field was set to each value, time_t string. who The session ID of the client that set each value. VESP_SUCCESS Request was successful. VESP_ERROR ADUID was not found. Returns ADU.
Chapter 7 ADU Server Methods For example, field quark was set twice, once at ADU creation (11:37:00am, by Scott, to “truth”) and again at ADU transfer (11:38:00, by Jane, to “charm”).
ADU.IncrValue ADU.IncrValue IDL Syntax ORBStatus IncrValue( in ADU_ID aduid, in string name, in long incr, out string newvalue ) ; Description This method is a useful alternative to using SetOneValue and GetOneValue to modify a value when there is a risk that two applications might conflict. This method changes one ADU data element. If the element does not exist it is created. An element that exists is overwritten if permission allows.
Chapter 7 ADU Server Methods Input Parameters monitorcriteria Monitor criteria string. If values contain anything other than letters and numbers (for example, spaces), they should be enclosed in double quotes, and \ or " characters must be quoted by a \ character. Refer to “ADU Event Monitoring,” on page 27 for additional information. VESP_SUCCESS Request was successful. VESP_ERROR Invalid monitor criteria. Returns ADU.
ADU.SetAndTransfer ADU.SetAndTransfer IDL Syntax ORBStatus SetAndTransfer( in ADU_ID aduid, in string to, in SeqCouple values ) ; Description This method combines SetValues and Transfer into a single call, as these operations often occur together. If the operation succeeds, it generates a Change event containing all changes made to the ADU. This operation is usually performed by Avaya IC components, not client software. Input Parameters aduid Agent Data Unit Identifier.
Chapter 7 ADU Server Methods This method allows the caller to specify which types of events are saved when ADUs are sent to the server named in the eventsink configuration parameter. The filter takes effect in subsequently created ADUs, not existing ones. All events generated for all subsequent ADUs are checked against the permissions in the bits set in the mask argument. Events already generated are not affected. The SetHistoryFilter()method can be used to override the default filter for individual ADUs.
ADU.SetOneValue Returns VESP_SUCCESS Request was successful. C Program Example Vesp_Request_Sync( "ADU.SetHistoryFilter", &ev, session, &request, aduid, HS_NOUSER /* /* /* /* /* /* method identification */ environment pointer */ session object */ pntr to pntr to request structure */ an ADU id */ The permission bit to be set for this ADU */ ); /* check ev for errors as needed */ Vesp_Request_Delete(session, request); ADU.
Chapter 7 ADU Server Methods C Program Example /*Set one value. */ status = Vesp_Request( "ADU.SetOneValue", callback, 0x2132, session, aduid, "my_favorite_element", "new value" ); ADU.SetValues IDL Syntax ORBStatus SetValues( in ADU_ID aduid, in SeqCouple values ); Description This method sets one or more ADU data elements. Data elements that do not exist are created. Existing elements are updated if permission allows.
ADU.Suspend This method is useful for applications that need to know how names were generated, especially for applications that make repeated use of the + token and need to be able to go back and fill in values in the various subcontainers they have created. The following fields are restricted and cannot be changed by applications: aduid termination transfercount duration createtime update_time endtime Setting values can generate watch, change, and drop events. Input Parameters aduid An ADUID.
Chapter 7 ADU Server Methods Input Parameters aduid Agent Data Unit Identifier. VESP_SUCCESS Request was successful. VESP_PARTIAL_ SUCCESS The ADU was not found in memory. VESP_ERROR Specified ADU does not exist. Returns C Program Example status = Vesp_Request( "ADU.Terminate", callback, 0x2132, session, aduid ); ADU.
ADU.Transfer Returns VESP_SUCCESS Request was successful. VESP_ERROR ADU not found in memory or in the ADU Server. ADU.Transfer IDL Syntax ORBStatus Transfer( in ADU_ID aduid, in string to ) ; Description This method generates an ADU.Transfer event to any process monitoring the ADU, changes the value of the transfercount element and adds the new client to the ADU's list of interested parties. Transfers do not “move” an ADU anywhere.
Chapter 7 ADU Server Methods 68 Agent Data Unit Server Programmer’s Guide
INDEX Symbols (adudata.alarm.priority) 40 (adudata.data.onlyname) 40 (adudata.event.ifname) 40 (adudata.eventname) 40 (adudata.perecnt) 39 (adus) 38 (checkpoint.interval) 37 (database) 38 (duindex.info1) 39 (duindex.info2) 40 (duindex.info3) 40 (duindex.lookup1) 39 (duindex.
Index ADU.SetHistoryFilter 62 ADU.SetOneValue 63 ADU.SetValues 64 ADU.SetValuesExtended 64 ADU.Terminate 65 ADU.TerminateMine 66 ADU.Transfer 67 ADU Server, overview 9 ADU.Assign 48 ADU.change 27 ADU.Create 48 ADU.Deassign 49 ADU.delete 27 ADU.DeleteOneValue 49 ADU.DeleteSubTree 50 ADU.DeleteValues 50 ADU.drop 27 ADU.end 28 ADU.EventsIn 51 ADU.Find 51 ADU.FindByKey 52 ADU.FindOrCreate 53 ADU.ForceTerminate 53 ADU.ForwardEvent 53 ADU.GetActive 54 ADU.GetOneValue 54 ADU.GetSomeValues 55 ADU.
Index D Data Element Names 39 Database 38 database 38 Deassign method 49 Deassign method, to stop monitoring 28 DeleteOneValue method 49 DeleteSubTree method 50 DeleteValues method 50 DUindex Info1 39 DUindex Info2 40 DUindex Info3 40 DUindex Lookup1 39 DUindex Lookup2 39 duindex.info1 39 duindex.info2 40 duindex.info3 40 duindex.lookup1 39 duindex.lookup2 39 DumpADU 35 duration 15, 29 DUStore 39 dustore 39 DUStore ADU Batch Size 39 E eDU methods VDU.
Index Memory, use of 37 Methods, overview list of 46 minimumagents 21 modifier 18 Monitor method 59 Multiple database servers, use of 42 N Name/value pairs, defined 14 No User Interval 38 NoEventSink 36 NoMeInDS 36 nouserinterval 38 Number of Cached Adu events 39 Number of fields 38 O oldest 21 On-Hold 18 Overview 9 owner 18 Ownership of an ADU 12 P padwidth 41 persistence 15 Ping Interval 42 pingtimer 42 Poll Wait 39 pollwait 39 Pool Growth Increments 38 Pool Re-Pack (%) 38 Pool Size 38 poolgrowsize 38
Index V Victims 36 voice.1.state 26 voice.1.state.alerting.starttime 26 voice.1.state.disconnected.starttime 26 voice.1.state.hold.starttime 26 voice.1.state.incall.starttime 26 voice.2.state 26 voice.2.state.incall.starttime 26 voice.acdname 19 voice.connector 19 voice.connectorname 19 voice.state.hold.total 26 voice.state.incall.total 26 voice.X 19 voice.X.abandon 19 voice.X.agent_key 19 voice.X.conferencedest.Z 19 voice.X.connect 19 voice.X.destination 19 voice.X.direction 19 voice.X.
Index 74 Agent Data Unit Server Programmer’s Guide
