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
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
