Maxim Sobolev wrote:
Klaus Darilion wrote:
The old rtpproxy (1.1.1.1) has to wait for at least one packet from each client. For the new version of rtpproxy it depends on the configuration, i.e. if the rtpproxy is symmetric on both ends or only on one end.
The default behaviour is to start relaying immediately to the port specified in the SDP, but once the firt packet from UA has been received check that actual source port match and update internal session data if it does not so that all subsequent packets will be relayed to the proper "NAT hole".
Cool, a nice feature - I guess I should give the new rtpproxy a try. :-)
Klaus