meaningful file name format for call recording
- Thread starter mingtuck
- Start date
- Status
There is some sort of facility to do this in later versions, maybe someone else has more info, I have not tried it yet. For me personally, the UUID is just fine, I didn't used to think that way but any other way ends up just as messy.
There are usually much cleaner ways of achieving your goal.
There are usually much cleaner ways of achieving your goal.
It really depends on what you are trying to achieve, it would be relatively easy to write some sort of exporter that added a file that mapped different fields or even renamed them on export.
In some scenarios I export the cdrs to another server and have a read only copy of the DB and users can just log into that instance to listen to recordings.
In some scenarios I export the cdrs to another server and have a read only copy of the DB and users can just log into that instance to listen to recordings.
We has this put in Version 4.2 *** Not tested in latest version ****
This created a copy of the call recordings, renamed them to the logic you descibed and saves them in seperate area. This way the original was also still in fusion and could be searched via the UUID. At the time it was a big thing but like Digi suggests this turns into an extra job maintaining. Also the UUID / Access via Fusion is somthing weve manage to sell as another layer of security ie without Fusion its next to impossible to locate call recordings etc.
This created a copy of the call recordings, renamed them to the logic you descibed and saves them in seperate area. This way the original was also still in fusion and could be searched via the UUID. At the time it was a big thing but like Digi suggests this turns into an extra job maintaining. Also the UUID / Access via Fusion is somthing weve manage to sell as another layer of security ie without Fusion its next to impossible to locate call recordings etc.
- Status