Issue 194 in restcomm: High Priority Rest API Defects with RestComm in New AWS Marketplace Instance

0 views
Skip to first unread message

rest...@googlecode.com

unread,
Oct 3, 2013, 4:14:42 PM10/3/13
to restcomm-issue...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Version-1.0.0.FINAL

New issue 194 by lylepr...@gmail.com: High Priority Rest API Defects with
RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=194

- Controlling Live (in-progress) calls using the Rest API, is not
supported :(. This is an extremely important feature.
----- Error: "The specified HTTP method is not allowed for the requested
resource"

- There doesn't seem to be any way to filter or paginate the Call List
Resource. It just returns every call that has ever hit the box! What if a
RestComm account had millions of calls? It would probably crash...
----- Use Example: there is no way to filter the Call List Resource to,
for example, only show LIVE (in-progress) calls.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

rest...@googlecode.com

unread,
Oct 3, 2013, 4:23:26 PM10/3/13
to restcomm-issue...@googlegroups.com

Comment #1 on issue 194 by lylepr...@gmail.com: High Priority Rest API
Defects with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=194

Posting updates to existing, in-progress calls is necessary to dynamically
alter what a LIVE Call is doing.

Simple examples:
- Move a caller that is currently in a conference out of the conference
room.
- Hang Up a live Call

Additional Details:

Sending a POST to an existing Call SID via the Rest API is not supported.

Example in Python:
request =
requests.post("%s/restcomm/2012-04-24/Accounts/%s/Calls/%s.json" %
(settings.RESTCOMM_URL, settings.RESTCOMM_ACCOUNT_SID, self.twilio_sid),
params={'url': "%s/restcomm/outgoing/update/" % (settings.SITE_URL)},
auth=(settings.RESTCOMM_ACCOUNT_SID, settings.RESTCOMM_ACCOUNT_TOKEN))

The above returns "The specified HTTP method is not allowed for the
requested resource".


-Lyle

rest...@googlecode.com

unread,
Oct 3, 2013, 4:31:30 PM10/3/13
to restcomm-issue...@googlegroups.com

Comment #2 on issue 194 by lylepr...@gmail.com: High Priority Rest API
Defects with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=194

Concerning the pagination/filtering of Calls:

Being able to filter by date or call status is important especially in
conjunction with LIVE Call modification.

For example:
If I want to Hang Up all live (in-progress) calls, I need to be able to hit
the Call List Resource and filter by "status=in-progress"

rest...@googlecode.com

unread,
Oct 8, 2013, 7:00:35 PM10/8/13
to restcomm-issue...@googlegroups.com

Comment #3 on issue 194 by lylepr...@gmail.com: High Priority Rest API
Defects with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=194

Hi Guys! Any update on this?

rest...@googlecode.com

unread,
Oct 10, 2013, 11:25:05 AM10/10/13
to restcomm-issue...@googlegroups.com
Updates:
Status: Accepted
Owner: gvage...@gmail.com

Comment #4 on issue 194 by gvage...@gmail.com: High Priority Rest API
Defects with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=194

Working on filtering and pagination issue.
Reply all
Reply to author
Forward
0 new messages