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

OME is not using persistent TCP connection for delivering LLDASH #564

Closed
jplogos opened this issue Nov 17, 2021 · 2 comments
Closed

OME is not using persistent TCP connection for delivering LLDASH #564

jplogos opened this issue Nov 17, 2021 · 2 comments
Labels

Comments

@jplogos
Copy link

jplogos commented Nov 17, 2021

PROBLEM

OME version: 0.12.1
We are using LLDASH feature in OME.
We see that OME is closing the connection to client(OME player) with [FIN, ACK] soon after each segment delivery.
As per the pcap trace we see the different TCP ports and that is of the fact that after each segment delivery the OME is closing the connection by issuing the [FIN, ACK]. please refer the attached image.

OME pcap trace image

EXPECTATION
We would like to know how to avoid OME closing the TCP connections after each segment delivery.
Also, is there any configuration available in OME to use persistent connections

ENVIRONMENTAL INFORMATION

  • OvenMediaEngine Information
    OME version: 0.12.1

  • Operating system and version

CentOS Linux release 7.9.2009 (Core)

@jplogos jplogos added the help label Nov 17, 2021
@getroot
Copy link
Member

getroot commented Nov 17, 2021

We've been too busy these days to do much on OME, but TCP keep-alive is one of our high priority tasks on our roadmap.
#548

@basisbit
Copy link
Contributor

basisbit commented Nov 21, 2021

This is a duplicate of #279. The current implementation of LL-DASH in OME thus is not usable except for in local network.

@getroot getroot closed this as completed Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants