[SR-Users] NAT problem

[Daniel-Constantin Mierla]

Hello,

is Kamailio and RTPProxy (or Asterisk) using public IP addresses? Or they
listen on a private address and the firewall does port forwarding of a
public IP address?

Cheers,
Daniel

On Mon, Sep 16, 2019 at 10:51 AM Arnout Van Den Kieboom <
arnoutvdkieboom at gmail.com> wrote:

> Hi,
>
> First of all, I'm really new to Kamailio. So sorry if I ask a stupid
> question, or perhaps a really weird one.
>
> I started using kamailio in a test environment about a week ago.
>
> for setup i have the situation for inbound calls: Carrier --> FW (NAT) -->
> Kamailio
> for outbound to an asterisk box i have: Kamailio --> FW (NAT) --> Asterisk
> for outbound to users i have: Kamailio --> FW (NAT) --> sip-phone
> (yealink) or grandstream
>
> During that time i was able to :
> Set up calls to users,
> Use the dispatcher module
> use the avpops module to do data lookups.
> Get calls from asterisk to kamailio user to work.
> Also calls between users (even though behind nat) are having good audio.
>
> I have installed rtpproxy and it works nicely.
>
> There is just one situation where it fails:
>
> Carrier --> FW (NAT) Kamailio --> asterisk
>
> There is only one way audio (from asterisk to carrier) but not from
> carrier to asterisk.
>
> I believe I need to do something with the rtp proxy module ... and tried
> different things (forcing the r flag, forcing the w flag)
> Any idea where I might need to start looking? It's been driving me crazy...
>
> Thanks
>
> Pemp
>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>


-- 
Daniel-Constantin Mierla - https://www.asipto.com
https://twitter.com/miconda - https://www.linkedin.com/in/miconda
Kamailio Advanced Training - https://www.asipto.com/u/kat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190916/f3cde0c8/attachment.html>