Killy, You were absolutely right. In some cases, they were leaving via eth0.
The default route of the box is via eth0. Using ³ip route add table² and then ³ip rule add from² I send all traffic sourced from eth1¹s IP to a router connected to eth1. In this way on all my voice-enabled boxes I keep the voice traffic on the voice network (eth1) and the non-voice traffic on eth0. In this case it seems somehow Mediaproxy is slipping past the rule that sends traffic via the different gateway. But, only some of the time. Mediaproxy¹s RTP (during 183) leaves via eth1 until the second host begins sending traffic to Mediaproxy. Once that happens, all Mediaproxy¹s RTP leaves via eth0. Very strange. All media after 200 is also leaves via the wrong interface. - Jeff On 12/15/08 10:55 PM, "Wasin Thiengkunagrit" <[email protected]> wrote: > Hi Jeff, I thought that it seems to be possible that MediaProxy send the > packet to another interface card. Can you try this command to capture the > packets ? "tcpdump -w mydump.cap -i any udp" Cheers, Killy 2008/12/16 Jeff > Pyle <[email protected]>: > Hello, > > I have a working OpenSIPS 1.4 + > Mediaproxy 2.1 configuration. At the > moment, no NAT is involved, and > opensips.cfg is set to engage_media_proxy() > on all initial invites. It > works just fine. > > I created a pcap file with the command "tshark w mp.pcap > i eth1 udp", > causing all the udp on interface eth1 (where OpenSIPS and > Mediaproxy > function) to dump to mp.pcap. During the 183 Session Progress > and after the > call was established with 200 OK, I see the RTP packets > arriving into > Mediaproxy. But I do not see them leaving the box destined > for the other > side. Yet I seem to have perfect two-way audio on the > call. > > Is Mediaproxy sending the packets at such a level where > Wireshark/tshark > misses them? > > > Thanks, > Jeff >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
