nateastle
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by nateastle
-
-
yes I have which is useful but I am not sure what url to post / put to. I have tried this as well: https://vodia.com/documentation/csta_api but it doesn't have any information on setup or endpoint to post things to.
-
yes, I am wanting to blind transfer a call through an api. I am trying to build a receptionist dashboard so a receptionist can see who is on calls and which people are available so she can transfer calls to the person. I looked through the rest documentation that you posted but was unable to find a rest call to do that. I think there is a way to do it through web sockets but it requires a cookie which complicates things and would not work. I found documentations about CSTA located here https://vodia.com/documentation/csta_api which would probably work but I am unsure what the url is to send events to.
-
It appears all the links are broken. I know this is a long shot but do you still have these files?
-
I am developing a web interface and would like to be able to transfer an active call. I found a topic about CSTA in the forums but it didn't get me anywhere. I am wondering if there is something where I can give the active call id and be able to transfer it.
I am using the remote_call.htm right now but the workflow isn't user friendly as the person has to answer the phone in order for the call to transfer.
-
Thanks, what I am trying to do is get active calls through an api instead of websockets as cookie authentication messes things up between the pbx website and my application's website. Do you know if there is a rest api for this instead of websockets? The vodia interface uses web sockets. I have looked into the 2.0 rest documentation but they only have a web socket example.
-
I am using 57.0 of the pbx and am trying to use the Soap API to get access to the database. However, I do not see the document {domain}/soap.xml. I am wondering if this functionality was removed and everything has to go through the 2.0 api or if we can still have access to the old soap api as found here: http://wiki.snomone.com/index.php?title=Access_to_the_Database
Nate
-
I too am running into this issue. I have found that if I login to the portal then create a connection then it will work as I have a cookie setup. However, if I do not do this then I get the same issue as voltier. I am wondering if there is a query parameter we can pass in on the connection instead of relying on the cookie? The cookie does not work across different domains.
However, I do have an example of the web sockets working you just need to login through the login interface and set a session in a cookie on the same domain as your pbx.
ie: document.cookie = "session={apikeyfromlogin};path=/;domain={pbxdomain.com}";
After that your code should work. Not sure if you are still having problems but this should point you in the right direction if you still need help.
-
that is the api I am talking about. The problem is I do not have a way to go from a cdr that I am consuming to finding the recording through the api. The only thing the cdr's give is the RecordLocation and the only way to find the recording is through an id.
-
I am consuming cdrs from various pbx's around the world. I am trying to take the call recordings and transform them into mp3's, however, the cdrs only provide the location of the call and the api only takes in an id. Is there a way to look up the recording based on location of the call or by cdr id or is there a way to determine which call leg goes to which recording through the api?
Like according to the documentation:
/audio.wav?type=recording&id=110859
it would be nice to have something like:
/audio.wav?type=recording&call_id=d33cfa1e@pbx
or
/audio.wav?type=recording&record_location=recordings/20160731/144453-o-8016280671-9022.wav
API to transfer an active call
in SOAP
Posted
Which I am willing to do however, I am not that familiar with how CSTA works or what endpoint I need to hit on the PBX or authentication to use in order for it to work and it doesn't appear to have documentation in the 2 links on how to get it configured.