Hello Alexey,
have you progressed on this one? Could you update us?
Thanks,
Olivier.
On 11/23/06, Alexey Sidelnikov <[EMAIL PROTECTED]> wrote:
Dear all!
I'm using for my work, checking the implementation of the SIP protocol
<<bla-bla-bla>>. Using command line was really inconvinient for me, because
I need to run many different scenarios, changing them, trying to figure out
how the SIP client will process the malformed packets etc. To make it more
easier, I quickly made some simple GUI using VS.2005 / C# / MS.Access.
Please have a look at the screenshot. I think it gives good idea about what
and how this program can do. Basically, I'm just using elementary commands
from SIPp to create XML scenario - just to simplify this routine. You can
keep several similar commands (like sending 200 OK with 100 seconds
registration time, with 3600 registration time etc) and create and manage
different scenarios very easy.
When scenario is ready, it can be executed wtih SIPp (just running console
window and passing SIPp command line to it :)). All commands are simply
glued together to create XML file which is fed to SIPp.exe. No response
besides process exit code can be returned to the program.
Another more complicated feature I recently added is so-called "Tests".
Basically it is the same as scenario - you can
group several scenarios as building blocks together to test some specific
feature of the UAC. But here you can, for example, run several SIPps to
emulate several different calls. The call hold test illustates it: UAC1
(actually this is a mobile phone) calls SIPpp first and, after the call is
established, another SIPp instance is started and call the mobile phone.
The user of the phone should see a popup saying "new call. Accept/Reject",
and when he accepts it, the first call is put on hold. So that allows to
test UI of the mobile phone, SIP flow, some exeptional cases etc. I'm not
really sure if you guys doing something similar with SIPp. As far as I
understood from the mailing list, many people just use it to generate MANY
calls to test the ability of the equipment to handle it. This program,
however, was designed with some other idea in a mind - to be able to test
SIP stack, UI of the end-user equipment and so on.
So, what do you think about this? Does anybody think it can be helpful for
him? I just want to make it GPL, but I don't know both how to do it, and
what to do :) Can I get some space from sipp website? What about SVN?
etc...
Thank you,
Alexey
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
--
HP OpenCall Software
http://www.hp.com/go/opencall/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
