Hello,
I had problems with sipp server scenario sending 200 OK to the wrong port.
I used the command line:
./sipp -sf uasl.xml -trace_err -trace_msg -rsa xxx:5060 -t u1 -p 5061
And the Via : header specified port 5060 too,
But sipp keeps sending the 200 Ok on the same port on which it received the
previous message.
We traced it with tshark.
We reverted to Sipp 2.1 and that problem was gone (but with 2.1 we have
problems with pcap . :-().
The partial scenario was:
<recv request="INVITE" rrs="true" crlf="true">
<action>
<ereg regexp=".*" search_in="hdr" occurence="1" header="Via:"
assign_to="1" />
<ereg regexp=".*" search_in="hdr" occurence="2" header="Via:"
assign_to="2" />
<ereg regexp=".*" search_in="hdr" occurence="1" header="From:"
assign_to="3" />
<ereg regexp=".*" search_in="hdr" occurence="1" header="To:"
assign_to="4" />
</action>
</recv>
[.]
<send retrans="500">
<![CDATA[
SIP/2.0 200 OK
Via:[$1]
Via:[$2]
[last_From:]
[last_To:];tag=[call_number]
[last_Call-ID:]
[last_CSeq:]
Contact: <sip:[EMAIL PROTECTED]:[local_port]>
Content-Type: application/sdp
Content-Length: [len]
v=0
o=calltaker1 53655765 2353687637 IN IP[local_ip_type] [local_ip]
s=Emergency Call
c=IN IP[media_ip_type] [media_ip]
t=0 0
m=audio [media_port] RTP/AVP 0
a=rtpmap:0 PCMU/8000
]]>
</send>
Any suggestion?
Thanks,
Anna
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
