Calls
Call Recordings
Secure Call Recording
4 min
secure recordings beta is available on request via hello\@exotel com and incurs additional charges this feature gives the following capability all your call recordings are stored in a separate secure private s3 bucket within exotel recordings can be accessed only if the user is logged into the exotel dashboard to gain access to recordings via exotel dashboard or api, signed urls are utilized with a short ttl (time to live) another customized way to access the secure recording is ip based whitelisting where the url can be accessed only behind certain ip addresses to access such recordings via api, refer to bulk call details api and use the optional parameter 'recordingurlvalidity' which will set the time in minutes for which the url can be accessed the 'recordingurlvalidity' value can be set in integer (min 1, max 1440) and the default is set to 30 voicemail recordings and call recording will go inside an account specific folder, wherein for secure recording enabled accounts, this folder would be in a secure bucket, for other accounts it will be in unsecure bucket limitation if this is enabled for an account, recordingurl in reports, passthru, and single call details api will not be playable presigned recording url we have another mechanism to access call recording urls through the signed url approach it is an account level feature and once enabled will start sending an extra parameter of “ presignedrecordingurl ” which will contain the signed recording url, in the api response of get call details api and get bulk call details api the signed recording url will have a ttl (time to live) associated with it and allow access to the signed recording urls for a limited time period by default, this will be set to 5 minutes at the account level this value can be modified between 5 minutes to 60 minutes at the time of enabling the feature for a particular account how to modify ttl at per api request level? in order to give granular control at the api request level, we have introduced a new query parameter in get call details api and get bulk call details api “ recordingurlvalidity ” this query parameter accepts an integer value equal to or between 5 and 60, and overrides the account level configuration for the “ presignedrecordingurl ” returned in the api response, the ttl will be set to the value passed in the “ recordingurlvalidity ” parameter parameter name description value accepted exceptions recordingurlvalidity this parameter will return a presignedrecordingurl in the response for both the get bulk call detail and get call detail apis, with the ttl specified in minutes max value that can specified is 60 i e 1 hr default value 5 mins (if the parameter is not specified) an integer equal to or between 5 and 60 if the value is greater than 60 or less than 5 then it will return a 4xx error how to enable? talk to your account director or cxm and get it enabled alternatively, raise a request to hello\@exotel com important note the recordingurl parameter contains the call recording url which will continue to be accessed only through either authentication (api key & api token) or ip whitelisting the presignedrecordingurlthe parameter contains the same call recording but with a signed url, accessible for a time period equivalent to default ttl or the one set in the api request through the parameter presignedrecordingurlvalidity
🤔
Have a question?
Our knowledgeable support team and an awesome community will get you an answer in a flash.
To ask a question or participate in discussions, you'll need to authenticate first.