With Telavox you're able to record all of your calls with our feature that is simply called Recorded calls.
Telavox normally stores all of your recorded calls for 2 years and during this time you can freely listen to the recordings, download them and delete them if you have the proper permissions for it.
If you would like to save your recordings for longer than 2 years, or if you just want the files to be saved and accessible locally on your side you can do this by setting up an FTP server where Telavox will then be able to upload all of your recordings automatically. If this service would be of interest, please contact the Telavox Support or your contact person.
General product information
- Recorded calls are continuously uploaded multiple times per hour (normally every 10 minutes) to your FTP server.
- All of the recordings on your customer page are automatically uploaded.
- Only recorded calls made or received from a traffic controlled mobile or fixed extension in the Telavox network will be recorded and exported. This means that calls are e.g. not recorded if the extension is roaming/abroad (this is true for recorded calls in general).
- For information regarding the service cost, please ask your support contact.
There are also some requirements for your FTP-server that needs to be fullfilled
- It specifically needs to be either an FTP or an SFTP server (FTPS will not work).
- The server need to have a 24/7/365 uptime.
- Enough free disc space to always allow for new files to be transferred.
- The server needs to have authentication, either in the form of username/password or a key.
- The FTP service may be locked to Telavox IP addresses. In case of changes, Telavox will notify this 3 weeks on beforehand (Telavox IP range is 80.83.208.0/20).
Lastly, when ordering this service from Telavox we need the following information to be able to set this solution up for you:
- Customer ID:
- IP Address:
- Port:
- Username:
- Password:
- SFTP (Yes/No):
- Transfer Start Date:
- Audio File Format (.ogg/.mp3):
- Upload Folder Path:
- Filename Format Version (1/2 – Metadata sent as .json file):
Below you can see some information regarding file names and how they are shown, as well as contents for metadata file contents.
File name version 1
The file extension follows the audio format selected for the export (.ogg, .mp3).
Filename version 1 looks like this:
<your number>_<other party>_<direction>_<date>_<time>_<duration>.<ext>
Where the different file names mean:
- <your number> - the Telavox number the recording belongs to, in E.164 format
- <other party> - the other party's number, in E.164 format
- <direction> - incoming or outgoing
- <date>_<time> - when the call started, yyyy-MM-dd_HHmmss (server time)
- <duration> - length of the recording in seconds
Example: +46401234567_+46701234567_IN_2026-07-21_143000_51.ogg
Good to know
A number that is missing or cannot be normalised is written as unknown.
File name version 2
<recording id>.<ext>
Each recording is also accompanied by a metadata fls:
<recording id>_metadata.json
Example: a1b2c3d4-e5f6-7890-abcd-ef1234567890.ogg and a1b2c3d4-e5f6-7890-abcd-ef1234567890_metadata.json
Metadata file contents
The _metadata.json file contains the call details for the recording it belongs to; the numbers involved, when the call started, how long it lasted, the direction, and whether the recording is owned by a user or a queue. Queue recordings additionally include the queue name and the answering agent.
Note that timestamp is the call start time as a Unix timestamp in milliseconds, and some fields are only present depending on the owner type.
Example:
{
"owning_number": "number that belongs to the account that made the recording",
"other_part_number": "number of the other part",
"timestamp": 1,
"duration_seconds": 1,
"direction": "in|out|unknown",
"owner_type": "queue|user",
"queue_name": "(only set if owner_type is queue)",
"answering_agent_number": "(only set if owner_type is queue)",
"name": ""
}