Results 1 to 5 of 5

Thread: Wowza and shoutcast DNAS 2 Beta

  1. Default Wowza and shoutcast DNAS 2 Beta

    Does Wowza support shoutcast DNAS 2 beta already?

    http://www.shoutcast.com/download

    Thanks.

  2. #2

    Default

    I do not think so. Someone else this week reported that it does not work. I believe there is a new protocol which we have not implemented:

    All-new SHOUTcast YP2 protocol

    Wowza supports the ICY2 protocol.

    Charlie

  3. #3

    Default

    I'll fire this up today and report back results.

    I am suspecting that the listen link is different and may need additional parsing by Wowza.

    Shamrock

  4. #4

    Default

    There is a simple fix, however needs an option in the Wowza side of things.

    Example walk through, just so everyone has clarity

    Shoutcast 2 configuration
    Code:
    portbase=8000
    password=changeme
    adminpassword=changeme
    relayshoutcastdebug=1
    relaydebug=1
    screenlog=1
    publicserver=never
    log=1
    yp2=1
    logfile=./test.log
    streamid_1=5
    streamauthhash_1=123456789ab
    streampath_1=/test.aac
    streamrelayurl_1=http://a.b.d.e:yyyy
    This is setup to relay just any Shoutcast 1 server but should suffice. The content on the remote side is aac and for this to work the streampath must end in .aac or .mp3 (depending on the content). The IP address of the shoutcast2 server was 192.168.1.1 and running on port 8000 (as per the config file).

    On the Wowza side and Application called Shoutcast2Test was set up as per a normal Shoutcast configuration

    In the content directory a file called

    shoutcast2.stream

    had the content

    http://192.168.1.1:8000/test.aac

    Now if you ask Wowza to connect you get this in the logs

    Code:
    INFO server comment - ShoutCastReceiver.init: shoutcastMP3GroupCount:4
    INFO server comment - LivePlayer.play[Shoutcast2Test/_definst_/shoutcast2.stream]: Dynamic Stream Markers are on.
    INFO server comment - ShoutCastReceiver.internalConnect: http://192.168.1.1:8000/test.aac
    INFO server comment - ShoutCastDecoder.checkHeader[shoutcast2.stream]: HTTP OK
    WARN server comment - ShoutCastDecoder.addChunkDataMP3[shoutcast2.stream]: Hunting.
    INFO server comment - ShoutCastReceiver.resetConnection: (SOCKET, R: /192.168.1.1:8000, L: /WOWZAIP:33614, S: /192.168.1.1:8000)
    INFO server comment - ShoutCastReceiver.sessionClosed:
    INFO server comment - ShoutCastReceiver.sessionClosed: reconnect: isCurrentSession:false tryConnect:true
    INFO server comment - ShoutCastReceiver.internalConnect: http://192.168.1.1:8000/test.aac
    INFO server comment - ShoutCastDecoder.checkHeader[shoutcast2.stream]: HTTP OK
    WARN server comment - ShoutCastDecoder.addChunkDataMP3[shoutcast2.stream]: Hunting.
    INFO server comment - ShoutCastReceiver.resetConnection: (SOCKET, R: /192.168.1.1:8000, L: /WOWZAIP:33614, S: /192.168.1.1:8000)
    INFO server comment - ShoutCastReceiver.sessionClosed:
    INFO server comment - ShoutCastReceiver.sessionClosed: reconnect: isCurrentSession:false tryConnect:true
    INFO server comment - ShoutCastReceiver.internalConnect: http://192.168.1.1:8000/test.aac
    INFO server comment - ShoutCastDecoder.checkHeader[shoutcast2.stream]: HTTP OK
    WARN server comment - ShoutCastDecoder.addChunkDataMP3[shoutcast2.stream]: Hunting.
    INFO server comment - ShoutCastReceiver.resetConnection: (SOCKET, R: /192.168.1.1:8000, L: /WOWZAIP:33614, S: /192.168.1.1:8000)
    INFO server comment - ShoutCastReceiver.resetConnection: null
    INFO server comment - ShoutCastReceiver.sessionClosed:
    INFO server comment - ShoutCastReceiver.sessionClosed: reconnect: isCurrentSession:false tryConnect:true
    INFO server comment - ShoutCastReceiver.internalConnect: http://192.168.1.1:8000/test.aac
    INFO server comment - ShoutCastDecoder.checkHeader[shoutcast2.stream]: HTTP OK
    WARN server comment - ShoutCastDecoder.addChunkDataMP3[shoutcast2.stream]: Hunting.
    INFO server comment - ShoutCastReceiver.resetConnection: (SOCKET, R: /192.168.1.1:8000, L: /WOWZAIP:33614, S: /192.168.1.1:8000)
    INFO server comment - ShoutCastReceiver.resetConnection: null
    INFO server comment - ShoutCastReceiver.resetConnection: null
    INFO server comment - ShoutCastReceiver.resetConnection: null
    INFO server comment - ShoutCastReceiver.sessionClosed:
    INFO server comment - ShoutCastReceiver.sessionClosed: reconnect: isCurrentSession:false tryConnect:true
    INFO server comment - ShoutCastReceiver.resetConnection: null
    If you ask the Shoutcast2 server what is going on, you get the following

    If you pretend to be a Winamp client, you get this

    Code:
    HTTP/1.1 200 OK
    Server: Ultravox 2.0
    Content-Type: misc/ultravox
    icy-pub: 0
    Ultravox-Max-Msg: 16377
    Ultravox-SID: 5
    Ultravox-Avg-Bitrate: 56000
    Ultravox-Max-Bitrate: 56000
    
    Z9x<metadata>
     <length>0</length>
     <song>
       <name>Digitalis - Airwalk (Parallaxia Remix)</name>
     </song>
    </metadata>
    [MP3 or AAC payload data in UVox 2 or UVox 2.1 format]
    If you pretend to be a Windows Media client, you get this

    Code:
    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/posix(linux x86) vFeb 17 2011<BR>
    icy-name:Tag's Trip  [SomaFM]
    icy-genre:Dance Trance House
    icy-url:http://www.somafm.com
    content-type:audio/aacp
    icy-pub:0
    icy-br:56
    [MP3 or AAC raw data]
    So if an additional variable could be added to Wowza to specify a User-Agent this would work. But also, sending the Meta-Int tag too, so keeping access to the meta data would be useful.

    Shamrock

    ps. sorry for the long post, but wanted to show the differences of the two in the simplest way.

    pps. the simplest fix is to change the Wowza user agent used to 'WowzaMediaServer' and it should work as before.
    Last edited by shamrock; 02-21-2011 at 03:20 AM.

  5. #5

    Default

    Now is shoutcast DNAS 2 suported by Wowza 3?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •