3 Aug
2005
3 Aug
'05
1:35 p.m.
The request sent over TCP is sent directly to 10.0.1.41, not to
10.0.1.42 (which I suppose is the proxy).
Jan.
On 02-08-2005 07:58, Erich Nahum wrote:
Howdy,
I'm playing with SER 0.9.3 with sipp as the workload generator on
a bunch of linux boxes. When the transport is UDP, openser adds the
record-route and via headers like it is supposed to as a proxy. But
when I use TCP these headers are not added. This is a UAC->proxy->UAS
scenario.
I'm attaching ethereal dumps of the UDP-based UAC, TCP-based UAC, UDP-based
UAS, and TCP-based UAS for reference.
Any suggestions appreciated.
Thanks,
-Erich
--
Erich M. Nahum IBM T.J. Watson Research Center
Research Staff Member P.O. Box 704
nahum(a)watson.ibm.com Yorktown Heights NY 10598
Frame 7 (537 bytes on wire, 537 bytes captured)
Ethernet II, Src: 00:11:25:29:11:5d, Dst: 00:0d:60:9d:30:3f
Internet Protocol, Src Addr: 10.0.1.40 (10.0.1.40), Dst Addr: 10.0.1.42 (10.0.1.42)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:service@10.0.1.41:5060 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Via: SIP/2.0/UDP bronxville1:5060;branch=z9hG4bK-1-0
From: sipp <sip:sipp@bronxville1:5060>;tag=1
SIP from address: sipp <sip:sipp@bronxville1:5060>
SIP tag: 1
To: sut <sip:service@10.0.1.41:5060>
Call-ID: 1-28105@bronxville1
CSeq: 1 INVITE
Contact: sip:sipp@bronxville1:5060
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 132
Message body
Session Initiation Protocol
Request-Line: INVITE sip:service@10.0.1.41:5060 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Via: SIP/2.0/TCP bronxville1:5060;branch=z9hG4bK-1-0
From: sipp <sip:sipp@bronxville1:5060>;tag=1
SIP from address: sipp <sip:sipp@bronxville1:5060>
SIP tag: 1
To: sut <sip:service@10.0.1.41:5060>
Call-ID: 1-27019@bronxville1
CSeq: 1 INVITE
Contact: sip:sipp@bronxville1:5060
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 132
Message body
Frame 10 (676 bytes on wire, 676 bytes captured)
Ethernet II, Src: 00:0d:60:9d:30:3f, Dst: 00:0d:60:9d:73:db
Internet Protocol, Src Addr: 10.0.1.42 (10.0.1.42), Dst Addr: 10.0.1.41 (10.0.1.41)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:service@10.0.1.41:5060 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Record-Route: <sip:10.0.1.42;ftag=1;lr=on>
Via: SIP/2.0/UDP 10.0.1.42;branch=z9hG4bKcf89.f46403c6.0
Via: SIP/2.0/UDP bronxville1:5060;received=10.0.1.40;branch=z9hG4bK-1-0
From: sipp <sip:sipp@bronxville1:5060>;tag=1
SIP from address: sipp <sip:sipp@bronxville1:5060>
SIP tag: 1
To: sut <sip:service@10.0.1.41:5060>
Call-ID: 1-26914@bronxville1
CSeq: 1 INVITE
Contact: sip:sipp@bronxville1:5060
Max-Forwards: 16
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 132
P-hint: outbound
Message body
Frame 16 (561 bytes on wire, 561 bytes captured)
Ethernet II, Src: 00:11:25:29:11:5d, Dst: 00:0d:60:9d:73:db
Internet Protocol, Src Addr: 10.0.1.40 (10.0.1.40), Dst Addr: 10.0.1.41 (10.0.1.41)
Transmission Control Protocol, Src Port: 56280 (56280), Dst Port: 5060 (5060), Seq: 1,
Ack: 1, Len: 495
Session Initiation Protocol
Request-Line: INVITE sip:service@10.0.1.41:5060 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Via: SIP/2.0/TCP bronxville1:5060;branch=z9hG4bK-1-0
From: sipp <sip:sipp@bronxville1:5060>;tag=1
SIP from address: sipp <sip:sipp@bronxville1:5060>
SIP tag: 1
To: sut <sip:service@10.0.1.41:5060>
Call-ID: 1-26885@bronxville1
CSeq: 1 INVITE
Contact: sip:sipp@bronxville1:5060
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 132
Message body
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers