Hello,
I want to announce the availability of the first version for openser devel guide, online at:
http://www.asipto.com/pub/openser-devel-guide/
Written together with Elena-Ramona Modroiu, the tutorial approaches the important components of openser: shared memory, locking, pseudo-variables, transformations, mi commands, statistics, db api, timer, module development a.s.o.
Hopefully, the guide will help new developers to understand easier the internals of openser and contribute back new code or improvements to existing code. Has a set of examples and references to the code to be able to learn quicker how to use the APIs.
The document is under polishing process towards clean docbook and pretty printing (pdf) format, then the sources will be included in the openser repository to be more accessible for improvements. It will be a continuing work-in-progress document, please report any error you find there.
It is also mirrored at: http://www.openser.org/docs/openser-devel-guide/
Cheers, Daniel
El Monday 07 April 2008 13:38:41 Daniel-Constantin Mierla escribió:
I want to announce the availability of the first version for openser devel guide, online at:
http://www.asipto.com/pub/openser-devel-guide/
Written together with Elena-Ramona Modroiu, the tutorial approaches the important components of openser: shared memory, locking, pseudo-variables, transformations, mi commands, statistics, db api, timer, module development a.s.o.
Hopefully, the guide will help new developers to understand easier the internals of openser and contribute back new code or improvements to existing code. Has a set of examples and references to the code to be able to learn quicker how to use the APIs.
This is really a nice new, and a good excuse to programm XD
Thanks a lot.
El Monday 07 April 2008 13:38:41 Daniel-Constantin Mierla escribió:
please report any error you find there.
A mini-bug:
2.3. SIP Message Processing The execution of OPENSER configuration file is triggered when receiving a SIP message from the network. The processing flow is different for a SIP request or a SIP message.
Maybe there should be "The processing flow is different for a SIP request or a SIP **response**" ? XD
El Monday 07 April 2008 13:38:41 Daniel-Constantin Mierla escribió:
please report any error you find there.
Other bug:
Figure 2.3. SIP Reply Processing
There appear at the figure top: "SIP REQUEST RECEIVED" "EXECUTE ROUTE[0]"
Shouldn't it be: "SIP RESPONSE RECEIVED" ?
Regards.
Thanks Iñaki !
The bugs were fixed.
Regards, Ramona
Iñaki Baz Castillo wrote:
El Monday 07 April 2008 13:38:41 Daniel-Constantin Mierla escribió:
please report any error you find there.
Other bug:
Figure 2.3. SIP Reply Processing
There appear at the figure top: "SIP REQUEST RECEIVED" "EXECUTE ROUTE[0]"
Shouldn't it be: "SIP RESPONSE RECEIVED" ?
Regards.
-
Daniel-Constantin Mierla -
Elena-Ramona Modroiu -
Iñaki Baz Castillo