14 Jul
2014
14 Jul
'14
2:03 p.m.
On 07/14/14 09:45, Alex Balashov wrote:
After doing a little testing, what I can say is that
this only happens
with the rtpproxy-ng module, not regular rtpproxy module.
Whether it's a "misbehaviour" is hard to say. I'm still investigating.
This is because rtpproxy-ng/rtpengine always replaces the entire SDP
body, whereas rtpproxy only replaces individual parts (such as the port
number). Perhaps there's a better way to do this than using the lump
mechanism?
cheers