Re: [Sipp-users] problem with recv MESSAGE after send MESSAGE at clientmode

[ZHU J. <Joh...@al...>]

Hi Miloslavsky,

 

I already use you workaround as the following.

In uac.xml

<send MESSAGE/>

<recv response="202"/>

In uas.xml

<recv request="MESSAGE"/>

<send 200 OK/>

 

Run them like this

./sipp -sf ../uac.xml remote_ip:5060 -trace_msg -m 1 -p 5061

./sipp -sf ../uas.xml remote_ip::5060 -trace_msg -m 1 -p 5061

 

But uas.xml is server mode. So when it received sip MESSAGE from remote
port (not 5060), it sent 200 OK to wrong remote port, no 5060. The
remote server does not listen it.

Because the remote server is sip server.

 

Thanks

Johnson

________________________________

From: Evgeny Miloslavsky [mailto:emi...@ju...] 
Sent: Wednesday, March 04, 2009 4:04 PM
To: ZHU Johnson
Subject: RE: [Sipp-users] problem with recv MESSAGE after send MESSAGE
at clientmode

 

As far as I know SIPp and SIP, the problem is that every MESSAGE request
has its own Call-ID. Thus SIPp fails to jump.

I would like to suggest you as a workaround/solution to call sipp
instanse (the one will receive MESSAGE) using exec command from the
current sipp instanse (the one sending the MESSAGE)

 

Regards,

Evgeny Miloslavsky

Systest Engineer

Juniper Networks Solutions Israel LTD.

Office: 972-9-9717320/2355

________________________________

From: ZHU Johnson [mailto:Joh...@al...] 
Sent: Wednesday, March 04, 2009 9:27 AM
To: sip...@li...
Subject: [Sipp-users] problem with recv MESSAGE after send MESSAGE at
clientmode

 

Hi, All

 

I have some problem about receive MESSAGE request. The script does not
want to jump over the <recv request="MESSAGE"/> block when it already
received sip MESSAGE.

My scenario is the following.

<send MESSAGE/>

<recv response="202"/>

<recv request="MESSAGE"/>

<send 200 OK/>

 

I find some info about MESSAGE problem at the following link
(http://osdir.com/ml/telephony.sipp.user/2007-04/msg00074.html). 

Charles suggest use two sipp instance. One sends MESSAGE and receives
202 response. Another receives MESSAGE and sends 200 ok.

So I change my script like this:

In uac.xml

<send MESSAGE/>

<recv response="202"/>

In uas.xml

<recv request="MESSAGE"/>

<send 200 OK/>

 

Run them like this

./sipp -sf ../uac.xml remote_ip:5060 -trace_msg -m 1 -p 5061

./sipp -sf ../uas.xml remote_ip::5060 -trace_msg -m 1 -p 5061

 

But uas.xml is server mode. So when it received sip MESSAGE from remote
port (not 5060), it sent 200 OK to wrong remote port, no 5060. 

Because the remote server is sip server.

 

My question is 

1)       how to bind remote port (5060) in server mode?

2)       How to recv MESSAGE request after send MESSAGE request in one
sipp instance?

 

 

Thanks

Johnson