New element in call recording XML metadata

If configured, Puzzel delivers your call recording files (WMA, MP3 or WAV) to Puzzel’s (s)FTP server, where you can fetch the recording files, so that they can be stored locally.

Only WMA files have the recording metadata (sessionId, caller's number, queueKey, agentName etc) as an XML-part within the call recording file's File properties, but the same recording XML metadata can be delivered as a separate XML file (for MP3, WAV or WMA).

In the maintenance window Tuesday March 20th, we will update the recording XML metadata format with a new element called fileName in the sessionInformation part.

Since the standard way to read XML metadata is to parse the XML and extract and use the elements that is of interest, this new element should not cause any challenges for you.

The recording XML metadata will be like this when the fileInformation element is introduced:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recordingDetails version="1.0">
  <sessionInformation>
    <sessionId>002b93e0-fe71-4d16-af34-d91a31214d8c</sessionId>
    <sessionStart>2016-11-02T16:50:55.003+01:00</sessionStart>
    <serviceId>10298</serviceId>
    <serviceNumber>21494324</serviceNumber>
    <serviceDescription>My Services</serviceDescription>
    <accessPoint>21492970</accessPoint>
    <countryCode>NO</countryCode>
    <fileName>002b93e0-fe71-4d16-af34-d91a31214d8c_1.wma</fileName>
  </sessionInformation>
  <requestInformation>
    <requestId>467224</requestId>
    <remoteAddress>21498175</remoteAddress>
    <queueKey>Q_PHONE_SALES</queueKey>
    <queueDescription>Phone Sales</queueDescription>
    <vip>0</vip>
  </requestInformation>
  <userInformation>
    <userId>17064</userId>
    <firstName>Kristian</firstName>
    <lastName>Halvorsen</lastName>
    <userName>kristian</userName>
  </userInformation>
  <recordingInformation>
    <recordingIndex>1</recordingIndex>
    <recordingStart>2016-11-02T16:51:00.69+01:00</recordingStart>
    <recordingStop>2016-11-02T16:51:03.307+01:00</recordingStop>
    <ownerType>user</ownerType>
    <ownerTypeId>1</ownerTypeId>
    <ownerId>17064</ownerId>
    <forcedOnQueue>false</forcedOnQueue>
    <forcedOnUser>true</forcedOnUser>
    <recordingSeconds>3</recordingSeconds>
  </recordingInformation>
</recordingDetails>
The sessionId found in the recording metadata is also used in the Raw data records for this call.

 The call recording documentation found here will be updated shortly after March 20th.

Published

Last updated