sc_serv_basic.conf, sc_trans_playlist.conf, sc_trans_basic.conf, sc_trans_dj.conf

[NitrofishRadio]

I am having problems connecting to sc_trans via v1, but my debug shows the refusal by the sc_trans or the calendar.xml to allow connection. Not sure which. Everything is set as it should be as far as I can see, but perhaps you can spot something I am missing. See debug below. default dj:noise being used and is enabled as far as I can see.

code:


2012-05-06 16:43:12	D	msg:[DJPROTOCOLSHOUTCAST] State EMPTY

2012-05-06 16:43:12	D	msg:[DJPROTOCOLSHOUTCAST] State NEEDPASS

2012-05-06 16:43:12	D	msg:[DJPROTOCOLSHOUTCAST] State CHECKPASS

2012-05-06 16:43:12	D	msg:[DJMGR] DJ `dj' requesting run permission

2012-05-06 16:43:12	D	msg:[DJMGR] DJ `dj' not enabled. Run permission denied.

2012-05-06 16:43:12	W	msg:[DJPROTOCOLSHOUTCAST] Login denied from dj:noise

2012-05-06 16:43:12	D	msg:[DJPROTOCOLSHOUTCAST] State SENDREPLY

2012-05-06 16:43:12	D	msg:[DJPROTOCOLSHOUTCAST] State KILL

2012-05-06 16:43:12	D	msg:[DJPROTOCOLSHOUTCAST] State KILL

2012-05-06 16:43:42	D	msg:[DJPROTOCOLSHOUTCAST] State EMPTY

2012-05-06 16:43:42	D	msg:[DJPROTOCOLSHOUTCAST] State NEEDPASS

2012-05-06 16:43:42	D	msg:[DJPROTOCOLSHOUTCAST] State CHECKPASS

2012-05-06 16:43:42	D	msg:[DJMGR] DJ `dj' requesting run permission

2012-05-06 16:43:42	D	msg:[DJMGR] DJ `dj' not enabled. Run permission denied.

2012-05-06 16:43:42	W	msg:[DJPROTOCOLSHOUTCAST] Login denied from dj:noise

2012-05-06 16:43:42	D	msg:[DJPROTOCOLSHOUTCAST] State SENDREPLY

2012-05-06 16:43:42	D	msg:[DJPROTOCOLSHOUTCAST] State KILL

2012-05-06 16:43:42	D	msg:[DJPROTOCOLSHOUTCAST] State KILL

Says dj is NOT ENABLED and denies the connection.

DJ_CALENDAR.XML

code:


<?xml version="1.0" encoding="UTF-8" ?>

<eventlist>



  <!-- if more DJ's are required in the system

       then we just add in more event blocks -->



  <event type="dj">

    <dj archive="1">dj</dj>

    <!-- for this example we will allow the DJ

         to connect to sc_trans at any time -->

    <calendar />

  </event>



</eventlist>

SC_TRANS_BASIC.CONF

code:


; NOTE: for any relative paths specified are relative to

; sc_trans and not to where the conf file is being stored





; here we will setup where the log and other related files

; will be stored. make sure that these folders exist else

; sc_trans will throw an error and will close itself down.

logfile=logs/sc_trans.log





; for the purpose of this test then we will not take into

; account the use of a calendar.xml file and so disable it

calendarrewrite=1





; for testing we will only setup a single encoder though it

; is easy to add in additional encoder configurations and

; we are using an aac plus encoder as the default due to

; the licensing requirements for mp3 encoding as detailed

; in sc_trans.txt - section 2.5).

encoder_1=mp3

bitrate_1=56000

encoder_2=mp3

bitrate_1=128000





; this is where we define the details required for sc_trans

; to connect to the sc_serv instance being used where the

; details must match those specified in sc_serv_basic.conf

outprotocol_1=3

serverip_1=XXX.XXX.XXX.XX





; default is 8000, if not change to sc_serv's 'portbase'

serverport_1=8000





unlockkeyname=XXXXX XXXXX

unlockkeycode=XXXXX-XXXXX-XXXXX-XXXXX





; this is the same as 'password' in sc_serv_basic.conf

password_1=XXXXXXXX



; this is the same as 'streamid' in sc_serv_basic.conf for

; the stream we are acting as the source for 

streamid_1=1

streamid_2=2





; this is a name for the source we're creating and is used

; with the AJAX control api or can be left blank to get a

; generic name created in the form of 'endpointX' where 'X'

; is the index of the created source from sc_trans lists.

endpointname_1=/Bob





; here you would provide any information to fill in details

; provided to clients about the stream. it us upto you what

; is entered though do not do anything which will annoy, etc

streamtitle=Nitrofish Radio

streamurl=http://www.NitrofishRadio.com

genre=Rock





; here we specify a playlist to use as the master list from

; which to play files from.

playlistfile=playlists/main.lst

playlistfile=playlists/weekdays.lst

playlistfile=playlists/weekends.lst





; these options will allow you access the admin interfaces

; of sc_trans though also allows the 'testui' example to be

; accessed. remember to change the password, etc as needed

adminport=7999

adminuser=admin

adminpassword=XXXXXXXX



xfade=7

xfadethreshold=90



djport=8500

djport2=8600

archive=archived/

djbroadcasts=recorded/



djlogin_1=dj

djpassword_1=noise

djpriority_1=4



;djlogin_2=dj2	

;djpassword_2=XXXXXX

;djpriority_2=2





; if we want to have an intro file for when the client gets

; the stream or a backup file incase of our connection to

; the server failing then we can set these. this is needed

; as we are using 'outprotocol=3' which supports this (and

; is needed in place of the sc_serv defined values to work)

;serverintrofile=intro/Ident-1-56-22050.mp3

;serverbackupfile=<specify_backup_filepath>

SC_TRANS.DJ.CONF

code:


; NOTE: for any relative paths specified are relative to

; sc_trans and not to where the conf file is being stored





; we use the sc_trans_basic.conf configuration file as the

; base configuration to work from for enabling DJ support

include=sc_trans_basic.conf





; here we enable support for a SHOUTcast 1 or SHOUTcast 2

; source as the DJ input though bear in mind the port usage

; as detailed in sc_trans.txt - section 3.0.3

djport=8500

djport2=8600





; NOTE: remember to change this to something else if needed

djlogin_1=dj





; NOTE: remember to change this to something else

djpassword_1=noise





; NOTE: remember to change this to something else if you do

;       setup multiple DJ's into the system as well as with

;       updating your calendar.xml to allow access for them

djpriority_1=4





; this is needed otherwise sc_trans will not allow DJ joins

; to be allowed to connect to the sc_trans instance.

calendarfile=calendar/dj_calendar.xml

Can someone please help me sort this out?

[DrO]

what configuration file are you using to run sc_trans? since if should be sc_trans_dj.conf for the example to work but that does not look like that is the case based on what you've posted. also does dj_calendar.xml existing in the 'calendar' folder for your install?

[edit]
bleugh, you're posting pretty much the same thing in multiple places - don't do that as it just makes things a nightmare to track through.

-daz

[NitrofishRadio]

Thanks and Sorry for the double post, but it seems like if I post to an old thread it does not get any responses for some reason. Perhaps I am not patient enough.

In regards to your question no I am not using sc_trans_dj.conf to run sc_trans. I am using sc_trans_playlist.conf to fire sc_trans.

Yes dj_calendar.xml does reside in the calendar folder of my install.

I guess that is what it is then. There is no DJ info in the PL_CALENDAR.XML so that is why it says not enabled.

I will add the DJ event there and that should allow me to login to the sc_trans and interrupt the stream.

I will report back.

Thanks!

[DrO]

that would explain your issue, sc_trans_playlist.conf is just an example for showing how to use the playlist features whereas sc_trans_dj.conf is an example for showing how to use the DJ features.

what you can do is include one in the other e.g. adding include=sc_trans_dj.conf into sc_trans_playlist.conf so the settings from both will be used with how you're running sc_trans. doing that will allow the playlist and dj settings to be loaded at the same time and then the DJ support should work.

[edit]
looks like you edited your post whilst i was replying as you've pretty much picked up what is needed without my reply.

-daz

[NitrofishRadio]

Yep that was it.... Just added the DJ stuff to the PL_CALENDAR.XML and all is good.

Thanks!

[NitrofishRadio]

What was the word on how to connect via v2? I know on v1 you just you pass the username and password as <djname>:<password> but how is it done on v2?

[DrO]

it depends on the source software you're trying to use and whether it supports v2. the key thing is to specify the value of 'djport2' for the port and then it's just username and password as with a v1 source (which should be taken as separate input options if a source is supporting all aspects of the v2 DJ support).

-daz

[NitrofishRadio]

The source is SAM 4.9.2 which does support v2 but it does not give input boxes for both the USERNAME and PASSWORD. It is just a single field for password, so then I take it you mean pass the username and password the same as v1 e.g. <djname>:<password> ?

[DrO]

SAM doesn't implement all of the v2 spec so you'll need to set it into v1 mode and do it in the <djname>:<password> method along with using 'djport' as the port to connect to. i know some people have had issues with trying to use SAM as a DJ source to sc_trans so it may not work (i'd have to check against the prior threads but as it's now going 11pm on sunday night for me i'm not going to do that until tomorrow).

-daz