headers
siproxd | 29 Oct 2004 14:20
Picon

local calls


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/
Permalink | Reply | 0 comments |
headers
Thomas Ries | 29 Oct 2004 18:39
Picon

Re: local calls

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, siproxd@... wrote:
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane