Open a issue here http://projects.ag-projects.com/projects/mediaproxy/issues
On May 28, 2013, at 12:53 PM, Jerzy Ptak wrote: > Hi, > > I have spent some time trying to debug this issue. > Despite the fact that depending on the individual case you can find > workarounds, this is a mediaproxy issue. The problem is caused by the way > mediproxy is processing media packets and setting up forwarding rules. > > Before the forwarding rules are set up, mediaproxy waits and passes on media > packets between both sides of the session. When mediaproxy receives at least > on media packet from each side then it is setting up forwarding rules. It > seems to be that, because the forwarding rules setup is not atomic there is a > time window in which media packet that have been handled by mediaproxy will > be sent out by the system (kernel) from the incorrect port. > > I have created a fix for this issue, which I am allowed to contribute back to > mediaproxy. Can somebody from mediaproxy team let me know where can I submit > the fix. > > > Regards > Jerzy Ptak > > -- > Jerzy Ptak > Purple Communications Europe Ltd. > Office: +44-1275-371700 > Email: [email protected] > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
