[Serusers] Re: [Serdev] SIP Stack development

Hi Alan, See inline. Alan Basinger wrote: :-) Sure, I realize that lack of documentation can be replaced (partially and only temporarily) by responsive support on mailing lists. It is also a way to establish the actual scope of documentation work. Aha, I recognize the name now :-) Without knowing the details of the draft, I have the following comments: * In general you want your servers out of the rtp path (i.e. direct media between UAs), in fact, ser is never in the rtp path. However ser is very good at doing message processing, forwarding and all sorts of "tricks" * RTP may be handled by three separate software components: rtpproxy, mediaproxy, and sems (mediaproxy is not an iptel.org project, the others are). SER modules (nathelper and mediaproxy) are used to communicate with these external components (locally or over udp) and for mangling the SDP payload * Your measurements will probably need to follow the media path of a normal session. If not, you will not be able to measure for example real latency on your ex. rtpproxy server(s). SEMS is a very good general-purpose media server, while rtpproxy/mediaproxy are more dedicated for proxying of rtp for NAT-purposes etc * Hence, you probably need to implement sdp loopback intp the rtp handling component. SEMS may be the easiest way due to its very modular and powerful plugin interface (it's also a B2BUA). However, as sems don't stay in the media path except in conferences etc, you don't really measure "real world..." * I suspect you can create a ser module (or extend nathelper) that implements the basic loopback stuff using rtpproxy without touching rtpproxy (too much) The basic concepts are still relevant. It has not been updated to cover to the attribute value pairs and the selects. We are currently focused on the user documentation for the next release, but we are debating what the next steps are. A how-to for module development is already on the list, possible with a retouch of the old developers guide. You can start out with one of the simpler modules (like textops or dispatcher) and modify to your needs. Understand the plugin interface, lumps and shared memory, and you are pretty much there ;-) :-) g-)