[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0911301123110.17037@router.home>
Date: Mon, 30 Nov 2009 11:27:04 -0600 (CST)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Patrick McHardy <kaber@...sh.net>
cc: Christian Hentschel <chentschel@...et.com.ar>,
netdev@...r.kernel.org
Subject: Re: SIP proxying: siproxd vs. Netfilter SIP nat
On Mon, 30 Nov 2009, Patrick McHardy wrote:
> > http://people.netfilter.org/chentschel/docs/sip-conntrack-nat.html
>
> That documentation is horribly outdated.
Where do I find more recent documentation?
> > Isnt there a way to make the kernel module work in the same way siproxd
> > works and able to support multiple phones? Right now configuring SIP
> > connectivity is a messy thing that is not easily setup. Can we fix this?
>
> It should work fine with multiple phones, it even recognizes calls
> between two internal phones and makes the media stream go between
> them directly. Depending on how your registrar/proxy works, you might
> have to set one or both of these module options:
Loaded both sip modules without specifying any parameters. Resulted in one
way audio problems which is what I also get without the modules.
> sip_direct_signalling: when set to zero, allows incoming signalling
> connections from other hosts than the registrar. Usually not needed.
>
> sip_direct_media: when set to zero, allows incoming media streams
> from other hosts than the registrar. This one is often required,
> some providers use server farms for handling the media streams,
> some set up media streams to go directly between the endpoints.
Ok will try setting that parameter to zero.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists