Loading Profile...
CallSid access during call session
maybe missing something here. . .
In order to access recordings made from incoming calls, I'll need the CallSid.
Is there a way access that during the call session to store it.
If not, then it seems the only way to get it is by requesting the call list.
if I only want calls that I haven't processed yet, what is the favorite methodology for getting that list?
In order to access recordings made from incoming calls, I'll need the CallSid.
Is there a way access that during the call session to store it.
If not, then it seems the only way to get it is by requesting the call list.
if I only want calls that I haven't processed yet, what is the favorite methodology for getting that list?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi mterenzio,
We send the CallSid as an http param with each request we make to you during the call. You should be able to read it from your application.
As far as looking up recordings, we also post a parameter "RecordingUrl" to the action url of the Record verb when each recording has completed. This parameter contains the full url to access the recording, so you dont need to worry about assembling it yourself.
-john -
-
Inappropriate?Hi mterenzio,
Actually, it's an embarrassing inconsistency in our API at the moment, but the param we send in each HTTP Request is called "CallGuid", not "CallSid." It's embarrassing because we call it a CallSid in most other places in our API.
http://www.twilio.com/docs/api_refere...
We should send both parameters (CallSid and CallGuid) to avoid confusion, and try to phase out CallGuid in a future API version.
Sorry for the confusion.
-jeff
EMPLOYEE
EMPLOYEE
