The problem with this kind of testing is that you are testing asterisk, using asterisk as the test generator.

When you start getting performance based artifacts, are you going to be able to tell if it's from the sections of asterisk handling the call transactions and media streams or from the sections that are generating the calls. How much of the system resources are going to be used in the generation of the calls, how does this affect asterisk.

Is the program flow of internally generated calls exactly the same as the program flow for the type of calls you are using as the scenario for the test?

I think you will find that using the same asterisk box as testee and tester will result in not being able to identify what is causing the artifacts... In other words, your testing tool will significantly affect your test platform.

-Chris

On 03:07 PM 8/16/2004, Tom Masterson wrote:
>We are trying to set up some scripts to test asterisk under various loads.
>What we are doing is trying to load a bunch of calls in to various queues
>atuomatically from various numbers etc so we can see how it behaves.  I
>think we can do this by loading files in to the var/spool/asterisk/qcall
>directory.  However the format of this file has a field named identifier
>which appears to be a file of some sort in some location.
>
>1.  Are we going about this in the correct direction?
>2.  Can someone explain what the fields in the file in qcall are and what
>identifier should be?
>
>Thanks
>Tom
>
>_______________________________________________
>Asterisk-Users mailing list
>[EMAIL PROTECTED]
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to