Changeset 5071 for pjproject/trunk/tests/pjsua/scripts-sipp/uac-reinvite-bad-via-branch.xml

Timestamp:

Apr 15, 2015 12:55:54 PM (10 years ago)

Author:

nanang

Message:

Re #1842: Workaround for spurious failure in sipp/uac-reinvite-bad-via-branch.xml test, i.e: just retry the scenario. The failure is caused by race between SIPp sending re-INVITE vs transaction immediate termination (by SIP INVITE module when the session reaches CONFIRMED state).

File:

• pjproject/trunk/tests/pjsua/scripts-sipp/uac-reinvite-bad-via-branch.xml (modified) (3 diffs)

pjproject/trunk/tests/pjsua/scripts-sipp/uac-reinvite-bad-via-branch.xml

@@ -25 +25 @@
 
 <scenario name="UAC re-INVITE with bad Via branch">
+
+  <label id="1"/>
+  
   <send retrans="500">
     <![CDATA[
@@ -113 +116 @@
   </send>
 
+  <!-- Previous INVITE transaction may have been destroyed, and 200     -->
+  <!-- response is received, instead of 500. So, let's just try again,  -->
+  <!-- i.e: send ACK and repeat the scenario.                           -->
+  <recv response="200" optional="true" next="9">
+  </recv>
+  
   <!-- By adding rrs="true" (Record Route Sets), the route sets         -->
   <!-- are saved and used for following messages sent. Useful to test   -->
@@ -160 +169 @@
   </send>
 
-  <recv response="200" crlf="true">
-  </recv>
-
+  <recv response="200" crlf="true" next="10">
+  </recv>
+
+  <label id="9"/>
+
+  <!-- Send ACK before repeating the scenario                           -->
+  <send next="1">
+    <![CDATA[
+
+      ACK sip:[service]@[remote_ip]:[remote_port] SIP/2.0
+      Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=z9hG4bKPj-1
+      From: sipp <sip:sipp@[local_ip]:[local_port]>;tag=[call_number]
+      To: sut <sip:[service]@[remote_ip]:[remote_port]>[peer_tag_param]
+      Call-ID: [call_id]
+      CSeq: 2 ACK
+      Contact: sip:sipp@[local_ip]:[local_port]
+      Max-Forwards: 70
+      Subject: Performance Test
+      Content-Length: 0
+
+    ]]>
+  </send>
+
+  
+  <label id="10"/>
 
   <!-- definition of the response time repartition table (unit is ms)   -->