Hi sipp-users,

May I ask for second pair of eyes to see what I'm doing wrong here?

Here is what I'm trying to accomplish:

- My XML code checks the payload type specified by "[field6]" in the code
from a CSV file I'm injecting.
- When it's payload type 0, exec rtp_stream of a g711 wav file.
- When it's payload type 9, exec play_pcap of a g722 pcap file.

Here is the logic:

  <nop>

    <action>

       <assignstr assign_to="1" value="[field6]" />

    </action>

  </nop>


  <nop next="5" test="2">

    <action>

       <test assign_to="2" variable="1" compare="equal" value="0" />

    </action>

  </nop>



  <nop next="4" test="3">

    <action>

       <test assign_to="3" variable="1" compare="equal" value="9" />

    </action>

  </nop>


  <label id="5" />

  <nop next="6">

    <action>

      <exec rtp_stream="/opt/sipp/g711-ulaw-msft.wav,-1,0" />

    </action>

  </nop>


  <label id="4" />

  <nop>

    <action>

      <exec play_pcap_audio="/opt/sipp/g722_sbstandup_short.pcap" />

    </action>

  </nop>


  <label id="6" />


The issue I'm seeing is as follows:

- The G.711 rtp stream plays correctly.

- The G.722 pcap play does not play anything at all even though I see UDP
packets in my tcpdump output.

-  With these conditional branching, I'm only limited to 540 calls on
single sipp process.

-  Once I removed all the branching and just have play_pcap action on G.722
pcap file, that works fine and I can hear the media.  Also, I'm able to get
700 concurrent users on a single sipp process.


What am I doing wrong here?


Thanks,

--Andy
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to