Hi Elias,
(also fwd. to "users" to let everybody know)
thanks for the contribution. I think that the new SEAS and PERL modules will give a lot more options when comes to integrate OpenSER with other application and what is more important , they will allow non-C extensions :) !!
I will generate the docs and place them on the web also. BTW, are some default application that I can give a fast try? I would like to test some real-case apps to get the feeling.
Regards and Merry Christmas, Bogdan
Elias Baixas wrote:
Hello everybody,
I just submitted a new module, called SEAS (which stands for Sip Express Application Server). This module allows a third party to create an Application Server and connect it to OpenSER to interoperate seamlessly. This permits the Application Server to trigger actions on OpenSER, such as sending out a request, or replying a UAS transaction, in some way similarly to what can be achieved using fifo, or MI commands "t_uac_dlg" and "t_reply", but SEAS provides a much richer API to this kind of tasks. The module also allows OpenSER to notify the Application Server when requests/responses come in, and then transfer the control over the incoming request entirely to the Application Server. Furthermore, the module implements a binary protocol that transfers the SIP message along with information abouth the structure of the message's headers (ie. where each header starts, and how long it is), so the Application Server doesn't need to reparse the entire SIP message, thus improving Application Server's performance very much. The SEAS protocol also carries information about the transaction being processed at OpenSER for every message, so that the Application Server doesn't need to implement all the SIP-transaction machinery, thus actually profitting from the highly optimized TM module at OpenSER.
The Application Server can be programmed in any language, because the SEAS module comunicates with it through a TCP socket.
At the moment, SEAS module has been written to work with an Application Server developed by VozTelecom. It is called WeSIP and can be downloaded freely from http://www.wesip.eu . WeSIP is an implementation of the SipServlet and HttpServlet standards, so it allows a programmer to easily implement Web-Sip converged applications (such as Click2call). WeSIP is programmed entirely in Java, so you have all the tools and facilities from Java and J2EE available to program SIP applications, while already using OpenSER to process the SIP messages and transactions at the low level, thus profitting both from the high performance of OpenSER, and the high-level SIP-Application programming framework which is SipServlet and the JAVA languaje.
I hope this module will help create new usage scenarios for OpenSER, allowing it to provide high-level Telephony Applications to users.
The module is still in a alpha stage, but should be able for production shortly.
best regards,
Elias Baixas
VozTelecom, Sistemas http://www.wesip.eu http://www.voztele.com
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Elias,
I manage to put the doc on the web along with the pictures...pretty nice ;).
http://www.openser.org/docs/modules/1.2.x/seas.html
Juha, looks like the devel section is very well documented.
Regards, Bogdan
Bogdan-Andrei Iancu wrote:
Hi Elias,
(also fwd. to "users" to let everybody know)
thanks for the contribution. I think that the new SEAS and PERL modules will give a lot more options when comes to integrate OpenSER with other application and what is more important , they will allow non-C extensions :) !!
I will generate the docs and place them on the web also. BTW, are some default application that I can give a fast try? I would like to test some real-case apps to get the feeling.
Regards and Merry Christmas, Bogdan
Elias Baixas wrote:
Hello everybody,
I just submitted a new module, called SEAS (which stands for Sip Express Application Server). This module allows a third party to create an Application Server and connect it to OpenSER to interoperate seamlessly. This permits the Application Server to trigger actions on OpenSER, such as sending out a request, or replying a UAS transaction, in some way similarly to what can be achieved using fifo, or MI commands "t_uac_dlg" and "t_reply", but SEAS provides a much richer API to this kind of tasks. The module also allows OpenSER to notify the Application Server when requests/responses come in, and then transfer the control over the incoming request entirely to the Application Server. Furthermore, the module implements a binary protocol that transfers the SIP message along with information abouth the structure of the message's headers (ie. where each header starts, and how long it is), so the Application Server doesn't need to reparse the entire SIP message, thus improving Application Server's performance very much. The SEAS protocol also carries information about the transaction being processed at OpenSER for every message, so that the Application Server doesn't need to implement all the SIP-transaction machinery, thus actually profitting from the highly optimized TM module at OpenSER.
The Application Server can be programmed in any language, because the SEAS module comunicates with it through a TCP socket.
At the moment, SEAS module has been written to work with an Application Server developed by VozTelecom. It is called WeSIP and can be downloaded freely from http://www.wesip.eu . WeSIP is an implementation of the SipServlet and HttpServlet standards, so it allows a programmer to easily implement Web-Sip converged applications (such as Click2call). WeSIP is programmed entirely in Java, so you have all the tools and facilities from Java and J2EE available to program SIP applications, while already using OpenSER to process the SIP messages and transactions at the low level, thus profitting both from the high performance of OpenSER, and the high-level SIP-Application programming framework which is SipServlet and the JAVA languaje.
I hope this module will help create new usage scenarios for OpenSER, allowing it to provide high-level Telephony Applications to users.
The module is still in a alpha stage, but should be able for production shortly.
best regards,
Elias Baixas
VozTelecom, Sistemas http://www.wesip.eu http://www.voztele.com
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Bogdan-Andrei Iancu writes:
I manage to put the doc on the web along with the pictures...pretty nice ;).
http://www.openser.org/docs/modules/1.2.x/seas.html
Juha, looks like the devel section is very well documented.
thanks for the document. based on elias's email, i got an impression that it would also be possible to issue commands from an application to openser (like t_uac_dlg), but after reading section 1.1.1 of the document, looks like it is the other way around, i.e., seas module is the one that invokes application server based on a SIP request in the same way as openser interacts with sems.
-- juha
ps. in my opinion, seams module documentation should only describe how seams module works and the protocol that it uses to communicate with application servers. it may include a pointer to some particular application servers, but description of those application servers should be done elsewhere. so all the java/wesip stuff should be described outside of openser module document.
Hi Juha,
with seas and wesip(or whatever in the future is attached to the module) you can initiate dialogs in a UAC fashion as well as process incoming requests acting as a proxy or a UAS. So it is a kind of bidireccional interface. Info on the architechture can be found at http://www.wesip.eu/mediawiki/index.php/WeSIP_and_Openser. There you find a tutorial(http://www.wesip.eu/mediawiki/index.php/ Tutorial:SIP_Servlet_Programming_model) and some example applications as well (http://www.wesip.eu/mediawiki/index.php/ApplicationsIndex) as well which you'll may find interesting.
Hope it helps
Gines
El 22/12/2006, a las 20:57, Juha Heinanen escribió:
Bogdan-Andrei Iancu writes:
I manage to put the doc on the web along with the pictures...pretty nice ;).
http://www.openser.org/docs/modules/1.2.x/seas.html
Juha, looks like the devel section is very well documented.
thanks for the document. based on elias's email, i got an impression that it would also be possible to issue commands from an application to openser (like t_uac_dlg), but after reading section 1.1.1 of the document, looks like it is the other way around, i.e., seas module is the one that invokes application server based on a SIP request in the same way as openser interacts with sems.
-- juha
ps. in my opinion, seams module documentation should only describe how seams module works and the protocol that it uses to communicate with application servers. it may include a pointer to some particular application servers, but description of those application servers should be done elsewhere. so all the java/wesip stuff should be described outside of openser module document.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Ginés Gómez -
jh＠tutpro.com