Page Comparison

The Avaya Contact Recorder (ACR) creates audio files of calls that have occurred on your telephone system.  Providing the ACR recordings are no longer taking place, these recordings can be migrated to VFC using the ACR Import Source.

The ACR Import Source migrates both ACR-only and ACR+15.2 systems using the native ACR API.

Both encrypted and unencrypted ACR recordings can be migrated by the ACR Import Source.

...

...

Step 4 - Click Save to save the settings

Image Removed

Lua CDR Customisation

As historical recordings may include changes in field layout, data anomalies caused by software bugs and ultimately may not be required due to business re-organisation, embedded Lua scripting has been provided to control the migration process.

Use of a Lua script is optional, if not required, the Lua CDR Customisation field should be left empty.

For more information about Lua, refer to https://www.lua.org

Lua CDR Customisation requires the use of a template:

• The srcValues table first item value is "xml" and the second item value is one record of the xml string returned by the ACR Layout query.  This query may return many records and the Lua Customisation script is called for each.
• The dstValues table lists the fields which the Lua CDR Customisation Script may return.  Each value to be returned must replace the name of the field passed in the dstValues table.  

function compute_cdr(srcValues,dstValues)
   return dstValues
end

Presently, the field names are hardcoded as follows to match the ACR Template, but they could be generic in the future.

inumIndex = 1
startedatIndex = 2
durationIndex = 3
udfsIndex = 4
otherpartiesIndex = 5
ownersIndex = 6
switchcallidIndex = 7
directionIndex = 8
skillsIndex = 9
agentsIndex = 10
servicesIndex = 11
srcNumberIndex = 12
dstNumberIndex = 13

In order to parse the xml string passed in field 2 of the srcValues table, it is advisable to use a Lua XML parsing library such as Xml2Lua https://github.com/manoelcampos/xml2lua

Access to xml2Lua is then possible using this line of Lua:

package.path = "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/vcpkg/packages/lua_x64-windows-static/xml2lua161/?.lua"

Xml may then be parsed within the Lua CDR Customisation script using the following pattern:

local xml2lua = require("xml2lua")
local handler = require("xmlhandler.tree")
handler=handler:new()

local parser = xml2lua.parser(handler)

parser:parse(srcValues[xmlIndex])

...

While testing the Lua CDR Customisation script, it is possible to write to a local log using the following Lua function or if preferred in a self-contained single-step debug environment using https://studio.zerobrane.com/

function log(message)
file = io.open("C:/Program Files/Verba/work/cdrimport/luaCustomCDR.log", "a")

-- sets the default output file as test.lua
io.output(file)

-- appends a word test to the last line of the file
io.write(os.date("!%c") .. " - " .. message .. "\n")

-- closes the open file
io.close(file)
end

Separate libraries may be developed in their own file to aid readability and then referred to by the main Lua CDR Customisation Script, for example

lib = require "DemoLib"

File: "DemoLib.lua"

local demo_mod = {} -- The main table

function demo_mod.Split(s, sep)
local fields = {}
local sep = sep or " "
local pattern = string.format("([^%s]+)", sep)
string.gsub(s, pattern, function(c) fields[#fields + 1] = c end)
return fields
end

return demo_modImage Added

Import Policy Configuration

...

...