Sipp truncates the Route header created by [routes]

Bug #308213 reported by Florian Hackenberger
4
Affects Status Importance Assigned to Milestone
sip-tester (Debian)
Fix Released
Undecided
Unassigned
sip-tester (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by Florian Hackenberger

Bug Description

Binary package hint: sip-tester

Many SIP providers use the Record-Route header of the sip protocol. The UAC is required to create the Route header accordingly. See 16.12.1.2 Traversing a Strict-Routing Proxy at http://www.ietf.org/rfc/rfc3261.txt The sipp keyword [routes] creates the Route header. See for example the following scenario snippet:

  <send>
    <![CDATA[

      ACK [next_url] SIP/2.0
      [last_Via:]
      From: sipp <sip:[field0]@[remote_ip]:[remote_port]>;tag=[pid]SIPpTag00[call_number]
      [last_To:]
      Call-ID: [call_id]
      CSeq: [cseq] ACK
      [routes]
      Max-Forwards: 70
      Subject: Performance Test
      Content-Length: 0

    ]]>
  </send>

The [routes] keyword should result in a header field like the following:
Route: <sip:217.10.79.9;lr=on;ftag=5415SIPpTag001>,<sip:172.20.40.1;lr=on>

The current version truncates the string (depending on it's length). The commit 239 from the Sipp svn [1] fixes this problem (the patch is a one liner).

A modified source package is attached.

[1] http://sipp.svn.sourceforge.net/viewvc/sipp?view=rev&revision=239

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :
Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :
Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Can I report this bug upstream automatically?

Changed in sip-tester:
status: New → Fix Released
status: New → Fix Released
Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

This bug is mentioned here:
http://<email address hidden>/msg01829.html

I attached the source code patch for the debian package.

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

Wouldn't it be better to have a complete upgrade to the latest sipp stable version?
https://bugs.launchpad.net/ubuntu/+source/sip-tester/+bug/312680

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

As nobody seems to care about bugfix updates anyway, an upgrade to the 3.x series within the Jaunty release cycle will probably be the best option.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.