I've encountered the same behavior. If I understand you correctly, it
is *receiving* media on 1.20.39.41 (eth1:5) but *sending* from
1.20.39.34 (eth1).
This is asymmetric RTP (send/receive on on different addrs) and is fully
valid/legal/whatever. Notice that the 200 OK contains (correctly)
1.20.39.41 in the SDP.
The reason is that sipp doesn't appear to bind to the -mi addr for send,
only for receive. In that case, send will use the first interface that
the route table returns as routable to the destination (172.20.32.74),
which I assume routes from eth1.
The only way I've effectively worked around it is to set eth1 as the
media address. You might possibly get the result you want by playing
with routing policies using iproute2, but I haven't tried that yet.
In short, whatever 'ip ro get 172.20.32.74' returns will be used as the
source of the media stream.
-David
-----Original Message-----
From: Mathers, Kevin [mailto:kmath...@sonusnet.com]
Sent: Tuesday, May 11, 2010 1:15 PM
To: sipp-users@lists.sourceforge.net
Subject: [Sipp-users] sipp sending media from wrong source address
usingpcap feature
I have sipp installed on a linux machine with multiple physical
interfaces and several sub interfaces (see below). I'm trying to send
rtp using a pcap file using the -i and -mi options. Rather than using
the sub interface specified, it's taking the physical interface. What
can I do to resolved this?
sipp -sf uastest.xml -d 90000 -i 1.20.39.41 -mi 1.20.39.41 -trace_msg
<snip>
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
