16
Other Yate server issues / Re: Yate as a client behind a firewall
« on: September 21, 2016, 02:28:21 PM »
I suppose the problem with RTP (RTCP). Let me know am I right.
As I understand an incoming voice from A to B transfers to the IP and port which was previous one be delivered from B to A. But first voice frame transfers to the IP and port which was specified in SIP header.
So in my situation Yate listens a port the data which is delivered to is blocked by the outer firewall. If Yate first transfers the voice to other side (i.e. opens new outgoing connection) all next incoming voice frames will not be blocked by the firewall due to using outgoing connection.
In other words, do not be silent!
As I understand an incoming voice from A to B transfers to the IP and port which was previous one be delivered from B to A. But first voice frame transfers to the IP and port which was specified in SIP header.
So in my situation Yate listens a port the data which is delivered to is blocked by the outer firewall. If Yate first transfers the voice to other side (i.e. opens new outgoing connection) all next incoming voice frames will not be blocked by the firewall due to using outgoing connection.
In other words, do not be silent!