Filename format for when recordings are stored in ...
# support
v
Hi, Now that Supabase is supported for the storage location, I would like to know what is the format of the files that are stored? For example for call ID 09965e70-a583-4d37-b80b-5d64e65f2c71 after my call I can get the recording URL which now points to https://xdvyfutpnnyavcrcmyxm.supabase.co/storage/v1/s3 which is my supabase storage location and it doesnt have the actual filename any more. I see the file uploaded to my storage on Supabase and it has the name in the following format: 09965e70-a583-4d37-b80b-5d64e65f2c71-1740688042924-adf24216-f9a8-4971-bf6f-fcbba7b92c65-mono.wav I can guess that the first part is the call id and the second is the timestamp. How about the section starting at adf2? Thanks
@Shubham Bajaj
k
Apologies @VahidKowsari for the delayed response.
The filename is constructed with the following parts: - callId - The unique identifier for the call (e.g., 09965e70-a583-4d37-b80b-5d64e65f2c71) - [Date.now](http://Date.now)() - Current timestamp in milliseconds (e.g., 1740688042924) - v4() - A randomly generated UUID using the uuid library (e.g., adf24216-f9a8-4971-bf6f-fcbba7b92c65) - Recording type - Either mono or stereo - File extension - .wav The third section starting with
adf2
is a randomly generated UUID that ensures uniqueness of the file name even if multiple recordings are created for the same call at the exact same timestamp.
v
Thank you @Shubham Bajaj. I was afraid of that. I think that might a little bit of a problem. The server messages back to the server for the end of call recording url we dont get in the URL when using Supabase storage. I just get the supabase storage root and the file just gets copied to the storage location and has this autogenerated UUID in the filename. That makes it hard to figure out what the actual file name is in my app without just matching it by the first part. If the server webhook provided the actual filename (with or without the storage location URL) then I would know what the filename is exactly.
s
@VahidKowsari created an enhancement-ticket for it, and will let you know once it is resolved.