Hello,

On 02/05/07 14:14, Klaus Darilion wrote:

On Mon, February 5, 2007 13:02, Daniel-Constantin Mierla said:

...

Hello,

starting with today the development for 1.2.0 is closed. No new features should be added until the release. The next month will be dedicated to testing, integration of submitted patches and fixing reported bugs.

Hi!

Sorry for my late response (skiing) - I wanted to have one (now missing) security related function: dropping responses if there is no ongoing transaction found for this response - even if it is a final response. I know dropping final responses is bad because the transaction stays alive - but if there is no transaction found, then there is no problem with dropping final responses.

you want to that in the assumption that you do only transaction statefull processing. Maybe the behavior of drop for provisional replies can be extended, but this will require some interference with TM in default onreply_route and that will require some changes. Next release should get something new as well :-)

Cheers, Daniel

regards klaus

...

We have a lot of new code to test, your help is very much appreciated. I want to list the major changes you should focus on while testing:

• usage of pseudo-variables and transformations is script

(http://openser.org/dokuwiki/doku.php/transformations:devel)

• TM timers (millisecond accuracy)
• IP blacklists
• DNS failover
• automatic error handling
• flags system (script flags, message flags, branch flags)
• usrloc enhancements (licking system refurbished, database content

optimization via DB fetch support)

• new management interface (mi_fifo, mi_xmlrpc)
• SIP Servlet Java Application server interoperability (seas module)
• PERL AGI (perl module)
• SNMP support via snmpstats module
• Presence support (modules presence, pua, pua_usrloc, pua_mi)
• xmpp IM gateway (xmpp module)
• sip session timer support (module sst)
• accounting clean up
• federation based peering via domainpolicy module

If I forgot something, please contribute.

In addition, great help would be with creating 1.2.0 variants of documentation and dokuwiki pages (where is the case), testing the tools (openserctl, DB creation scripts) and developing scripts to migrate database from 1.1.x to 1.2.0.

To keep track of discovered issues, please register them on the tracker -- it this way you make sure it is not lost in mail threads: http://sourceforge.net/tracker/?group_id=139143&atid=743020

Have nice testing sessions! Your feedback is always helpful!

Cheers, Daniel

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users