[Users] via header not added when transport=TCP?

[Erich Nahum]

Howdy,

I'm playing with OPENSER 0.9.5 with sipp as the workload generator on
a bunch of linux boxes.  When the transport is UDP, openser adds a
via header like it is supposed to as a proxy.  But when I use TCP no
via header is added.  This is a UAC->proxy->UAS scenario.  Here's the
header as seen at the UAS:

| UDP message received [633] bytes :
| 
| INVITE sip:service at 10.0.1.41:5060 SIP/2.0
| Record-Route: <sip:10.0.1.42;ftag=1;lr=on>
| Via: SIP/2.0/UDP 10.0.1.42;branch=z9hG4bKe9cc.cc24a79.0
| Via: SIP/2.0/UDP bronxville1:5060;received=10.0.1.40;branch=z9hG4bK-1-0
| From: sipp <sip:sipp at bronxville1:5060>;tag=1
| To: sut <sip:service at 10.0.1.41:5060>
| Call-ID: 1-31891 at bronxville1
| CSeq: 1 INVITE
| Contact: sip:sipp at bronxville1:5060
| Max-Forwards: 16
| Subject: Performance Test
| Content-Type: application/sdp
| Content-Length:  132
| P-hint: outbound

And the corresponding message received at the UAS when using TCP:

| TCP message received [495] bytes :
| 
| INVITE sip:service at 10.0.1.41:5060 SIP/2.0
| Via: SIP/2.0/TCP bronxville1:5060;branch=z9hG4bK-1-0
| From: sipp <sip:sipp at bronxville1:5060>;tag=1
| To: sut <sip:service at 10.0.1.41:5060>
| Call-ID: 1-31865 at bronxville1
| CSeq: 1 INVITE
| Contact: sip:sipp at bronxville1:5060
| Max-Forwards: 70
| Subject: Performance Test
| Content-Type: application/sdp
| Content-Length:  132

Note the absence of the 2nd Via header.  Openser complains about this on
the way back to the UAC.

Any suggestions appreciated.

Thanks,

-Erich
-- 
Erich M. Nahum                  IBM T.J. Watson Research Center
Research Staff Member           P.O. Box 704
nahum at watson.ibm.com            Yorktown Heights NY 10598