HI there .... well, it seems that you went far beyond than I did :) I'm willing to try openser just for the sake of trying it. As I said, I only installed it but have not configured it yet. Did you notice any improvements with openser that ser did not provide ? Now I'm running ser 0.9.0 ... I'm willing to try openser 0.9.5. The change, is worth the trouble? About mediaproxy, I said that Openser did not supported it, because I did not see mediaproxy at the modules list of openser. Regards, Lucas -----Mensaje original----- De: Kanakatti M. Subramanya [mailto:mahesh@aptela.com] Enviado el: Jueves, 21 de Julio de 2005 11:59 a.m. Para: Lucas Aimaretto CC: 'Iqbal'; serusers(a)iptel.org; users(a)openser.org Asunto: Re: [Users] RE: [Serusers] openser /ser Hmmm We're running openser in production and its pretty darn stable (now) Couple of things in no particular order a) Openser does support mediaproxy, which is not surprising since the first release is (basically) a repackaging of ser 0.9.3 b) The database structure has changed slightly. I spent some time working on a migration script to move stuff. Basically, you have two options - Leave everything in the existing databases, and just modify the tables appropriately (location and aliases need a new column. look at the faq) - set up the new databases using 'openser_mysql.sh', and dump/restore your ser data into it (use mysqldump, and hand edit the dump file. Note that you'll need to modify your ser.cfg to point at the new stuff) - ok, i lied. there is a third way. I regenerated all our data using our provisioning scripts. it was a good opportunity to sanitize/clean our data. c) Openser will be keeping up with some of the more recent developments - avpops, acc, uac, just to name a few. If you need these, you really don't have much of a choice ;-) d) Stability is an issue (for me, at least). I'd recommend commenting out -DF_MALLOC and uncommenting -DDBG_QMALLOC in Makefile.defs. It worked like a charm for me cheers Lucas Aimaretto wrote: I am looking at upgrading soon, and am looking both at ser and openser, without wanting to open a can of worms, what is better, the features look pretty much the same, not sure if there are any changes to the underlying code, in terms of speed etc etc. I like some of the features in the roadmap of ser, if anyone has migrated from ser to openser, and has any pointers let me know, would be nice to be able to go back and forth, between them both, but I dont think openser cfg is compatible down to some features. I'm facing the same situation. Up to what I've seen, Openser does not support the mediaproxy module. It has some nice features regarding NAT with the use of the rtpproxy module. I have not upgraded yet, but I'll give openser a try. By now, I only installed it, but have not yet configured it. I'll tell you in a couple of days. Regards, Lucas -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/54 - Release Date: 21/07/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/54 - Release Date: 21/07/2005

On 07/21/05 18:45, Iqbal wrote: there is not too much to optimize in terms of performance in ser/openser right now. But there are some minor ones in openser, e.g., in development branch -- many new request methods have now id and you can use is_method() from text ops to do integer comparison instead of ignore-case string comparison as it is in 'if(method=="xxx")'. Another one is 'return' and 'exit' which avoid complex scripting statements to exit from script. Also, the 'switch' statement is faster than a chain of "if" statements (anyhow this is related to 'return'). The big improvements are in terms of new features. Just take a look at roadmap and news in the web site or in ChangeLog file. Daniel