On Tue, May 8, 2012 at 2:29 AM, Carl Constantine < [email protected]> wrote:
> Ok, well hopefully the docs on this can be updated soon. If not, where can > I find up-to-date information and maybe I will update the docs as I write > code. > You are right, we need to update the wiki doc However, information about conference new api can be retrieved from here http://track.sipfoundry.org/browse/XX-9886 There is a comment that explains how the url looks like and some explanations If you can update wiki doc based on this information and given your testing, would be great! thanks > > Anyway, when I do you suggest, I get the following error: > > HTTP ERROR: 403 > User is not owner of this conference > RequestURI=/sipxconfig/rest/my/conference/test/list > > > This is sort of correct. The conference has no owner, so the > administration of the conference should be the admin user which is what I > used to try to access the command. So in this scenario, how would the admin > user access conference details. It would be nice if this could be done > regardless of the conference owner. > This rest api is addressed to user (has the pattern /rest/my) and apply to user owned conferences What you are suggesting makes sense, but for this to be accomplished we would need a new REST API that applies to admin users (to have the format /<service_name>, so not to contain /my) Here is how admin and user rest apis are distinguished: http://wiki.sipfoundry.org/display/sipXecs/Configuration+RESTful+Service - there are two chapters Admin services and User services > > I would also like to change ownership of the conference to correspond to a > conference chair who can then use commands in the conference instead of the > admin user. > the new Admin conference rest api should be able to do that > > > At any rate, this still comes down to having accurate documentation > available. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Carl B. Constantine, IT Analyst > Server, Network and Telecomm Infrastructure > IT Services > Royal Roads University > 250 391-2600 ext.4975 > fax 250 391-2594 > http://www.royalroads.ca > [email protected] > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of George Niculae > Sent: May-07-12 4:16 PM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] Conferencing web API > > On Tue, May 8, 2012 at 1:57 AM, Carl Constantine < > [email protected]> wrote: > > I have a couple conferences set up for testing purposes similar to > > what is described here: > > http://wiki.sipfoundry.org/display/sipXecs/Conferences > > > > > > > > The Web API here: > > http://wiki.sipfoundry.org/display/sipXecs/Conference+Web+Service, > > says I can send commands to a conference. But if I try to run a > > command, I get a > > 404 error: > > > > > > > > https://user:pass@somehost:8085/conference/test/list > > > > > > > > HTTP ERROR: 404 > > > > /conference/test/list Not Found > > > > RequestURI=/conference/test/list > > > > Powered by Jetty:// > > > > > > > > > > > > Is something not configured correctly? Conferencing is enabled. I can > > actually call the conference from my SIP phone and the conference > > works, but I can't seem to do anything programmatically on it. What am I > doing wrong? > > > > > > > > Also, I want to programmatically change/update the user and/or the PIN > > associated with a conference on occasion, so it acts more like a > > private conference. We just rotate the PIN so it's not the same from > > one conference to the next. Looking at the WEB API I should be able to > > do that do, something like: > > > > > > > > curl --digest -k -X PUT > > https://user:pass@somehost:8085/conference/test/pin/12345 > > > > > > > > But again, that does not work. > > > > > > > > Ideas? Is there some other configuration or file I should be looking at? > > Different port things are running on for the Conference API? > > > > API has been changed and moved on config side and wiki page is not up to > date, you should try something like https://user:pass@somehost > /sipxconfig/rest/my/conference/test/list > and use conf owner / pass to call it. > > George > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
