Asterisk does not like multiple interfaces in the way you are configured. You can either:
A) use the bindaddr in the sip.conf to limit where the packsge come and go. B) use an outside traffic manager Look up the archives, kpf explained why this would not work, as asterisk can't do load balancing at this time -----Original Message----- From: "Robert Webb" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com> Sent: 3/7/06 11:27 AM Subject: Re: [Asterisk-Users] Oh this is bad.... bindaddr and rtp traffic On Tue, 7 Mar 2006 09:12:25 -0700 "Douglas Garstang" <[EMAIL PROTECTED]> wrote: > I have a configuration where RTP traffic is going out >interface pub0, and coming back into through pub1. > I have bindaddr=0.0.0.0 in sip.conf, and a netstat -an >shows: > > udp 0 788 0.0.0.0:5060 0.0.0.0:* > > which means that Asterisk is listening on all addresses >(on all interfaces?). > > Anyway, when the RTP traffic comes back in on interface >pub0, Asterisk does nothing with it. A 'rtp debug' shows >it's receiving the RTP packets, it just seems it does >nothing with them. > > Anyone seen this? > > Doug. > > I thought all RTP was controlled through rtp.conf and only the SIP traffic was controlled through SIP.conf. I am not sure what settings, beside the RTP port range, you can out into the rtp.conf though. Robert _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
