Answer the question
In order to leave comments, you need to log in
Why do RTP packets only go one way in Asterisk?
There was a virtual machine with asterisk on VMWARE, everything worked fine on it, I decided to install another one. VMWARE acts as a NAT, ports are forwarded through it. But with the second machine, rtp packets go only in one direction, from the machine, but do not arrive at it, the config is the same except for bind-port and extern-ip, where other ports other than 5060 are indicated. Well, different ports are opened accordingly for rtp.conf on different machines. What could be the snag? VMWARE is on windows server 2012 r2, maybe it's worth digging into the settings of the remote access and routing service?
Answer the question
In order to leave comments, you need to log in
Asterisk and NAT were on the same machine, and now they are on different ones?
Then you need to configure this same nat in the asterisk
RTP connection Natted to mismatched ports before and after nat. You need a SIP/RTP proxy that can change SIP packets on the fly and open the appropriate NAT ports that are negotiated for the proxied asterisk. With the first one, you are just lucky that by default (I observed the behavior on CentOS7), when you try to NAT the connection, it is checked whether it is possible not to change the port, and if so, it NATs into it. As an alternative, specify a different range of RTP ports on the second asterisk, and allocate port forwarding on NAT unchanged to this VM, the same with the SIP port, it might even work.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question