Skip to main content

Create and Verify SFTP Accounts

Open SFTP Server > SFTP Action Accounts to create the destination that CUCM or another file source will use. A dedicated account keeps credentials, actions, monitoring, and retention settings scoped to one workflow.

Screenshot of the Essentials+ SFTP Action Accounts page showing three fictional CUCM backup and CDR archive accounts with status, action counts, paths, and storage usage

Essentials+ — three fictional SFTP Action Accounts. Community uses the same account workflow with a two-account limit and seven days of history.

Create a Dedicated Account​

  1. Select New Account.
  2. Enter a unique Username for the uploading system.
  3. Enter a strong Password.
  4. Add a Description that identifies the cluster, source, or purpose.
  5. Leave Account Status enabled when the source is ready to connect.
  6. Select Create Account.
Screenshot of the Community and Essentials+ New SFTP Account dialog with username, password, description, and enabled status fields

Community and Essentials+ — create an SFTP-only account for an upload source.

Use separate accounts for production backups, lab backups, and unrelated CDR archives. This makes failures, retention decisions, and credential rotation easier to isolate.

Connect CUCM DRS​

In the Cisco Disaster Recovery System, create or edit a network backup device with:

  • Host Name/IP: the Call Telemetry appliance address.
  • Path: /.
  • User Name and Password: the new SFTP account credentials.
  • Number of backups to store: the number required by your recovery policy.

Save the device, associate it with the intended DRS schedule, and run a backup while you can observe Call Telemetry.

Verify the First Workflow Run​

Select the account username and open Run History. Confirm that the expected file appears and each applicable On Success action reaches Succeeded. Validate optional On Failure notifications separately with a controlled failed-run scenario.

Screenshot of Essentials+ SFTP account Run History showing detailed CUCM Backup Validation and Amazon S3 upload actions for fictional backup files

Essentials+ — detailed validation and cloud-action run history.

warning

If an action fails, use the file, action type, event, and timestamp in the row to identify the affected step. Fix the destination or notification configuration before relying on the schedule.

Continue With Automation​

The account can receive files before actions are added. Validation and delivery begin after you configure the relevant success workflow; add a failure workflow when the operation also needs failure notifications.

Automate Backup Actions →

Last updated on by Call Telemetry