Hello Alex,
I tried the flag loop-protect and it works.
I get the following message on the logs:
rtpengine[22968]: INFO: [fd72c95927567a5b]: Ignoring message as SDP has
already been processed by us
Thanks for your inputs!
Regards
On Fri, Jul 17, 2020 at 4:15 PM Alex Balashov
wrote:
> I thi
I think one angle on the problem is to identify why RTPEngine is being
invoked twice for the same SDP (most likely the same SIP message).
That's best done by looking at the content of the reinvite itself. Focus
especially on the Request URI and the Route header.
I am not sure if the RTPEngine
Thanks for your explanation Alex,
Actually i compiled the latest..git clone
https://github.com/sipwise/rtpengine.git
But still i dont have a clue on how to solve it, any advise?
Thank you
Mario
On Fri, Jul 17, 2020 at 2:34 PM Alex Balashov
wrote:
> This happens when an SDP body that has alrea
This happens when an SDP body that has already been passed to RTPEngine, and
already adulterated by RTPEngine, is passed to it yet again.
Newer versions of RTPEngine have a loop protection feature to deal with it. It
involves injecting an unregistered a=rtpengine attribute into the SDP, to say
Hello Everyone,
I have a scenario, where opensips is working with rtpengine . Call connects
fine with audio.
I have enabled reinvite pinging to keep the call alive ; when the reinvite
is sent to both legs of the calls i get error messages and NO AUDIO. The
reinvite has full SPD body.
some con
