I added the #!define WITH_NAT option, and now the call can only be made one
way. RTPProxy was started like so:
$ rtpproxy -l 192.168.1.101 -s udp:localhost:7722 -u kamailio
root@kamailioA:~# netstat -pln | egrep "kamailio|rtpproxy"
tcp0 0 192.168.1.101:5060 0.0.0.0:*
On Wed, Jul 27, 2016 at 01:54:07AM -0400, SamyGo wrote:
> You need to enable NAT handling in your Kamailio (#!define WITH_NAT), then
> depending upon how your clients will interact with asterisk you may or may
> not need a media proxy, like RTPproxy. If asterisks can send/receive media
> directly
Hi Tickling,
Could you please share with us your working config?
With kind regards,
Jurijs
On Wed, Jul 27, 2016 at 8:54 AM, SamyGo wrote:
> Hi Again,
>
> You need to enable NAT handling in your Kamailio (#!define WITH_NAT), then
> depending upon how your clients will
Hi Again,
You need to enable NAT handling in your Kamailio (#!define WITH_NAT), then
depending upon how your clients will interact with asterisk you may or may
not need a media proxy, like RTPproxy. If asterisks can send/receive media
directly from the internet then its ok for now, else you
With the help of members from this mailing list (many thanks!), I finally
got Asterisk fronted by Kamailio for LB and REGISTERs and I am able to make
a call using the setup that looks like this:
[Kamailio 4.4.2]<->[Asterisk 13.7.2]
Kamailio manages REGISTERs, but also forwarding them to