Hi guys, can anyone run by me how to set this up? I have followed the plugin and config file integration but more my question is about what to do next. How do I relate Icecast streams to amember subscription packages? Do I put something into the secure folder for each amember secure file so that fires up the stream once the client has accessed amember with their amember uid and password, or does it happen from icecast's end, as in, from the radio page ? Any experience would be much appreciated here. Thanks Guy
Hi, Have a look: http://www.icecast.org/docs/icecast-2.3.1/icecast2_listenerauth.html In short, authentication wil be done by icecast itself. It will ask login/password and send it to aMember. If user is valid aMember will return special header and user will be allowed to access.
Thanks ALex. What do I put into Amember for it to associate with an Icecast account? Can it be used for multiple streams? I have an icecast server that will have multiple streams and different accounts will need to be set up for different streams. Where in amember do I add the what data for icecast to connect / pass login/password data to? I see in the plugin readme the {$config.root_url/amember/plugins/protect/icecast/i.php but how does this know that I have subscriber a connected to Icecast stream a? Thanks
You set protection levels in icecast config itself. For example create several mounts (that should have different protection levels) and in each mount configuration specify listener_add url in such format: amember/plugins/protect/icecast/i.php?product_ids=1,2 above will allow to access only for users who have product 1 or 2
Ok I think I get it. So the product id is set by stream. I thought I had this sorted yesterday with Anton but i did get it wrong. IF the product Id is entered into the configuration on a stream by stream basis then this works because you then associate a stream with a product ( or as you mentioned a group of products). Is this the case? I am still trying to get my support to help me get access to the icecast configuration file. If there is only one configuration file for the whole icecast server then it surely can't work for multiple streams because it will give any subscription access to any stream. I want to set up more than one different subscription products to manage members for more than one stream
Question: From the amember icecast plugin readme instructions; quote: http://www.ambientmusicgarden.com/amember/amember/plugins/protect/icecast/i.php?product_ids=1,2 will give access only to customers having subscription to products #1 and #2 unquote I have two streams I want to offer as subscription services. Each stream is independent of the other so clients can choose one stream to subscribe to. Does this mean, if I have two amember products (1) and (2), can I have stream (a) for members subscribed to product 1, and stream (b) for subscribers of product 2 Im not sure exactly what as yet I would need to add into the product details to achieve the connection between amember product and icecast stream, probably just the stream URL/port. OR does this mean amember will confirm ANY subscriptions to EITHER amember products (1) OR (2) for ANY stream? This greatly reduces the opportunity for the integration of numerous subscription services and I hope is not the case. This is critical to my understanding and my business model so please can you clarify which one is correct. I will post this to support as well since it is so important to me. Thanks Guy
Guy, If you want to offer separate access to each stream you should use http://www.ambientmusicgarden.com/amember/plugins/protect/icecast/i.php?product_ids=1 for first stream, which will give access to user's of product # 1 only. and http://www.ambientmusicgarden.com/amember/plugins/protect/icecast/i.php?product_ids=2 for second. In product setting just specify steam url. User will see that link in member's area after login.