CAS stands for Converged Application Server. It is the controller for the TransferHTTP extension, and I blogged on it sometime ago here. The controller, also known as the proxy, is called CAS because it provides two endpoints (a SIP endpoint for the signalling and services and an HTTP endpoint for the services administration). Below is the User Interface (UI) for setting policies in the work. The policies include web session mobility blocking and forwarding policies. In web session mobility blocking policies, users could add SIP URI they would not want to accept a session transfer from; while in web session forwarding policies, users could forward (i.e. redirect) a session transfer request to any of their PCs.
User's Policies Interface
Below the user’s policies (in the above figure) are registered SIP URIs of the user. Those are the URIs at which the user could be contacted. The log in credentials (SIP URI and password) will be required to connect to the server. Here is the client interface – http://transferhttp.mozdev.org/screenshots.html – where the user will enter the credentials.
I already have a number of things under future work. These include extending CAS to support buddy list with presence and extending the TransferHTTP extension to support an address book.
