How do I determine a router issue blocking DSP login?

seobrien · 11th June 2017, 02:16

Streaming server URL is "master.shoutcast.com".
Port is "8000".
Stream ID is "903975".
User ID is seobrien with the password I use to login online

Winamp Shoudcast DSP plugin doesn't connect
I'm getting the sense that there could be router or firewall issues but I don't follow how determine that and the logs aren't telling me anything.

Should I be entering the above information differently? User ID as seobrien@master.shoutcast.com (for example, I know that's not right)

2017-06-10 20:08:39 Connecting to... Server: master.shoutcast.com; Port: 8000; Mode: v2; Stream ID: 903975; DJ / User ID: seobrien
2017-06-10 20:08:39 Sending Cipher Request
2017-06-10 20:08:39 Cipher Response Received
2017-06-10 20:08:40 Automatically Switching SHOUTcast Protocol Mode From v2.x To v1.x
2017-06-10 20:08:45 Connecting to... Server: master.shoutcast.com; Port: 8000; Mode: v1; Stream ID: n/a; DJ / User ID: seobrien
2017-06-10 20:08:45 Sending Cipher Request
2017-06-10 20:08:45 Receiving Authorization Response
2017-06-10 20:08:46 Not Connected

djSpinnerCee · 11th June 2017, 04:37

probably not a router/firewall issue since the log indicates that you were able to make a connection and recieved a response.

if some blocking was going on, you would not be able to make the connection, and you would not see the negotiation that is occurring in the log.

it's possible that your server is not active yet (it takes time, hours to days, for a new config to become live).

seobrien · 11th June 2017, 15:11

Thank you for the reply. We learn

I'm also reading
Legacy encoders do not have the Stream ID field. As a result, fill out your password field then add ":#" and your Stream ID (after the password).
Example: abcde:#123456

Output 1, in Summary of the DSP plugin, says that it's Shoucast v1, which I'm led to believe is legacy.

Making me think that means we should NOT use the Stream ID field and should append the password as explained. Though that doesn't work either (and I'm only noting that for the sake of the thread and other support inquiries - the documentation isn't helpful).

Does Output 1 or Output 2 (which appears to be v2) matter? Does the Connect Using Automatic Mode matter?

I think I got it figured out and working, though no idea why, I'm asking the clarifying questions and providing more detail so that the documentation or others searching can find answers.

11th June 2017, 04:37	#2
djSpinnerCee Forum King Join Date: Aug 2004 Location: Hollis, Queens/The Bronx, NYC Posts: 3,512	probably not a router/firewall issue since the log indicates that you were able to make a connection and recieved a response. if some blocking was going on, you would not be able to make the connection, and you would not see the negotiation that is occurring in the log. it's possible that your server is not active yet (it takes time, hours to days, for a new config to become live). /* v2 HTML5 / Player test pages DigitalMixNYC, DigitalMixNYCbx \| DNAS Status: Now Playing js codes (scaststatus_X.php) \| PortForward.com \| Upload/Download Speed Test \| No-IP.com: Free Dynamic DNS \| In the YP \| dnasDir */

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

11th June 2017, 02:16	#1
seobrien Junior Member Join Date: Jun 2017 Posts: 2	How do I determine a router issue blocking DSP login? Streaming server URL is "master.shoutcast.com". Port is "8000". Stream ID is "903975". User ID is seobrien with the password I use to login online Winamp Shoudcast DSP plugin doesn't connect I'm getting the sense that there could be router or firewall issues but I don't follow how determine that and the logs aren't telling me anything. Should I be entering the above information differently? User ID as seobrien@master.shoutcast.com (for example, I know that's not right) 2017-06-10 20:08:39 Connecting to... Server: master.shoutcast.com; Port: 8000; Mode: v2; Stream ID: 903975; DJ / User ID: seobrien 2017-06-10 20:08:39 Sending Cipher Request 2017-06-10 20:08:39 Cipher Response Received 2017-06-10 20:08:40 Automatically Switching SHOUTcast Protocol Mode From v2.x To v1.x 2017-06-10 20:08:45 Connecting to... Server: master.shoutcast.com; Port: 8000; Mode: v1; Stream ID: n/a; DJ / User ID: seobrien 2017-06-10 20:08:45 Sending Cipher Request 2017-06-10 20:08:45 Receiving Authorization Response 2017-06-10 20:08:46 Not Connected

11th June 2017, 15:11	#3
seobrien Junior Member Join Date: Jun 2017 Posts: 2	Thank you for the reply. We learn I'm also reading Legacy encoders do not have the Stream ID field. As a result, fill out your password field then add ":#" and your Stream ID (after the password). Example: abcde:#123456 Output 1, in Summary of the DSP plugin, says that it's Shoucast v1, which I'm led to believe is legacy. Making me think that means we should NOT use the Stream ID field and should append the password as explained. Though that doesn't work either (and I'm only noting that for the sake of the thread and other support inquiries - the documentation isn't helpful). Does Output 1 or Output 2 (which appears to be v2) matter? Does the Connect Using Automatic Mode matter? I think I got it figured out and working, though no idea why, I'm asking the clarifying questions and providing more detail so that the documentation or others searching can find answers.