Frequently Asked Questions

Below are the answers to the most frequently asked questions about call information logging.

• How many storage files can a system have?

  Each LIM can store up to 10 outputs (streams), where each output is independent. So basically the system can have 10 different outputs per LIM, each with a different format (totally 1240 outputs).

• Can several formats be active simultaneously?

  Yes, all output streams can have its own format. The same data can basically be printed in 10 different ways per LIM.

• Where are the files normally stored?

  The path to where the files are stored is /var/opt/eri_sn/call_logging.

• Is it possible to get only one output for the whole system?

  Each LIM can forward its input to other LIMs. Then the receiving LIM can be the connection point to the central billing system.

• Why does the commaseparated look so strange?

  The intension is to create a format that is easy to read, by a computer, where each column carries specific data. Each call is one row and each data in the output uses one column. If a file is imported into Microsoft Excel, the initial comment can be used to identify the data fields as the first rows can be fixed to be the heading.

• Can an individual file be stored in a central place?

  Yes, but this is not recommended because the post processing gets more complex with more files and more commands are needed. Enter the following commands to create one set of files per LIM in the central storage:

  >callinfo_output_set -type file -subtype xml -dbname /var/opt/eri_sn/call_logging/logfile -lim all -output 0 -local

  >callinfo_status_set -output 0 -lim 1 -state on

  >callinfo_output_set -type asyncfile -subtype fp15 -dbname /call_logging/central_1 -server storage.mynet.com:0 -lim 1-output 1 -format "utc"

  >callinfo_status_set -output 1 -lim 1 -state on

  >callinfo_output_set -type asyncfile -subtype fp15 -dbname /call_logging/central_2 -server storage.mynet.com:0 -lim 2 -output 1 -format "utc"

  >callinfo_status_set -output 1 -lim 2-state on

• Why are the files deleted after 6 days? Can data be stored more then 6 days?

  The setup is to prevent the files to grow indefinitely. This way the directory size is controlled and no human intervention is (normally) needed to prevent the disks to be filled up. To store the data more than 6 days, there is a template file that can be started from the cron service each day, under /usr/etc/opt/eri_sn/templates/callinfo_copy_script.sh.

• Can more than one central storage be set up?

  Yes, all outputs can be setup as central storage, but it is recommended to store at least one local copy.

• How can the data, sent on TCP to the central storage, be tested?

  The command callinfo_tcp_print is creating a passive server that will listen to the incoming datastream and present it on the screen. To see the output, make a copy of the output data and paste it directly into the server where the program is running. For example, enter command:

  >callinfo_tcp_print -server localhost -port 1023

• How is a V24 (rs232) output set up?

  A 9 pin - 25pin null modem shall be used, if the system is connected to a 25 pin dumb terminal for testing. The following example is using bitrate = 9600, flow control = none, bits = 8, stopbit = 1, no parity, control signal = DTR/RTS. For example, enter commands:

  >callinfo_output_set -output 1 -type v24 -subtype asb501 -lim all -dbname /dev/ttyS0 -bitrate 9600 -parity no -flowcontrol hw -databits 8 -eol CRNL -record call -format local

  >callinfo_status_set -state on -lim all -output 1

• How is the data sent to a line printer (centronix)?

  The data is sent to a line printer by entering commands:

  >callinfo_output_set -output 1 -type v24 -subtype asb501 -lim all -dbname /dev/lp0 -noinit -eol CRNL -record call -format local

  >callinfo_status_set -state on -lim all -output 1

• How is the naming of the files done?

  The file name is built up from the -dbname, supplied on the command line, by adding a week day number and an extension. The extension is usually .dat or .xml. The week day extension is 0 for Sunday, 1 for Monday ... and 6 for Saturday.

  For example, enter commands:

  >callinfo_output_set -output 0 -type file -subtype xml -dbname /var/opt/eri_sn/call_logging/foobar -lim all

  >callinfo_status_set -lim 1 -output 0 -state on

  If the commands above are entered on a Tuesday, the resulting output file name would be "var/opt/eri_sn/call_logging/foobar.2.xml".