From: Thomas R. <tr...@gm...> - 2004-10-29 16:39:47
|
Hello Mike, As mentioned in the documentation, siproxd MUST be running on the router / NAT-device between the private and public network. If you have additional NAT devices installed, it also depends on their behavior. Siproxd depends on "having access" to the network interface holding the internal (private) IP AND the network interface holding the external (public) IP. A local-UA to local-UA call looks: internal external IP IP UA1 ----+ | +- . . . . ---+ siproxd | +- . . . . ---+ | UA2 ----+ The RTP traffic is takes the full path through siproxd, there is no "Ah, it's a loop-back"-shortcut. Regards, /Thomas On 29 Oct, si...@mi... wrote: > > > > > I note from the FAQ that local call functionality was added v0.5.3 Feb > 2004. > > In my configuration, siproxd is running on a NAT/firewall with a private > LAN IP. To access the internet it goes through a separate ADSL NAT > router/firewall gateway. This works for incoming/outgoing calls, but > fails for internal private local UA-UA calls. > > I am guessing this is perhaps because siproxd relies on the UDP packets > being "loopedback" from the ADSL public IP? > > Can siproxd be configured to "loopback" locally without requiring packets > to be reflected from the public IP? > > Any suggestions? > > Thanks, > Mike. > > > > ------------------------------------------------------- > This Newsletter Sponsored by: Macrovision > For reliable Linux application installations, use the industry's leading > setup authoring tool, InstallShield X. Learn more and evaluate > today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ > _______________________________________________ > Siproxd-users mailing list > Sip...@li... > https://lists.sourceforge.net/lists/listinfo/siproxd-users -- GnuPG: pub 1024D/87BCDC94 2000-03-19 Thomas Ries <tr...@gm...> - Fingerprint = 13D1 19F5 77D0 4CEC 8D3F A24E 09FC C18A 87BC DC94 - Key via pgp.openpkg.org / http://www.ries.ch.vu/87BCDC94.pub VoIP: sip:174...@pr... |