Daniel-Constantin Mierla writes:
> Hello,
>
> I didn't know about limitation, so far I needed only set_rtpengine_set()
> with one parameter. Now I am wondering why won't work for
> rtpengine_manage() because internally it calls the
> rtpengine_offer()/_answer().
I have never used
Hello,
I didn't know about limitation, so far I needed only set_rtpengine_set()
with one parameter. Now I am wondering why won't work for
rtpengine_manage() because internally it calls the
rtpengine_offer()/_answer().
Not being familiar with this use case, I would to do a test and watch
the
There is a use case mentioned "This is useful if you have a set of RTP
proxies that the caller must use, and another distinct set of RTP
proxies that the callee must use. This is supported by all rtpengine
commands except rtpengine_manage(). "
How do you actually implement this - is it something