Thx Brian, I understand that you can set the *destination* IP:Port via variables, but I was concerned with the source interface of the multicast traffic. And I just confirmed that on FreeBSD you do not need to specify a route in the single interface case because: "the default multicast route is via the interface with the default route; setting a route isn't necessary unless you need to force multicast to go via a particular interface by default, this is done by longest-prefix matching like all other IPv4 routing activities." They also state that: "An unprivileged userland application is also able to control where it is sending its multicast traffic (without mucking with the routing table) by using the sockopt IP_MULTICAST_IF. It can specify the address of any interface on the machine" But this would really be a hassle for the programmer :) Thx for your help! On Mon, Feb 22, 2010 at 4:35 PM, Brian West <brian@freeswitch.org> wrote:
The args to the app are the ip and port to send on...
/b
On Feb 22, 2010, at 4:27 PM, Luis F Urrea wrote:
Since this would be in the category of a host operation and there would be no need to forward multicast traffic between interfaces I thought that maybe there could be code in the esf application that would choose the IP it would bound to.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org