The SipXrest container - a restful service container for exporting REST interfaces to sipXecs call control services

As sipXexs sipXecs grows to integrate with other products, there is a need to export call control services using a web services model so that these services may be invoked by other components and from other products. An example of such a service would be the third party call controller. Call control services are traditionally written in sipXecs as stand alone processes. SipXrest does not aim to supplant this model. Rather, what we aim to do is to provide a web services interface to interact with such call control services that are useful to export for business integration purposes. Web services (and recently REST-based services)are exported by sipXconfig for configuration functions. We aim to do something similar for call control functions. This has worked well thus far by placing such integration code into sipxconfig. SipXconfig thus exports the third party call controller as a REST service in SIPXECS 4.0. However, as the number of these services grows, so do the associated problems of putting every bit of call control integration functionality into sipXconfig. As the complexity of the product grows, so does the number of such services and hence so do the number of integration issues.

...