In case you're thinking this because of the way the UAS scenario looks
on the screen, please note the scenarios are displayed differently
depending on whether they are server or client side:

 

When client side sends NOTIFY, it shows

NOTIFY ----->

When server side expects NOTIFY, it shows

--------> NOTIFY

 

Are you actually seeing (e.g. tcpdump) this NOTIFY being sent "on the
wire" by the UAS side?

 

Regards,

-David

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: mercredi 11 juin 2008 14:35
To: [email protected]
Cc: Lecluse, Philippe
Subject: [Sipp-users] Strange behaviour with a UAS scenario in IMS Bench

 

Hi, I get a strange behaviour in IMS Bench.

I wrote this simple UAS scenario:


------------------------------------------------------------------------
-------------------------------
<scenario name="ims_not" on_unexpected="9">

<!-- *** STEP 1 *** -->
 <!-- Select a user from the 'Registered Subscriber' pool
-->
  <nop>
    <action>
      <assign_user pool="2" scheme="rand_uni"/>   <!-- 'Subribed' user
-->
    </action>
  </nop>

<!-- *** STEP 2 *** -->
 <!-- Now that our preparation step is done, we wait for the time when
the scenario -->
 <!-- must actually start, according to the random scenario arrival
distribution.   -->
  <sync crlf="true">
    <action>
      <exec int_cmd="set_start_time"/>
    </action>
  </sync>

<!-- *** STEP 3 *** -->
 <!-- Now the SIP scenario really starts -->

  <!-- Ricezione NOTIFY dal P-CSCF e risposta per l'evento (gestito
dall'OpenIMSCore di    -->
  <!-- registrazione gestite in modo automatico dalla opzione -aa del
sipp                 -->
  <recv request="NOTIFY" timeout="100" ontimeout="9">
  </recv>

  <send crlf="true">
    <![CDATA[

      SIP/2.0 200 OK
      [last_Via:]
      [last_Record-Route:]
      [last_From:]
      [last_To:];tag=[pid]SIPpTag01[call_number]
      [last_Call-ID:]
      [last_CSeq:]
      Content-Length: [len]

    ]]>
  </send>

  <label id="9"/> <!-- END OF SCENARIO -->


  <!-- definition of the response time repartition table (unit is ms)
-->
  <ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/>

  <!-- definition of the call length repartition table (unit is ms)
-->
  <CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000"/>

</scenario>
------------------------------------------------------------------------
-------------------------------

It begin with a <recv> then waits some time listening for specific
coming messages.
The strange thing is that when I launch the symulation it seems that
this scenario wants to send a NOTIFY message instead of listening for
it.

Why it happens?

Rob 

---------------------------------------------------------------------
Intel Corporation NV/SA
Rond point Schuman 6, B-1040 Brussels
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to