I'm using an old version (unfortunately upgrading is not an option at the moment), and we're having issues that after a new port is negotiated (callee reINVITEthen 200OK), the callee is briefly sending RTP from the old port, which causes RTPproxy to fill in the old port as the new stream and "forget" the new port.
i.e. rxmit_packets: callee's address filled in .....
from what i can tell, this is occurring due to the "rxmit_packets" function in main.c, if i change it as below, will this address the issue by instituting a .01 second lag before the final fill-in? could this cause other issues?
Hi,
I'm using an old version (unfortunately upgrading is not an option at the moment), and we're having issues that after a new port is negotiated (callee reINVITEthen 200OK), the callee is briefly sending RTP from the old port, which causes RTPproxy to fill in the old port as the new stream and "forget" the new port. i.e. rxmit_packets: callee's address filled in .....
from what i can tell, this is occurring due to the "rxmit_packets" function in main.c, if i change it as below, will this address the issue by instituting a .01 second lag before the final fill-in? could this cause other issues?
change from:
to: