1. On the Admin page, click Accounts.
2. Select an account from the Accounts page and click Edit.
3. Click Archival Configurations to expand the Archival configuration.
4. Select the Archival Location entry on which you are enabling checksum validation.
5. Click Advanced Configurations.
6. Set the Checksum field to MD5.
7. Click Update.
   If a checksum violation occurs, the Recording Details page displays displays an error.
8. Once MD5 Hashing is enabled, you may retrieve the checksum on new recordings. Using an authorized valid token, make a FACE details request. For example:

   $ curl -k -X GET "https://<face_ip>:8443/Face/audioRecording/details?token=<token>&filename=<file_name>

   The following is a truncated sample response:

   <?xml version="1.0" encoding="UTF-16"?>
   
   <result><code>0</code><message>ACK</message><recording>
   ...
   <checksum>5941ee64142e6eb45dfaeef23203cf54</checksum>
   <checksumMismatch>false</checksumMismatch>
   <customDataSets/>
   <siprecDataSets/>
   <dtmfDigits/>
   </recording>
   </result>

1. On the Recordings page, select the Recording you are archiving and click Details.
2. Click File Location.
   The Archival Status and Archival Remarks fields provide information about the Archival of a specific recording.

1. Select the "Source" Location in the "Update" form. This may be the RSS's "Primary" Location, or another Location specific to your environment.
2. Select the "Destination" Location, in the "Update" form. This could be the RSS's "Secondary" Location, or another Location specific to your environment.
3. Click Update.
4. Confirm, using the Recording Detail page's File Location section, with a recording made on an Account not specifically configured for Archival.
   

1. Access the Recording Details page.
2. Click the File Location section.
   

   The Archival Status and Archival Remark comments provide information about the recording's Archival.

   Note:

   Only converted and wav formatted recording files will be archived to the destination location if the location type is SFTP.
3. The Administrator may use the Reset button to resolve a problem in the architecture and attempt Archival again for the recording.

   Note:

   Invalid permissions of the destination directory for the Archival process user or Archival SFTP client user are a common source of Archival failures. For example, invalid SFTP credentials yield an Archival Remark reason of "Archive is Aborting due to unable to establish SFTP Session for the Location".

1. On the Admin page, click Accounts.
2. Select an account from the Accounts page and click the Edit button.
3. Click Route Defaults to expand the route default information.
4. Click Recording Defaults to expand the recording default information.
5. Route Mode—Select the type of recording you want this account to perform by default. Valid values are:
   • Standard (SIPREC)—ISR records as the Session Recording Server (SRS) in a SIPREC architecture.

   • Record and Save—The ISR records calls and only saves them if the Record and Save on DTMF key (see Record and Save Mode Defaults) is pressed by one of the parties on the call. If no key is pressed, the recording is automatically discarded. When you select this option, the Percent to Record, Route Can Record, and Default Recording State parameters become grayed-out.

6. Recording is—Select whether or not calls on this route are recorded. Valid values are:

   • Yes (default) - Recording is enabled for all calls on this route.

   • No - Recording is disabled for all calls on this route.

7. Percent to Record—Specify a value for the percentage of calls to record on this route. Default is 25. Valid values are:

   • 0 to 100

   Note:

   When a session is not recorded based on this value, the ISR replies to unrecorded INVITEs with a 412 response code, logs the rejected session, and adds the rejected session to the call statistics table.

   When this value is set to 0, the ISR remains connected and available for ad-hoc API recording for all sessions. When you set this value to 0 and update your ISR, the ISR Dashboard provides the following message:

   Percent To Record has been set to 0%. Each session is accepted and remains active for ad-hoc recording. To reject sessions due to percentage-based recording, the value must be greater than 0%. 

8. Always Record As Raw RTP—Select Yes when multiple transmission codecs are present in a session. If set to No with multiple transmission codecs present in a session, the ISR does not record the call properly.
9. Codec profile Name—Specify the associated codec profile you want to assign to this account.
10. Record DTMF—Select whether routes for this account record DTMF digit presses by default. The default value is Use System Account's Setting.

1. Allow Editing of Agent ID?—Select whether or not you want users for this route to edit the Agent ID for a recording. Valid values are:

   • Yes - Allow editing of Agent ID for a recording.

   • No (default) - Prevent editing of Agent ID for a recording.

2. Allow Editing of Rating?—Select whether or not you want users for this route to edit the Rating assigned to a recording. Valid values are:

   • Yes - Allow editing of rating for a recording.

   • No (default) - Prevent editing of rating for a recording.

3. Allow Editing of Completed Transaction?—Select whether or not you want users for this route to be able to indicate that a recording represents a complete transaction. Valid values are:

   • Yes - Allow editing of completed transaction information for a recording.

   • No (default) - Prevent editing of completed transaction information for a recording.

4. Allow Editing of Notes?—Select whether or not you want users for this route to edit the Notes specified for a recording. Valid values are:

   • Yes - Allows editing of notes specified for a recording.

   • No (default) - Prevent editing of notes specified for a recording.

When the Route Mode is set to Record and Save (see Recording Defaults), you can set the DTMF key that indicates the recording is to be saved. If any other key is pressed, or no key press is received, the recording is discarded.

To set the record and save mode defaults:

• Record and Save on DTMF—Select the type of keypress that allows the caller to save their recording from their phone’s keypad. This parameter allows you to assign a specific DTMF key (keypress), that when pressed by the caller, stores the recording at their location. The value dtmf-disableddisables this feature. Valid values are:
  • dtmf-pound # (default)
  • dtmf-star *
  • dtmf-0
  • dtmf-1
  • dtmf-2
  • dtmf-3
  • dtmf-4
  • dtmf-5
  • dtmf-6
  • dtmf-7
  • dtmf-8
  • dtmf-9
  • dtmf-disabled

1. Session Capacity—Enter the maximum number of sessions to assign by default to new routes for the account. Default is 24. Valid values are:

   • -1 to 999999999 (must indicate total number of licensed sessions)

   • -1 indicates no limit (default)

   • The maximum session limits for an Account are subject to your licensing agreement.

   • The maximum session limit data is included in the Usage and Billing Reports. For more information about generating reports, see Managing Reports.

2. Additional Burst Session Capacity—Enter the number of additional call recording sessions to assign by default to routes for the account. These are only used after the maximum number of sessions has been depleted. Default is 6. Valid values are:

   • -1 to 999999999 (must indicate total number of licensed sessions)

   • -1 indicates no limit (default)

   • The additional burst session limits for an Account are subject to your licensing agreement.

   • The additional burst session data is included in the Usage and Billing Reports. For more information about generating reports, see Managing Reports.

3. Click Update to save the default route parameters. The Edit Account page displays.