Awesome, thanks for the pointers! That definitely cleared up a few things for me on understanding what is going on under the hood.
So right now I figure my plan will be to make a Restlet patterned after the other Rest API resources already there (like AutoAttendantsResource.java) and then hook into the functionality in the same way that the SipXecs admin page classes do (like EditOpenAcdAgentPage.java). From what I can tell that page uses the getOpenAcdContext() method and then calls methods off that (like saveAgent()) to work with OpenAcd. Of course, please anyone stop me if I am going down the wrong path (like if I should be going directly to MongoDB - it just feels like I should be leveraging / honoring the code path through SipXecs since it already has the functionality in its admin pages). Thanks again! D. Chang From: [email protected] [mailto:[email protected]] On Behalf Of Jan Vincent Liwanag Sent: Thursday, March 01, 2012 9:03 PM To: sipXecs developer discussions Subject: Re: [sipx-dev] Tips on adding to SipXecs API to expose Call Center (OpenACD) functionality Hi Dan, sipX integrates with OpenACD by way of the sipXopenacd plug-in. This is an Erlang plug-in that lets OpenACD use the common MongoDB database that sipXconfig and the rest of the sipX components take advantage of. The entries for MongoDB (as well as eventual persistence to Postgres) are managed in sipXconfig. For a head start, take a peek through the MongoDB database "imdb" under the collection "entity". Jan Vincent Liwanag [email protected] On Friday, March 2, 2012 at 5:54 AM, Dan Chang wrote: First, I give the standard caveat that I have just joined the dev mailing list (glad to be here!) and may be missing a lot of history, but from checking I have not found my particular question mentioned. I am interested in adding to the SipXecs API (either RESTful or SOAP) to add access to Call Center (that is, OpenACD) functionality such as adding call queues, adding agents to queues. I was looking for some pointers as to where to start looking in the code (for instance where SipXecs code is that handles OpenACD commands), and any tips on the preferred way to approach it. I had noticed SipXecs seems to handle things for OpenACD independently (such as creation of users vs. agents) and that there is current development to increase integration between SipXecs and OpenACD, so I wanted to go through "the SipXecs way" (for the benefit of the code base as well). But of course warnings that changes are coming or that maybe the idea is not even tenable are also welcome. Thanks again for any insights! D. Chang _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
