AltiGen comm MAXCS 87 CDR Manual

							CDR Manual 35
CHAPTER 4 
Data Storage
MAXCS can store data using either an Internal Logger Service (ILS) or up 
to two External Logger Service (ELS). CDR Search can use either ILS or 
CDR to search stored data. 
Call detail record data (CDR) and workgroup-related statistical data (RTM) 
are stored in the same database but in different tables. These two storage 
systems are described below. 
Common Features of ILS and ELS
• Status can be monitored in MaxAdmin through the bottom of the Main 
Window or through the Call Report window (System > Call Report)
• Broken and reconnection mechanism implemented on:
• TCP connection between MAXCS/ACM and Logger Service
• Database connection between Logger Service and database
When the connection is broken, the sender will cache all data to the 
first-in-first-out buffer. The sender will try to reconnect the receiver 
automatically. Once the connection is back, all data will be sent. The 
buffer is stored in memory and hard disk. The size limitation of each 
buffer is 1G (data for approximately two months), or free size of hard 
drive is less than 512 MB, whatever is met first. When the buffer is 
overflowed, the earliest data is dropped.
• Auto check and upgrade database at startup—when Logger Service 
starts, it performs the following:
1. Compares CDR structure with the current database used by 
configuration.
2. If they are the same, there is no change.
3. If they are different, and the data can be upgraded, it will be 
automatically upgraded.
4. If the database cannot be upgraded, it will rename the old database 
and create a new database; the new database will then be used to 
store data. 
						

							Differences between ILS and ELS
36 CDR Manual
• Status monitoring of connection between MAXCS and Logger 
Service—User Database ID and Client ID can be used to verify 
connection to Logger Service. “Database ID” is fixed to “Default” and 
cannot be found on any GUI. “Client ID” is mentioned as “Password” 
in MaxAdmin and External Logger Service Configuration. If the 
verification fails, the status of the Logger Service is “Invalid 
Password,” which can be monitored by the administrator.
• If no database is set up correctly, or the database is shut down when 
Logger Service is starting, it will be stopped.
Differences between ILS and ELS
• Internal Logger Service
• Implements auto retain and backup mechanism (1-12 months)
• Only MAXCS/MaxAdmin within the same computer can connect 
to the Internal Logger Service.
• External Logger Service
• Supports Microsoft SQL Server (see “Hardware Requirements”  f o r  
versions supported)
• No retain/backup mechanism
• Any computer can connect to the server (TCP port 10027)
• Any number of MAXCS systems with different System IDs can 
connect to the same Logger Service. If two MAXCS systems with 
the same System ID try to connect to the same Logger Service, the 
second Logger Service will get a “System ID conflicted” error.
• When ELS is installed within Microsoft SQL Server, the 
installation program will create the database, ODBC configuration, 
and other configuration by default. If it is installed to work with 
remote SQL, the customer must manually configure the Logger 
Service first.
Logger Service Configuration
MaxAdmin can configure CDRLogDLL, add (register) and remove New 
Logger Server for MAXCS remotely, but they cannot configure Logger 
Server. 
						

							Data Storage
CDR Manual 37
In order to implement remote manager ability, a Log Service configuration 
window can be accessed in MaxAdmin.
Use the Log Service Configuration window to Add, Edit and/or Remove 
a Log Service.
External Logger Server Configuration Tool
The External Logger Configuration Tool is used to configure Logger 
Server. Currently, all configurations are saved into registry, so any change 
in configuration will not work unless Logger Service is restarted. When the 
configuration is changed, the Configuration Tool will automatically restart 
Logger Service.
Note:There is no configuration tool for Internal Logger Server because 
all parameters are fixed. 
						

							External Logger Server Configuration Tool
38 CDR Manual
Configuration GUI for External Logger Server
For ELS, only Database ID, Password, ODBC Source Name, Login ID 
and Password are configurable. Other parameters, such as TCP port and 
buffer folder, cannot be changed. If the database is a Microsoft Access 
Database, ELS can purge and back up the database on demand.
Testing the DB Dialog
The Test button is used for testing and diagnosing the ODBC database. It 
can test whether the ODBC source, Login ID and password are correct and 
that the CDR/RTM tables of the database are compatible with the current 
Logger Server.
Important:It is strongly recommended that you run this test after you 
have changed any database parameters.
If the configuration tool cannot connect to the ODBC source, it will pop up 
the following dialog boxes to report error information and to re-input login 
information. 
						

							Data Storage
CDR Manual 39
When the ODBC information is correct, the tool will check all tables 
required and will try to find all differences. If the database in not 
compatible, the OK button will be disabled.
Limitations
• One Internal Logger Server per computer.
• One External Logger Server per computer.
• One Super Logger Server per computer.
• One Internal, External and Super Logger Server can be installed in the 
same computer. 
						

							External Logger Server Configuration Tool
40 CDR Manual
• One MAXCS can only output data to, at most, one Internal Logger 
Server and two External Logger Servers.
• Internal Logger Server only serves MAXCS of same computer.
• Internal Logger Server only supports Microsoft Access Database.
• Internal and External Logger Server do not support multiple databases.
• One Database Connection license is required for every Logger Server 
and every CDR Search requires one additional license.
• External Logger Configuration tools cannot run remotely.
• 100 commands per second on every TCP or database connection.
• Maximum 1 GB buffer files for every buffer; otherwise, always keep 
500 MB free hard drive space. (When free space is below 500 MB, the 
buffer files will be truncated automatically.) 
						

							CDR Manual 41
CHAPTER 5 
Records and Data Schema
This section contains explanations  of the CDR search results records, 
including the data schema. 
Important!
In order to reduce th e storage space of the database, records with all zero 
files are not written  to the database.
Search Results
This section explains the fields  in all the CDR Search results windows.
CDR Search / Group CDR Search Results: Summary 
Window
Field Definition
ID Number assigned by CDR Search to this record
Time/Extension/
Workgrou
 p/Trunk/
Date Start time for this record, if sorting by 
Tim e; Extension for 
this record, if sorting by Extension ; Workgroup for this 
record, if sorting by  Workgroup; Trunk for this record, if 
sorting by Trunk; Date for this record, if sorting by  Date.
Total Records Total CDR records of the type searched for. 
Note:
One call may have mult iple CDR
  records logged. 
Therefore, the number of records may not match 
the number of calls in WG Statistics screens.
Total Duration Sum of duration of the calls in the records, where duration 
lasts

 from  Start Time  to End Time  (see “Record Window 
for Call Info”  for explanations of these fields)
This is shown in “Summary (CDR  Search and Group CDR Search)” 
						

							Search Results
42 CDR Manual
CDR Search / Group CDR Se arch Results: Detail 
Window
Field Definition
ID Number assigned by CDR Search to this record
Session ID Unique number assigned by MAXCS to this call
Sequence ID Unique number to identify multiple records of same call 
(same session ID)

, beginning with 0.
Conference ID Unique number to identify multiple conference calls.
Date Date of call
Time Start time of call
Duration Duration of call 
(En
 dTime minus StartTime; see 
Table  , “Table: CDRMAIN"  for explanations of these 
schema)
Wait Time RingDuration plus 
Qu
 eueDuration (see Table , 
“Table: CDRMAIN"  for explanations of these schema) 
Talk Time TalkDuration
 (see Table , “Table: CDRMAIN"  for 
explanations of these schema)
Others Time AADuration plus Hol
 dDuration plus VMDuration
Message Duration VMRecDuration
Exit state  The last state of call before the call record is logged. 
(see 
Table  , “Table: CDRMAIN"  for details)
Caller ID Caller phone number of a call
Caller Name Caller name for a call
Target ID Target number for a call
Target Name Target name for a call
DNIS DNIS information for an incoming call
Acct Code Account code
URL URL when “call” is initiated by AltiWeb user clicking the 
make-call butto

n
User Data Agent input
Callback Type Blank - Not a callback attempt or request
Request
 -
 A callback request
Attempt - A return ca
 ll attempt 
						

							Records and Data Schema
CDR Manual 43
Record Window for Call Info
This is shown in the “Call Details” section.
FieldDefinition
Node IDServer ID (System ID) assigned to a MAXCS system in 
MaxAdmin
Session IDSession ID: a unique number, usually 9 digits or larger, assigned 
by MAXCS to a call
Internal CallInternal or external call
DirectionDirection of the call (incoming or outgoing)
Start Time
Outgoing call: Date / time when caller receives ringback, busy, or 
connect signal
Incoming call: Date / time when system responds to the call.
End TimeDate and time when call exits this stage or disconnects
DurationDuration of call (End Time minus Start Time)
Caller TypeCaller line type (see Table , “Table: CDRMAIN" for details)
Caller PADLine’s physical address for a call
Caller IDCaller number for a call 
Caller NameCaller name for a call 
Target TypeCall target line type (see Table , “Table: CDRMAIN" for details)
Target PADPhysical address of line for a call target
Target IDNumber for a call target
Target NameName for a call target
Workgroup NumberTarget workgroup number for an incoming call
Outgoing 
WorkgroupWorkgroup number for an outgoing call, as set in MaxAdmin or 
by agent at logon
DNISDNIS number for incoming call
ProjectProject number for trunk, as set in MaxAdmin
Account CodeAccount code
Attendant DurationDuration while call is in Auto Attendant/IVR state
Ring DurationDuration while call is in ringing state.
Queue DurationDuration while incoming call is in queue (workgroup or direct call) 
						

							Search Results
44 CDR Manual
VM DurationDuration after a call goes into voicemail box; includes 
greeting, false attempts at messages, and review of 
message, and includes VM Record Duration
VM Record DurationDuration of recording time for a VM message that was 

Length field of a voicemail.
Hold DurationDuration while call was on hold or parked
Talk DurationDuration while the call is answered by a person; see Table , “Table: CDRMAIN" for details)
Record DurationDuration of conversation recording
Exit StateThe last state of call before the call record is logged; (see Table: CDRMAIN for details)
URLURL when “call” is initiated by AltiWeb user clicking the make-call 
button
User DataAgent input
IVR DataThe data collected in auto attendant. Example: 
CustomerID=1025&ZIP=95134
Caller DepartmentThe department name of the calling extension (Department 
name can be defined by using Enterprise Manager)
Callee DepartmentThe department name of the target extension (Department 
name can be defined by using Enterprise Manager)
Callback Type 
Blank - Not a callback attempt or request
Request - A callback request
Attempt - A return call attempt
Callback Sesision IDSame as the Request call CDR Session ID
Callback Exit state
1 - Callback requested
2 - RNA
3 - Busy
4 - Callback rejected
5 - Callback succeeded
Field Definition