Chapter
7
Database Tables
This section describes the purpose and structure of database tables used as persistent information storage by Universal Callback Server.
Universal Callback Server uses DBMS for the purposes of persistent information storage. In the event that the system goes down and callback requests-related data needs to be recovered for further processing, Universal
Callback Server on its startup gathers all the information from the database tables.
Universal Callback Server uses two database tables to store callback requests-
related data. Figure 12 on page 94 shows these tables as they are presented by
Microsoft SQL Server Enterprise Manager’s Database Diagram Wizard.
Reference Manual 93
Chapter 7: Database Tables
Figure 12: Database Tables Diagram
Universal Callback Server stores mandatory attributes of the callback requests in the main table which is configured in CME via Calling List object. User data which might be associated with the callback is stored in the additional table, which has a column udata_body
capable of storing binary data. The name of this additional table is formed by Universal Callback Server from the name of
“main” table. The link between the data in two tables is established by
( connid_high, connid_low
) combination of columns.
Table 18
below illustrates all fields from the “main” database table, their types and descriptions.
Table 18: Fields of the “Main” Database Table
Column Name
phone phone_type call_result attempt
Data Type
character (64) integer integer integer
Description
Phone number to dial for a callback; attached in
VCB_CONTACT attribute
Zero, not used at this time
Final outcome of the callback
Number of attempts made to deliver the callback
94 Voice Callback 7.1
Chapter 7: Database Tables
Table 18: Fields of the “Main” Database Table (Continued)
Column Name
dial_sched_time call_time integer
Data Type
integer
Description
Date and time for which the callback has been scheduled: in UTC format (seconds since midnight
01/01/1970)
Last date and time the callback was delivered: in
UTC format tz_dbid integer virt_connid callback_type character (32) integer
Configuration DBID of the time zone object; name of the time zone attached in
VCB_TZ_NAME attribute
Connection ID of the virtual call, which represents callback request
Type of requested callback (1=
ASAP
, 2=
Scheduled
) callback_status treatment_id app_id origin origin_type origin_dbid connid_high connid_low integer integer integer character (220) integer integer decimal decimal
Last status of the callback. See Voice Callback 7.1
Reference Manual, Enumerations chapter, Table 10.
Zero, not used at this time
Configuration DBID of the
Universal Callback
Server
Application object which handles callback request
Name of the DN on which callback request was submitted
Callback origination (0 =
Unknown
, 1 =
IVR
, 2 =
WEB
,
3 =
Desktop
); attached in
VCB_ORIGIN
attribute
Configuration DBID of the DN object on which callback request was submitted
High part of the Connection ID of the original call which requested a callback
Low part of the Connection ID of the original call which requested a callback
Reference Manual 95
Chapter 7: Database Tables
Table 18: Fields of the “Main” Database Table (Continued)
Column Name
ewt integer
Data Type Description
Value of estimated waiting time (EWT) in seconds; attached in
VCB_EWT
attribute ewt_time integer A timestamp when EWT was measured, in UTC format; attached in
VCB_EWT_TIME
attribute
Table 19 illustrates all fields from the additional database table, as well as their types and descriptions.
Table 19: Fields of the Additional Database Table
Column Name
connid_high
Data Type
decimal connid_low udata_body decimal binary object
Description
High part of the Connection ID of the original call which requested a callback
Low part of the Connection ID of the original call which requested a callback
User data associated with the callback
96 Voice Callback 7.1
