What you are asking is difficult because SIPp is written to have separate 
initiator and responder processes and Linux will not let two processes share 
the same port. (I assume Windows has the same restriction.)

 

There are three ways of getting around this problem. 1) is to be able to 
control the Call-ID of the second INVITE so the client process thinks it is on 
the same call. I was using SIPp to test a Gateway so I had this control and I 
implemented the partial Call-ID matching to have multiple Call-IDs map to one 
call in SIPp. 2) is to use to protocol to say "reply to me on this port" which 
is the server port. Even if you get the initial 180 at the Server you can deal 
with that by allowing multiple messages to create a call. 3) is to control the 
timing so that you terminate the client process and start the server process 
during a pause in the exchange. (Again easy with a Gateway, harder with a real 
application.)

 

You are not the first person to have this problem and I don't remember any 
better response. I have long thought that an option to "just treat everything 
as one call" would be a good idea and not that hard to do.

 

I hope this helps,

Peter


 


Date: Fri, 3 Sep 2010 17:34:40 +0800
From: lu.zhen...@huawei.com
To: sipp-users@lists.sourceforge.net
Subject: [Sipp-users] Send and recieve INVITE in one scenario





Dear all:
i am handling a case which need to send a INVITE to an application first , the 
application will response with 180,
then the application initial a INVITE to the same port I sent the INVITE, I 
will handle the INVITE to finish the call and then the application will send 
the 200/ok corresponding to the first INVITE I sent.
INVITE(Call1)---->
<----180(Call1)
 
 
<----INVITE(Call2)
---->180
---->200
<----ACK
---->BYE
 
<----200(Call1)
.......
 
 
Is there any possible to compose a scenarion to send and recieve INVITE at the 
same time? Or b2bua mode?
 
Best Regards
 
Thanks
 
lu
 
 
------------------------------------------------------------------------------ 
This SF.net Dev2Dev email is sponsored by: Show off your parallel programming 
skills. Enter the Intel(R) Threading Challenge 2010. 
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________ Sipp-users mailing list 
Sipp-users@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/sipp-users                         
                 
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to