SIPp and SailFin
If you using SIPp to make calls to SailFin read Jens's blog for some of the parameters that has to be copied from Contact header of the 200 OK to the request URI of subsequent requests. For SailFin single instance you need to copy parameter fid (fragment id). This is used by the container for associating dialog to a call. For SailFin cluster you need to copy both fid and bekey. bekey is used by Converged Load Balancer front-end to route request to the backend.
For a UAC generate the default scenario from SIPp using
$sipp -sd uac > uac.xml
Update the uac.xml as highlighted.
| <recv response="200" rtd="true">
<action>
<ereg regexp="fid=([[:alnum:]]*)_([[:alnum:]]*)"
search_in="hdr" header="Contact:" check_it="true" assign_to="1" />
<ereg regexp="bekey=([[:alnum:]]*)" search_in="hdr" header="Contact:" check_it="true" assign_to="2" />
</action>
</recv>
<!-- Packet lost can be simulated in any send/recv message by -->
<!-- by adding the 'lost = "10"'. Value can be [1-100] percent. -->
<send>
<![CDATA[
ACK sip:[service]@[remote_ip]:[remote_port];[$1];[$2] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:sipp@[local_ip]:[local_port]>;tag=[pid]SIPpTag00[call_number]
To: sut <sip:[service]@[remote_ip]:[remote_port]>[peer_tag_param]
Call-ID: [call_id]
CSeq: 1 ACK
Contact: sip:sipp@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
]]>
</send>
<!-- This delay can be customized by the -d command-line option -->
<!-- or by adding a 'milliseconds = "value"' option here. -->
<pause/>
<!-- The 'crlf' option inserts a blank line in the statistics report. -->
<send retrans="500">
<![CDATA[
BYE sip:[service]@[remote_ip]:[remote_port];[$1];[$2] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:sipp@[local_ip]:[local_port]>;tag=[pid]SIPpTag00[call_number]
To: sut <sip:[service]@[remote_ip]:[remote_port]>[peer_tag_param]
Call-ID: [call_id]
CSeq: 2 BYE
Contact: sip:sipp@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
]]>
</send>
|
Tracing the SIPp call you can see the following.
| UDP message received [357] bytes :
SIP/2.0 200 OK^M
Content-Length: 0^M
Contact: <sip:$127.0.0.1:15060;fid=instance2_1;bekey=sailfin>^M
To: "sut"<sip:service@127.0.0.1:15060>;tag=ffvglcl9-d^M
Cseq: 1 INVITE^M
Via: SIP/2.0/UDP 127.0.0.1:5061;branch=z9hG4bK-11792-1-0^M
Server: Glassfish_SIP_1.0.0^M
Call-Id: 1-11792@127.0.0.1^M
From: "sipp"<sip:sipp@127.0.0.1:5061>;tag=11792SIPpTag001^M
^M
----------------------------------------------- 2008-05-06 01:11:57:894.606
UDP message sent (382 bytes):
ACK sip:service@127.0.0.1:15060;fid=instance2_1;bekey=sailfin SIP/2.0^M
Via: SIP/2.0/UDP 127.0.0.1:5061;branch=z9hG4bK-11792-1-5^M
From: sipp <sip:sipp@127.0.0.1:5061>;tag=11792SIPpTag001^M
To: sut <sip:service@127.0.0.1:15060>;tag=ffvglcl9-d^M
Call-ID: 1-11792@127.0.0.1^M
CSeq: 1 ACK^M
Contact: sip:sipp@127.0.0.1:5061^M
Max-Forwards: 70^M
Subject: Performance Test^M
Content-Length: 0^M
^M
----------------------------------------------- 2008-05-06 01:11:59:897.111
UDP message sent (382 bytes):
BYE sip:service@127.0.0.1:15060;fid=instance2_1;bekey=sailfin SIP/2.0^M
Via: SIP/2.0/UDP 127.0.0.1:5061;branch=z9hG4bK-11792-1-7^M
From: sipp <sip:sipp@127.0.0.1:5061>;tag=11792SIPpTag001^M
To: sut <sip:service@127.0.0.1:15060>;tag=ffvglcl9-d^M
Call-ID: 1-11792@127.0.0.1^M
CSeq: 2 BYE^M
Contact: sip:sipp@127.0.0.1:5061^M
Max-Forwards: 70^M
Subject: Performance Test^M
Content-Length: 0^M
^M
|
Posted at 01:31AM May 06, 2008
by sonymanuel in Sun |
Posted by Sony Manuel's blog on May 06, 2008 at 01:38 AM IST #