-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTP Timeout per caller/callee stream #1402
Comments
Hello @patrickarton, this is currently not possible as far as i know. I made for our internal use some patches against an older version which basically works. I will try to update the patches to the newest development version and create a PR in the next days. I'll let you know... Arnd |
thanks for the reply. i will be very glad to see that patch included. i will wait from your updates. |
i created PR #1403. For best working: Start with timeout-mode=off (during early media) and when you receive a final answer (200 OK for example) activate timeout with timeout-mode=any. If you enable it on start of call establishment you will get a timeout if early media is one-way only. |
thank you very much. @arnd-s . i will test it. |
Closing this to continue discussion on #1403 |
Hello,
with --timeout option in rtpengine we delete the call if all streams of the call ( caller and callee ) did not received any rtp packet within this amount of time.
i looked in the code and did not see yet a way to enable --timeout only for one side stream.
For example even if caller streams are active (still sending packets) i want to close the call if callee streams are inactive ( did not received any packets within the --timeout option ).
Thanks.
The text was updated successfully, but these errors were encountered: