| View previous topic :: View next topic |
| Author |
Message |
ksosunov
Joined: 02 Nov 2008 Posts: 2
|
Posted: Sun Nov 02, 2008 8:18 am Post subject: help needed |
|
|
hi all
I have the following problem.
There is an icecast2 server on the provider's side on my network. This server retranslates differebt radio stations in the locan netowrk.
At home I have Sonos system which is able to play internet radio.
So the problem is the following: when I try to connect from Sonos to icecast it (Sonos) thinks for about 30 seconds and then gives me the meassage connection to server was lost. But if after that I try to reconnect eveything is fine - so the connection is established only after 1st unsuccesful attempt.
The server itself seems to be ok - there is no such a problem if I try to connect winamp or WMP from PC. At the same time Sonos also seem to be capable of handling connections with icecast - I tried to connect it to various other icecast servers on the internet and it always connects right away. So I can't even guess what seem to be the problem. May it is some timeout value ort similar in config file? Any help will be appreciated. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Nov 02, 2008 4:54 pm Post subject: |
|
|
Depends on the exact failure, but it sounds like sonos , when performing the initial connection, is also waiting on something else to respond, like a DNS lookup. If this secondary request is stalled then it could prevent playback from icecast causing icecast to drop the connection. sonos then may decide to not do the secondary request after the first attempt fails giving you the effect you are seeing.
karl. |
|
| Back to top |
|
 |
ksosunov
Joined: 02 Nov 2008 Posts: 2
|
Posted: Sun Nov 02, 2008 6:53 pm Post subject: |
|
|
| karlH wrote: |
Depends on the exact failure, but it sounds like sonos , when performing the initial connection, is also waiting on something else to respond, like a DNS lookup. If this secondary request is stalled then it could prevent playback from icecast causing icecast to drop the connection. sonos then may decide to not do the secondary request after the first attempt fails giving you the effect you are seeing.
karl. |
Karl thanks for a swift response. I still have questions though. I don't think that it is DNS related feature - I am putting IP of the server into Sonos not its DNS name. Also, I still think this is the matter of configuration in this particular icecast because Sonos connects without problems with other icecast servers on Internet.
And in any case what would be the suggestion to overcome this issue?
Thanks. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Nov 02, 2008 8:13 pm Post subject: |
|
|
As I said, it depends on the exact reason for the timeout. Are the headers being sent, does icecast drop the player for being too slow, is it a connect timeout , have you checked the network traffic to see what is actually going over the link. Without knowing the specifics then it's hard to know what the specific cause of the problem. Sonos is not something I've used, so only the icecast logs would be helpful here.
karl. |
|
| Back to top |
|
 |
|