Re: [Sipp-users] MESSAGE & INVITE

Simon Flannery Mon, 11 Aug 2008 16:11:02 -0700

Hi,

I'm not sure what is happening in your message traces. Is the message
going around in a circle?


Anyway, I have attached an example message scenario. There is a sender
(message_small.xml) and a receiver (message_listener_200.xml).

This has been used with SIPp version 3.0, I do not recommend you use
SIPp 3.1 as a lot of things are simply broken!

Simply run an instance of SIPp on one PC for the sender, and run
another instance of SIPp on another PC for the receiver. You will have
to change the IP addresses in the scripts and provide your own CSV
file.

HTH,

Simon

2008/8/12 ims.asuser ims.asuser <[EMAIL PROTECTED]>:
> Thank you Simon,
>
> Your advice was really useful.
> But i spent the whole day trying to establish a call and exchanging Message
> but it DOES NOT work and I really do not know why!
>
> Actually, when the caller sends an INVITE then a ACK...the ACK is not
> "forwarded" to the callee (I received a 100 instead), very weird!
>
> For the instant messaging, When the client receives a MESSAGE, it does not
> send back a 200 OK (dunno why?!)
>
> Always, OpenIMSCore is always sending back either INVITE or MESSAGE.
>
> I'm really fed up and I would be very grateful if anyone could help me!
> Also, is anyone has basic call & messaging scenarios that work (I just want
> to test if it work on my side)
>
> Attached is my scenarios for messaging and INVITE.
> The trace are downloadable here: http://dl.free.fr/o3qaadnzW
>
> Thanks a lot!
> Khaldon
>
>
>
>
> 2008/8/11 Simon Flannery <[EMAIL PROTECTED]>
>>
>> Not sure if this will help, but have you considered using the -aa
>> switch to auto respond to inbound NOTIFYs and simply pausing your
>> scenario (add a pause command in the scenario file)?
>>
>> Normally when testing a similar scenario, as you have described, I
>> send a SUBSCRIBE with a different port in the SIP contact header. Then
>> I run another instance of SIPp on the other "different" port which
>> simply responds to an in bound NOTIFY such as:
>>
>> <?xml version="1.0" encoding="ISO-8859-1" ?>
>> <!DOCTYPE scenario SYSTEM "sipp.dtd">
>>
>> <scenario name="NOTIFY signal listener">
>>  <recv request="NOTIFY" />
>>  <send>
>>    <![CDATA[
>>      SIP/2.0 200 OK
>>      [last_Via:]
>>      [last_To]
>>      [last_From]
>>      [last_Call-ID:]
>>      [last_CSeq:]
>>      [last_Event:]
>>      Contact: <sip:[local_ip]:[local_port];transport=[transport]>
>>      Content-Length: 0
>>    ]]>
>>  </send>
>> </scenario>
>>
>> Or, you could use the -aa switch as described before.
>>
>> HTH,
>>
>> Simon
>>
>> 2008/8/10 ims.asuser ims.asuser <[EMAIL PROTECTED]>:
>> >
>> > Hi all,
>> >
>> > That not totally right (for me), If I follow that registration flow,
>> > OpenIMSCore sends me a NOTIFY. after receiving the 200 OK for the IMS
>> > core,
>> > it tries to send me a NOTIFY. As the program stopped, It tries to send
>> > it
>> > again and again...That' really painful because when I run my UAS, it is
>> > expecting to receive an INVITE but it receives a NOTIFY (that the core
>> > sends
>> > back).
>> >
>> > So, I have decided to send a subscribe to the reg event (thank you
>> > Franz)
>> > but SIPp is blocked on receiving a NOTIFY. Even if the core send tons of
>> > NOTIFY messages, it does not take it into account...weird!
>> >
>> > I think I will (soon) test the IMS bench SIPp, Is anyone have a simple
>> > tutorial that show to use it easily and quickly (I have read all the 67
>> > pages of documentation and that look really difficult, I do not where to
>> > start from!)
>> >
>> > Thank you all!!
>> > Khaldon
>> >
>> > ps: attached is my scenario and wireshark trace
>> >
>> > 2008/8/7 Кузьмин И. И. <[EMAIL PROTECTED]>
>> >>
>> >> Hi Khaldon,
>> >>
>> >> i did perfomance tests of OpenIMSCore using SIPp 2.1 and SIPp IMS
>> >> Bench.
>> >> Normal Registration signaling flow looks like:
>> >>
>> >> > 1) register ->
>> >> > 2) <-401
>> >> > 3) register->
>> >> > 4) <-200
>> >>
>> >> it's enough to provide the registration for user. Pay attention to
>> >> P-Headers ;)
>> >>
>> >> In addition you'll need to fill the FoHSS with a number of subscriber
>> >> entities, to handle this issue in automatic mode analyse the SQL
>> >> scripts
>> >> used for creation of Alice and Bob.
>> >>
>> >> Regards,
>> >> Ivan Kuzmin.
>> >> State University of Telecomunications, St.Petersburg, Russia.
>> >>
>> >>
>> >> -----Original Message-----
>> >> From: "ims.asuser ims.asuser" <[EMAIL PROTECTED]>
>> >> To: [email protected]
>> >> Date: Thu, 7 Aug 2008 16:16:40 +0200
>> >> Subject: [Sipp-users] SUBSCRIBE scenario
>> >>
>> >> >
>> >> > Hi all,
>> >> >
>> >> > I would like to test the OpenIMSCore platform (I will perform as much
>> >> > as
>> >> > I
>> >> > can). These tests will be then given to the IMS community.
>> >> > First of all, did anyone perform OpenIMSCOre tests using SIPp?
>> >> >
>> >> > I would like to perform first in different stage:
>> >> > 1) Registration
>> >> > 2) Calls
>> >> > 3) Instant Messaging
>> >> >
>> >> > So far, I'm only on the first step (registering a user). I only
>> >> > managed
>> >> > to
>> >> > do a simple registration (register ->, <-401, register->, <-200). But
>> >> > I
>> >> > have
>> >> > problems when I want to go further.
>> >> > In ims, the scenario looks like that:
>> >> > 1) register ->
>> >> > 2) <-401
>> >> > 3) register->
>> >> > 4) <-200
>> >> > 5) subscribe->
>> >> > 6) <-notify
>> >> > 7)  200->
>> >> >
>> >> > The IMS Core is behaving really eerily when I send a subscribe
>> >> > message
>> >> > then
>> >> > the simulation stops
>> >> > Is anyone know why is it working like that?
>> >> >
>> >> > Attached are my script and wireshark trace.
>> >> >
>> >> > Many thanks,
>> >> > Khaldon
>> >> >
>> >> > ATTACHMENT: text/xml (Registerbob1.xml)
>> >> > ATTACHMENT: application/octet-stream (SIPp_SUBSCRIBE)
>> >> >
>> >> >
>> >> >
>> >> > -------------------------------------------------------------------------
>> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's
>> >> > challenge
>> >> > Build the coolest Linux based applications with Moblin SDK & win
>> >> > great
>> >> > prizes
>> >> > Grand prize is a trip for two to an Open Source event anywhere in the
>> >> > world
>> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> >> >
>> >> > _______________________________________________
>> >> > Sipp-users mailing list
>> >> > [email protected]
>> >> > https://lists.sourceforge.net/lists/listinfo/sipp-users
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> >
>> > -------------------------------------------------------------------------
>> > This SF.Net email is sponsored by the Moblin Your Move Developer's
>> > challenge
>> > Build the coolest Linux based applications with Moblin SDK & win great
>> > prizes
>> > Grand prize is a trip for two to an Open Source event anywhere in the
>> > world
>> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> > _______________________________________________
>> > Sipp-users mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/sipp-users
>> >
>> >
>
>

<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE scenario SYSTEM "sipp.dtd">

<scenario name="MESSAGE signal listener">
  <recv request="MESSAGE" />
  <send>
    <![CDATA[
      SIP/2.0 200 OK
      [last_Via:]
      [last_To]
      [last_From]
      [last_Call-ID:]
      [last_CSeq:]
      Content-Length: 0
    ]]>
  </send>
</scenario>

<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE scenario SYSTEM "sipp.dtd">

<scenario name="MESSAGE signal with unknown header and field">
<send retrans="4000">
    <![CDATA[
      MESSAGE sip:[EMAIL PROTECTED] SIP/2.0
      From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number]
      To: [field0] <sip:[EMAIL PROTECTED]>
      Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]	
      Call-ID: [call_id]
      CSeq: [cseq] MESSAGE
      Route: <sip:[remote_ip]:[remote_port];lr>
      User-Agent: [field3]
      Max-Forwards: 69
      Accept-Contact: *;+g.oma.sip-push.0x903f;explicit;require
      Content-Type: multipart/mixed; boundary=abcdef
      P-Asserted-Identity: <sip:[EMAIL PROTECTED]>
      Subject: IMS Push Message
      Content-Length: [len]

--abcdef
      Content-type: application/sip-app-info

      <SIPAPINIT>
        <S>sip:xxx.xxx.xxx.xxx</S>
        <N>Taro Soft<\N>
        <Vnd>Softbank</Vnd>
        <Ver>1.0.0</Ver>
        <M>Good evening</M>

        <L>http://www.hogehoge.com/app/index.html</L>
      </SIPAPINIT>

--abcdef
      Content-type: binary
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      afghagopuiouidfnvkadjvherafguinhsf8oahuiw4avrt5n479v5nh3479vt4nhip7vfwevyan
      END OF BINARY
--abcdef--

--abcdef--

   ]]>
  </send>
  <recv response="500" rtd="true" next="1" optional="true" />
  <recv response="502" rtd="true" next="1" optional="true" />
  <recv response="503" rtd="true" next="1" optional="true" />
  <recv response="504" rtd="true" next="1" optional="true" />
  <recv response="513" rtd="true" next="1" optional="true" />
  <recv response="403" rtd="true" next="1" optional="true" />
  <recv response="408" rtd="true" next="1" optional="true" />
  <recv response="412" rtd="true" next="1" optional="true" />
  <recv response="480" rtd="true" next="1" optional="true" />
  <recv response="481" rtd="true" next="1" optional="true" />
  <recv response="200" rtd="true" />
  <label id="1" />
</scenario>

MESSAGE_tcp_200.sh
Description: Bourne shell script

MESSAGE_udp_200.sh
Description: Bourne shell script

MESSAGE_push_small_tcp.sh
Description: Bourne shell script

hero.csv
Description: application/filler

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Re: [Sipp-users] MESSAGE & INVITE

Reply via email to