Hi Fernando,
although the OPTIONS request was initially intended to determine
capabilities of the peer, its typical use became different through time:
it is being sent to determine whether the remote peer is up at
application level, and any response (even a 4xx or 5xx except 503) is
typically enough to make the sender consider the recipient as up and
running for "normal" requests, i.e. INVITEs. The message should come
outside any existing dialog, which seems to be your case as well.
So to accommodate your server-side (UAS) SIPp script to the new
behaviour of the remote device, it should be enough to add the following:
1) before the first <recv request="INVITE" ..., add:
<recv request="OPTIONS" optional="true" next="respond_options"/>
2) somewhere to a harmless place, add:
<label id="respond_options"/>
<send next="end_of_scenario">
<![CDATA[
SIP/2.0 501 Not supported, sorry
[last_Via:]
[last_From:]
[last_To:]
[last_Call-ID:]
[last_CSeq:]
Content-Length: 0
]]>
</send>
3) right before the end of the scenario, place
<label id="end_of_scenario"/>
That should be it. This way, you'll add handling for the OPTIONS which
will not interfere with the main part of the scenario any more.
Good luck
Pavel
Dne 4.12.2015 v 21:33 Fernando Jorge napsal(a):
Hi,
Hope you can help me....
We've been using sipp in our company for years with no problems at all
and yesterday I started receiving the following errors from the
"server" side of the system....
2015-12-04 11:45:12:995 1449258312.995055: Continuing call on
unexpected message for Call-Id '3A26FE3029EAABC731E430124B031FB1':
while expecting 'INVITE' (index 0), received 'OPTIONS
sip:10.10.50.171:5060 <http://10.10.50.171:5060> SIP/2.0
Via: SIP/2.0/UDP
10.10.50.13:5060;branch=z9hG4bK3A26FE3029EAABC731E430124B031FB1
From: Anonymous <sip:10.10.50.171:5060
<http://10.10.50.171:5060>>;tag=3A26FE3029EAABC731E430124B031FB1
To: <sip:10.10.50.171:5060 <http://10.10.50.171:5060>>
Call-ID: 3A26FE3029EAABC731E430124B031FB1
CSeq: 15 OPTIONS
Max-forwards: 70
X-redundancy: Request
Content-Length: 0
'.
sipp: There were more errors, see
'sipp_server_no_echo_call_volume_G711_2732_errors.log' file
I've been keeping and eye on my DUT and Im constantly seeing this
coming from the sipp "server" side...
[17426]sipMsg.c:1455-- TX message :5060->10.10.50.171:5060
<http://10.10.50.171:5060> transport:UDP altPort:0
[17426]sipMsg.c:1488-- Translated:
"OPTIONS sip:10.10.50.171:5060 <http://10.10.50.171:5060> SIP/2.0
Via: SIP/2.0/UDP
10.10.50.13:5060;branch=z9hG4bK054EB0661BC0B2B5C0C37AC6F7CCE3F0
From: Anonymous <sip:10.10.50.171:5060
<http://10.10.50.171:5060>>;tag=054EB0661BC0B2B5C0C37AC6F7CCE3F0
To: <sip:10.10.50.171:5060 <http://10.10.50.171:5060>>
Call-ID: 054EB0661BC0B2B5C0C37AC6F7CCE3F0
CSeq: 27 OPTIONS
Max-forwards: 70
X-redundancy: Request
Content-Length: 0
"
[17426]sipMsg.c:1455-- TX message :5060->10.10.50.171:5060
<http://10.10.50.171:5060> transport:UDP altPort:0
[17426]sipMsg.c:1488-- Translated:
"OPTIONS sip:10.10.50.171:5060 <http://10.10.50.171:5060> SIP/2.0
Via: SIP/2.0/UDP
10.10.50.13:5060;branch=z9hG4bK7513C36395D84289915E34B4B1776C91
From: Anonymous <sip:10.10.50.171:5060
<http://10.10.50.171:5060>>;tag=7513C36395D84289915E34B4B1776C91
To: <sip:10.10.50.171:5060 <http://10.10.50.171:5060>>
Call-ID: 7513C36395D84289915E34B4B1776C91
CSeq: 28 OPTIONS
Max-forwards: 70
X-redundancy: Request
Content-Length: 0
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
