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

Point listeners to different listener URL #51

Open
redimongo opened this issue Jul 1, 2022 · 2 comments
Open

Point listeners to different listener URL #51

redimongo opened this issue Jul 1, 2022 · 2 comments

Comments

@redimongo
Copy link

So first love all the work @xiph is doing to support internet radio and broadcast. However we have an odd request.
We are wondering if it is possible to instead of showing server listener link on the YP directory, if instead we can put a custom URL listener link that is hosted say on our web server.

Why?
We have icecast servers in AU,US,UK and we have them clustered so they all get the same music etc etc. However the cluster does not send a user to the closest server so we created a script that can do that by looking at the users IP address.

We would almost call this a middleware solution to a small problem, but it's really cool from the part that a service provider can allow broadcasters to know that we are doing the server management and making sure that no listener has a bad experience.

So basically I want to change the published URL listener link to for example https://example.com/ID_of_Station and still publish it to YP directory.

@petterreinholdtsen
Copy link

petterreinholdtsen commented Oct 11, 2022 via email

@phschafft
Copy link
Member

Is there a ticket for this in the official ticket system?

Generally speaking you can just publish your stream to the YP directly. I mean if you already have infrastructure in front of your cluster, then said infrastructure should know best what to publish and do that itself. Publishing to the YP should be an easy task and would take individual servers out of the loop.

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