Skip to content
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

Closed
patrickarton opened this issue Nov 17, 2021 · 5 comments
Closed

RTP Timeout per caller/callee stream #1402

patrickarton opened this issue Nov 17, 2021 · 5 comments

Comments

@patrickarton
Copy link

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.

@arnd-s
Copy link

arnd-s commented Nov 18, 2021

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

@patrickarton
Copy link
Author

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.

@arnd-s
Copy link

arnd-s commented Nov 22, 2021

i created PR #1403.
It adds a new timeout config option and interface parameter: timeout-mode
off == notimeout / any == timeout on a single stream / all == timeout on all streams (old behavior).

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.

@patrickarton
Copy link
Author

i created PR #1403. It adds a new timeout config option and interface parameter: timeout-mode off == notimeout / any == timeout on a single stream / all == timeout on all streams (old behavior).

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.

@rfuchs
Copy link
Member

rfuchs commented Nov 23, 2021

Closing this to continue discussion on #1403

@rfuchs rfuchs closed this as completed Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants