-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable recording for Exotel masked calls #661
Comments
@mahalakshme : Should "Record" be set to true for all calls or will it be part of request parameter ? |
@mahalakshme This is temporarily ok to go. We need a followup where we make this value configurable in the exotel configuration. |
@vinayvenu : I verified that the Record parameter accepts the sting 'true' by manually invoking API using postman. |
@ashusvnath commit needs to be also put in 5.1 branch for 5.1.3 release |
@mahalakshme Done |
Using Exotel GET Bulk CallDetails APIs, we verified that the recordingUrl is available for the calls made with this fix. |
Ticket: https://avni.freshdesk.com/a/tickets/3264
AC:
Since the Exotel API has changed without backward compatibility being provided(v1 version of API call we are using has changed) in
callMasking
method set the Record parameter to true.To test:
Test using Exotel credentials available in Keeweb.
Reference:
https://developer.exotel.com/api/make-a-call-api#call-customer
The text was updated successfully, but these errors were encountered: