...
- Server: this is the main class. It extends the Jetty Server and starts in addition all SIP components.
- SipHandler: base interface for all SIP handlers.
- SipAppContext: derivation of WebAppContext which represents a SIP Servlets application.
- SipContextHandlerCollection: use to manage all deployed SIP applications. Responsible for the selection of the appropriate SIP application when handling an initial request. Application selection is actually performed by the Application Router.
SIP Processing
Cipango architecture originally evolved from a traditional (non-SIP) call processing platform we developed in a former life. As a result, SIP processing in Cipango remains very call-centric which is something we wanted to keep as it has proven a sound approach to simplicity, performance and reliability.
One of Cipango goals is to be able to support various SIP processors (SIP Servlets, load balancers ...). To support this goal, the SIP layer is organized as a pipeline of handlers. The first handler to be called after a message has been received is the Server which then delegates the actual processing to a configured chain of handlers.