Hi SIPp community,
Recently (last two days) a colleague and I have been assigned performance
testing of an IMT I&V network at work. Although SIPp is a popular testing
tool at work, I had never used it before. After modifying some sample
scenario xml files we quickly were able to register thousands of users and
then place millions of calls (we left SIPp running over the weekend).
All in all, this is a great tool that was easy to get started and use!
Now here comes the "but", I do have a couple of constructive criticisms (I
hope you don't mind).
1. The format of the CSV (Comma Separated Values) files.
Why is a semi-colon used to delimit the fields? For small hand-made files
this is OK, but why not use a more popular delimiter, like a comma (as the
file type implies) or a TAB stop? Our CSV files have thousands (or even
millions) of users within them and we use MS EXCEL to generate the files.
However, MS EXCEL only (among others) exports to either a real CSV file
(using commas) or a TAB delimited file (using TABs). So then we need to
perform a simple "find & replace" operation changing "," to a ";". I know
this step is easy, but it is just plain annoying. So what is the reasoning
behind the choice of a semi-colon?
2. XML files.
Like most companies and communities, especially within the telecom industry,
SIPp has jumped onto the XML bandwagon without using it right - just like
most of the telecom industry - there are some serious XML crimes being
committed out there :). For example, take the following scenario:
<scenario name="UAC Basic Registration">
<label id="0" />
<send retrans="500" start_rtd="true">
<![CDATA[
REGISTER sip:[field1] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number]
To: [field0] <sip:[EMAIL PROTECTED]>
]]>
</send>
<recv response="200" rtd="true" next="3" optional="true" />
<recv response="401" rtd="true" next="1" auth="true" crlf="true" />
<label id="1" />
<send retrans="500" start_rtd="true">
<![CDATA[
REGISTER sip:[field1] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number]
To: [field0] <sip:[EMAIL PROTECTED]>
]]>
</send>
<recv response="200" rtd="true" next="3" crlf="true" />
</scenario>
The "next" and "label"s resemble the "goto"s and "label"s of the programming
world, so why not just use a flat / rational file and NOT XML which is
supposed to be hierarchical based? Firstly, spaghetti coding went out years
ago. Secondly and most importantly, the order of elements within an XML
document IS NOT guaranteed by any parser (although most report children in
document order because it is easier)! An easy and relatively small fix would
be to wrap code blocks with the existing "label" tags and add an entry
attribute so SIPp knows where to begin! For example (using the earlier
sample):
<scenario name="UAC Basic Registration">
<label id="0" entry="true">
<send retrans="500" start_rtd="true">
<![CDATA[
REGISTER sip:[field1] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number]
To: [field0] <sip:[EMAIL PROTECTED]>
]]>
</send>
<recv response="200" rtd="true" next="3" optional="true" />
<recv response="401" rtd="true" next="1" auth="true" crlf="true" />
</label>
<label id="1">
<send retrans="500" start_rtd="true">
<![CDATA[
REGISTER sip:[field1] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number]
To: [field0] <sip:[EMAIL PROTECTED]>
]]>
</send>
<recv response="200" rtd="true" next="3" crlf="true" />
</label>
</scenario>
Hit me back with comments,
Simon
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
