Comment #1 on issue 860 by vladimir.ralev: The behavior of MSS1.0 with Proxy
http://code.google.com/p/mobicents/issues/detail?id=860
Our analysis shows that the UAC sipp script is incorrect. As per the SIP
specification the subsequent requests must move the URIs from Record-Route
into
Route headers and follow the same path.
uac.xml has subsequent requests of this type:
<send>
<![CDATA[
ACK sip:[servi...@[remote_ip]:6000 SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:s...@[local_ip]>;tag=[pid]SIPpTag00[call_number]
To: sut <sip:[servi...@[remote_ip]>[peer_tag_param]
Route:[$1]
Call-ID: [call_id]
CSeq: 1 ACK
Contact: sip:s...@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
]]>
</send>
Where $1 is a values parsed with a regular expression, which doesn't take
into
account the whole URI.
Please note that the recommended way to use Route headers in sipp is like
this:
<send>
<![CDATA[
ACK sip:[servi...@[remote_ip]:6000 SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:s...@[local_ip]>;tag=[pid]SIPpTag00[call_number]
To: sut <sip:[servi...@[remote_ip]>[peer_tag_param]
[routes]
Call-ID: [call_id]
CSeq: 1 ACK
Contact: sip:s...@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
]]>
</send>
[routes] is specifically implemented in SIPp for this purpose and regexp
matching is
never required.
If you really have a good reason to use regular expression, let us know, we
could
work on fixing the regular expression, however we find this unnecessary.
So our recommendation is to modify your SIPp script. Attached is the new
uac.xml
using [routes].
If this scenario simulates some real use-case, we will provide an option in
MSS to
work with your original script.
Short explaination why this is happening - we store some information in the
Record-
Route header as an optmiziation for Application Routing and Clustering (to
reduce
replication overhead). It also helps us in monitoring and debugging. We are
planning
to provide an option to turn off this behaviour in the next update. Let us
know if
you think this is high-priority task.
Attachments:
uac.xml 4.3 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
