[SR-Users] Familiar topic about Kamailio with Asterisk behind NAT
osas at voipembedded.com
Thu Oct 1 00:17:38 CEST 2015
If you have kamailio bound to both private and public interfaces, then
you need to run rtpproxy in bridge mode (vanilla rtpproxy).
Another option is to get rid of the rtpproxy altogether and let
asterisk handle the media, but you will need to make sure that:
- kamailio is rewriting IPs in SDP provided by asterisk;
- you perform port forwarding for the NATed RTP ports to asterisk.
Also, you need to be more specific about the client trying to connect
to the private address of asterisk. Are you referring to media? In
this case it seems that you didn't engage rtpproxy. Is it about
signalling? Then you might deal with a bogus SIP client.
Take a look at other clients that are working and find out why this
particular one doesn't work.
On Wed, Sep 30, 2015 at 4:22 AM, Dirk Teurlings - SIGNET B.V.
<dteurlings at signet.nl> wrote:
> I found some existing topics on this but failed to get a solutions out of
> We're running into some issues with client devices connecting to our private
> addresses. The way it is setup now:
> CLIENTS <-> (NAT) <-> INTERNET <-> KAMAILIO(4.2.5) with RTPPROXY(v1)
> <-> PRIVATE LAN <-> ASTERISK (v1.8)
> Our Kamaialio and Asterisk are in a private address range, but Kamailio also
> has a public interface. Most of the clients (about 95%) work well with this
> setup, but a couple don't. We have one case now where the CLIENT tries to
> connect to the private address of ASTERISK. And of course, that doesn't
> I'm kind of stuck as to where I need to fix this. I tried using the
> externaddr option in Asterisk to solve it on that end. But that didn't help
> anything. The NAT options in Kamailio are not really suited for this, as
> they tend to fix client NAT problems.
> Any pointer or help would be greatly appriciated.
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
VoIP Embedded, Inc.
More information about the sr-users