Shoutcast and Proxy Problem

[kenpierce]

Hi All,

I'm sitting behind a proxy at Uni and I think the campus team have tightened it recently because Shoutcast has stopped working (as has some mms:// streaming).

Some machines here have external IP addresses (bypassing the proxy) and they have no problems. I can listen to stations running on port 80 (e.g. groovesalad from somafm, although the track info is always '1018').

For other stations however, Winamp simply skips through all the streams in the playlist. Some AAC streams seem to get an 'ICY 200 OK' but don't buffer, other fail silently.

I'd quite like to know what the proxy is saying to Winamp; is there a way to log the http requests/results, perhaps it's missing a header for example?

Do people have any other suggestions for getting Winamp through (or round?) a 'corporate' proxy?

Cheers,
Ken Pierce.

System Specs:

HP Compaq dc7700
Intel Core 2 Duo 6300 @ 1.86GHz; 3.50Gb RAM
On-Board Realtek High Definition Audio
Radeon X1300 256Mb
Windows XP Professional SP2
DirectX 9.0c
Winamp 5.35 Basic (Seperate Settings)

my_plugin_list.txt and hijackthis.txt attached.

[Sawg]

Well, violating corporate policy usually isn't a good thing. But make sure you have the latest version of Winamp installed and no third-party MP3 decoders. (Which doesn't look like you have)

'ICY 200 OK' is also common of AAC+ streams that Winamp cannot find the decoder play.

Other then that, there is packet sniffers, but that is beyond the scope here, and frowned upon by most IT departments.

When you can't play a stream hit Alt+3 and get the URL. Replace the http part with icy or icyx.

IE:
icyx://10.10.10.10:8000/
And try loading that URL (Ctrl+L)

[kenpierce]

Thanks for the speedy reply, Sawg.

'ICY 200 OK' doesn't seem a problem anymore, but all non port 80 streams just say [connecting to host]. No luck with icy:// or icyx:// either, so it doesn't look like protocol resolution is the problem.

I'm actually a Ph.D. student at the Computer Science department here and many of the staff are anti-proxy because it interferes with ligitimate research (as well as Winamp).

I might try the packet sniffer route to see what Winamp is sending and receiving. I have Admin rights on my machine so it should be fine.

I'll post updates on what I find.

Thanks,
Ken.

[kenpierce]

Oops, I'm a little silly. I had 'use proxy only for port 80 URLs' checked from a previous experiment.

icy:// now seems to work for the sampling of MP3 streams I tried, but track data isn't getting though (similar to streams on port 80, as mentioned previously).

Still getting 'ICY 200 OK' for AAC streams.

Cheers,
Ken,

[kenpierce]

A packet sniffing result, if this helps. Winamp successfully makes a connection and downloads data (numnerous packets flow in) but it doesn't seem willing to play it.

This was 'Groove Salad from SomaFM [aacPlus] [SomaFM]' resulting in the playlist entry:

"[HTTP/1.0 200 OK] icy://207.200.96.232:8012/"

Any thoughts?


GET http://207.200.96.232:8012/ HTTP/1.0
Host: 207.200.96.232
User-Agent: WinampMPEG/5.35
Accept: */*
Icy-MetaData:1
Connection: close


HTTP/1.0 200 OK
Date: Thu, 06 Sep 2007 16:30:48 GMT
X-Cache: MISS from bucket6.ncl.ac.uk
X-Cache-Lookup: MISS from bucket6.ncl.ac.uk:8080
Via: 1.0 bucket6.ncl.ac.uk:8080 (squid/2.6.STABLE13)
Proxy-Connection: close

ICY 200 OK
icy-notice1:<BR>This stream requires <a href="http://www.winamp.com/">Winamp</a><BR>
icy-notice2:SHOUTcast Distributed Network Audio Server/SolarisSparc v1.9.93atdn<BR>
icy-name:Groove Salad from SomaFM [aacPlus] [SomaFM]
icy-genreowntempo Ambient Groove
icy-url:http://SomaFM.com
content-type:audio/aacp
icy-pub:1
icy-metaint:24576
icy-br:64

** losts of binary data **

[Sawg]

It's seeing the "HTTP/1.0 200 OK" response, which it isn't expecting, instead of seeing the ICY response, which somes second.

Depending on the proxy, usually using icy:// (and I think uvox://) since it isn't HTTP the proxy will ignore it.

[kenpierce]

Right I see. Well using icy:// and uvox:// doesn't seem to make a difference for AAC streams. Is this a 'bug' in Winamp? Could it not be updated to look past an HTTP response and see if there's an ICY response coming?

Thanks,
Ken.

[Sawg]

Do you have no such issues with MP3 streams? Is it currently limited to AACPlus streams?

[kenpierce]

AACPlus streams don't work at all.

Adding icy:// to MP3 streams plays music but no track data is displayed (mildy annoying, I'm assuming it's a similar problem).

The mms:// streams I've tried (e.g. BBC Radio 4 [UK only] - mms://wmlive-acl.bbc.co.uk/wms/radio4/radio4_nb_e1s1) also don't work.

[Sawg]

Out of curiosity, do you have header captures for any of those?

[kenpierce]

Sawg, I've included the header captures in a zip to save messing up the thread.


MP3 streams (mp3_works.html)
----------------------------

I just tried some MP3 streams and I didn't need to add icy:// to get them to work (still no track data though). Not sure what I did before. I've included the headers to see if that sheds light on the AACPlus problem.


MMS streams (radio4.asx.html and radio4_nb_e1s2.html)
-----------------------------------------------------

The original URL is an http .asx file, which resolves into four streams (I've included the data for one).

Cheers,
Ken.

[kenpierce]

Hi all,

Can anyone see any solutions to this problem?

Cheers,
Ken.

[zizipoil]

Hey ken

well i have the same problem as yours.
I'm also behind a proxy and entering the address of its automatic configuration script is not working...
the most frustrating is that i'm able to see the interface of the radio choice (i mean the bars where you can look for radios in the media library)..

Well i'll try to get my proxy address (and not the configuration script for it).

i tried to use windows media player... and it works

Why am i condemned to use this crap???!!!!!

please, help us guys

Raph

[kenpierce]

Hi zizipoil,

If you download your proxy's configuration script and open it in notepad, you should be able to spot the IP address/port. Then put this into winamp.

Cheers,
Ken.

[zizipoil]

i managed to use it in the end!

all i did is give winamp the address of the proxy itselft and not the configuration script.

in my case, i just had to :

- replace prx by pixs
- remove the proxy.pac and set the correct port

in the end :

http://prx.xxx.xx.xxx.com/proxy.pac

becomes

http://pixs.xxx.xx.xxx.com:8080

AND IT WORKS!!!! wwwhoooohhhooooo!!!!!



One question : when can we pretend to a automatic configurable winamp??

Raph

[zizipoil]

i managed to use it in the end!

basicaly this is what ken said :

all i did is give winamp the address of the proxy itselft and not the configuration script.

in my case, i just had to :

- remove the http://
- replace prx by pixs
- remove the proxy.pac and set the correct port

in the end :

"http://prx.xxx.xx.xxx.com/proxy.pac"

becomes

"http://pixs.xxx.xx.xxx.com:8080"

AND IT WORKS!!!! wwwhoooohhhooooo!!!!!



One question : when can we pretend to an automatic configurable winamp??

Raph

[kenpierce]

Proxy scripts (.pac) are generally written in javascript, which is nice and easy for a web-browser to resolve (because it's already built-in). Winamp however doesn't have that luxury so it's a lot harder. I suppose you could write a regex to search for IP addresses but it wouldn't be foolproof.

Anyway, I'm glad your problem is sorted. My problem is that even after I put the proxy in it doesn't work

Cheers,
Ken.

[coderWinAmper]

kenpierce, did you check out this thread: http://forums.winamp.com/showthread....hreadid=277229
?

[kenpierce]

Sorry, I just got 'URL submitted by user' there insteal of a link.

Cheers,
Ken.

[coderWinAmper]

Yeah, just hit quote and you'll see the link. It's a thread in the same forum as this one, name "Salvation for the [Error syncing to stream] while tunneling".

Set up an encrypted proxy tunnel and you can listen to anything.