Re: [Ekiga-devel-list] Need help to setup a test system

2008-07-29 Thread Julien Puydt
Damien Sandras a écrit : Le lundi 28 juillet 2008 à 21:41 +0200, Julien Puydt a écrit : Hi, I would need a way to setup ekiga with something in front of it, which will send presence/status information on a pretty high rate. The goal is to trigger the crash in sigc::trackable much, much more

Re: [Ekiga-devel-list] Need help to setup a test system

2008-07-29 Thread yannick
Hi Snark, If you have some times, could you document how to setup this tool for testing purpose here: http://wiki.ekiga.org/index.php/Pre-release_test ? Maybe we should define some testing protocol using tools like this one. I personally plane to do intensive testing from mid august to mid

Re: [Ekiga-devel-list] Need help to setup a test system

2008-07-29 Thread Julien Puydt
Damien Sandras a écrit : Le mardi 29 juillet 2008 à 10:05 +0200, Julien Puydt a écrit : Damien Sandras a écrit : Le lundi 28 juillet 2008 à 21:41 +0200, Julien Puydt a écrit : Hi, I would need a way to setup ekiga with something in front of it, which will send presence/status information on

Re: [Ekiga-devel-list] Need help to setup a test system

2008-07-29 Thread Julien Puydt
Julien Puydt a écrit : Running : sipp -sn uas -aa is supposed put sipp in server mode (-sn uas), and answer ok to everything (-aa)... Not sure uas is what I thought it was... I have to dig further. Snark ___ Ekiga-devel-list mailing list

[Ekiga-devel-list] Need help to setup a test system

2008-07-28 Thread Julien Puydt
Hi, I would need a way to setup ekiga with something in front of it, which will send presence/status information on a pretty high rate. The goal is to trigger the crash in sigc::trackable much, much more easily, to kill it. I was thinking a pseudo-server could do the trick (ie: a false

Re: [Ekiga-devel-list] Need help to setup a test system

2008-07-28 Thread Damien Sandras
Le lundi 28 juillet 2008 à 21:41 +0200, Julien Puydt a écrit : Hi, I would need a way to setup ekiga with something in front of it, which will send presence/status information on a pretty high rate. The goal is to trigger the crash in sigc::trackable much, much more easily, to kill it.