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

RTPEngine Support #4

Open
hyavari opened this issue Jun 20, 2023 · 5 comments
Open

RTPEngine Support #4

hyavari opened this issue Jun 20, 2023 · 5 comments

Comments

@hyavari
Copy link

hyavari commented Jun 20, 2023

Hi team,

Great work you did. Any plan for adding RTPEngine is there?

Thanks.

@adubovikov
Copy link
Member

Thank you! Depends what are you going to do ? NGCP ?

@hyavari
Copy link
Author

hyavari commented Jun 20, 2023

Actually, I am using the subscribe mechanism of RTPEngine for SIPREC, I thought that eBPF would be great for forking. Do you agree?

@lmangani
Copy link
Member

@hyavari interesting! we don't use this feature, so please feel free to share some examples for us to get inspired :)

@hyavari
Copy link
Author

hyavari commented Jun 20, 2023

In my current SIPREC server, I am sending subscribe request and answer to RTPEngine and then record forked streams. But I think what if we use your approach, eBPF I mean, and just filter streams based on IP and ports in the kernel level, and then in userspace remove IP headers and use the payload and etc. (I am just thinking loudly!)

@adubovikov
Copy link
Member

looks really interesting, yes, it can be possible by using XDP packet inspection and the receive function of RTPEngine.

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