Register
Results 1 to 7 of 7

Thread: oscam tutorial

  1. #1
    Newbie
    Join Date
    Oct 2008
    Posts
    2
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default oscam tutorial

    Does anybody know o step by step tutorial to setup oscam in order to conect 2 dreambox.

  2. #2
    Junior Member
    Join Date
    Jul 2010
    Posts
    23
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    For starters what box u using and what image

  3. #3
    Newbie
    Join Date
    Oct 2008
    Posts
    2
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default Oscam cfg

    2 Dm 500 with Gemini 4.20

  4. #4
    Junior Member
    Join Date
    Jul 2010
    Posts
    23
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    I use oscam/mgcam or oscam/mbox. Oscam is card reader and mgcam is client. I believe that there is a way to use oscam both as server and client by using the API feature inside the oscam.conf file but this is something that I am not familiar with. Im sure that someone will correct me if Im wrong. These settings are basic but should work ok. There is much scope for tweaking oscam afterwards if required.

    After installing the oscam/mgcam there are 4 main files to configure.
    oscam.conf
    oscam.server
    oscam.user
    newcamd.list
    -----------------------------------------------------
    oscam.conf
    #
    # main configuration
    #

    [global]
    nice = -1
    waitforcards = 1

    readerrestartseconds = 0
    saveinithistory = 1

    # logging

    pidfile = /tmp/oscam.pid

    disablelog = 1
    disableuserfile = 1

    # monitor

    [monitor]
    port = 988
    aulow = 120
    monlevel = 0

    hideclient_to = 45

    # web interface

    [webif]
    httpport = 8888
    httpuser = oscam
    httppwd = oscam

    httprefresh = 5
    httphideidleclients = 1
    httpallowed = 0.0.0.0-255.255.255.255
    httpreadonly = 0

    # protocols

    [newcamd]
    key = 01 02 03 04 05 06 07 08 09 10 11 12 13 14
    port = 52010@0963:000000
    -----------------------------------------------------------------
    Pay attention to the [newcamd] section. The key and port must match the one used in the users box cws line in newcamd.list file. You must also add correct caid and ident to the port line. In this case it is for white sly card. You can use any port and 52010 is for example only.

    Our card reader next. This is for lower or single internal slot.

    oscam.reader
    label = SCI1
    enable = 1
    protocol = internal
    device = /dev/sci0
    services =
    caid = 0963
    boxid = xxxxxxxx
    detect = cd
    group = 1
    emmcache = 1,3,2m.server
    ---------------------------------------------------------------
    Add boxkey if applicable and caid for your particular card.

    Oscam.user
    [account]
    user = Mgcamd #for your reader box
    pwd = Mgcamd
    group = 1
    au = 1 # Auto Update if required
    caid = 0963

    [account]
    user = box2 #Your second box
    pwd = box2
    group = 1
    caid = 0963


    newcamd.list

    Add this line to reader box

    CWS = 127.0.0.1 52010 Mgcamd Mgcamd 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan local

    Add this one to box2
    CWS = IP_of_Box1 52010 box2 box2 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan local
    The rest of the files configs on box2 can be left pretty much bog standard as its only acting as client. The important part is the cws line.

    That should do it. I park my oscam and mgcamd configuration files in var.keys.

    Here is a start script for Gemini to start up both cams. I use this on my 800 but should be ok for 500 as well. Chmod it 755
    --------------------------------------
    mgcamd_oscam_cam.sh


    CAMD_ID=4396
    CAMD_NAME="Mgcamd/OSCam"
    CAMD_BIN=oscam
    CAMD_BIN2=mgcamd

    INFOFILE_A=ecm0.info
    INFOFILE_B=ecm1.info
    INFOFILE_C=ecm2.info
    INFOFILE_D=ecm3.info
    #Expert window
    INFOFILE_LINES=1111111111000000
    #Zapp after start
    REZAPP=0

    ########################################

    logger $0 $1
    echo $0 $1

    remove_tmp () {
    rm -rf /tmp/*.info* /tmp/*.tmp*
    }

    case "$1" in
    start)
    remove_tmp
    /var/bin/$CAMD_BIN -b -c /usr/keys
    sleep 15
    /var/bin/$CAMD_BIN2 &
    ;;
    stop)
    killall -9 $CAMD_BIN2 $CAMD_BIN 2>/dev/null
    sleep 2
    remove_tmp
    ;;
    *)
    $0 stop
    exit 0
    ;;
    esac

    exit 0


    And you may also have to use a port.list file in which case:
    In var/keys the filename reflects on the port used. In our case:

    52010.list

    #SF= Forbidden. SA:= Enabled
    #Sky 0962
    R: { 1000 }
    SF: { 0000 }

    Once again this can be tweaked by individual channels later on if you wish.

    The cws line is the same as using an N line in cccamd or a C line in mbox. All use the newcamd protocol.
    Last edited by japseye; 15th November, 2010 at 06:28 PM. Reason: changed usr to var for 500

  5. #5
    Newbie ex1020's Avatar
    Join Date
    Oct 2009
    Posts
    11
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    thanks japs eye i have a 800hdse orig and have downloaded oscam as a server cam from pli image in my box but i am having trouble locating the files i have cccam working perfect as a server so what is the easiest way to go .
    thanks
    THE BLUE SH*TE BANG ON "IF YER KNOW YER HISTORY" IF ONLY THEY DID THEY WOULDNT BE TOO QUICK TO BRING ATTENTION TO IT!

  6. #6
    V.I.P. Member
    Join Date
    Dec 2009
    Location
    merseyside
    Posts
    2,233
    Thanks Thanks Given 
    117
    Thanks Thanks Received 
    119
    Thanked in
    93 Posts

    Default

    cut+-paste from another site

    This is a complete minimal-configuration of oscam running on a Dreambox.
    Oscam is reading the card from internal reader
    Oscam is also decrypting the channels using the built-in softcam "dvbapi".
    Oscam even updates the card using these settings. (Supported cards "EMM: OK" here)
    No other softcam necessary!

    All you've got to do is CHANGE THE CAID(cardID) AND IDENT(Providers)
    in the reader (in oscam.server) to match your card.
    You can find an overview of cards and their providers here:
    http://streamboard.gmc.to:8001/wiki/CardsList

    This is a basic configuration which runs out of the box.


    oscam.conf
    global configuration
    all listeners ("server processes") are here
    could be newcamd- cccam- camd3x- web-server or
    dvbapi, the "built-in softcam" of oscam
    code:1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20 :21:[global]Nice = -10WaitForCards = 1PreferLocalCards = 1saveinithistory = 1[monitor]port = 988monlevel = 4nocrypt = 127.0.0.1[webif]httpport = 10001httprefresh = 5httpallowed = 127.0.0.1,192.168.0.0-192.168.255.255[dvbapi]enabled =1boxtype = dreamboxuser = localuserau = 1



    oscam.server
    reader configuration
    where oscam finds it's cards
    could be real card-readers, or remote servers on any protocol
    code:1:2:3:4:5:6:7:8:9:10:[reader]label = myreadernameenable = 1protocol = internaldevice = /dev/sci0detect = cdcaid = 0123 <---put your caid hereident = 0123:123456,234567 <---put your caid:ident,ident,... heregroup = 1emmcache = 1,3,2


    oscam.user
    user configuration
    users who are allowed to connect to this oscam
    like our local dvbapi-user, or remote users for any protocol
    code:1:2:3:4:[account]user = localusergroup = 1au = myreadername


    MANY MANY MANY other functions can be added to this configuration to enhance or add features.

    If you'd like to share your card, you have to add server-processes in oscam.conf,
    like a newcamd-protocol-server or cccam-protocol-server or other protocol server.
    Doing so, different remote cardservers or softcams like oscam, cccam, newcs,...
    are allowed to connect using the corresponding protocols.
    Then add accounts in oscam.user so that our oscam accepts connections
    from these remotes.

    If you want to connect to remote cardservers, you have to add readers in oscam.server,
    like newcamd-protocol connections or cccam-protocol connections or other protocol connections.
    Doing so, your oscam reads cards from remote cardservers or softcams like oscam, cccam, newcs,...
    using the corresponding protocols.

    For more information it's strongly recommended to read the documentation
    which came with oscam or read the always up-to-date documentation here:
    http://streamboard.gmc.to/svn/oscam/trun...bution/doc/txt/
    And configuration examples here:
    http://streamboard.gmc.to/svn/oscam/trun...on/doc/example/

  7. #7
    Newbie ex1020's Avatar
    Join Date
    Oct 2009
    Posts
    11
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default @s outhpaw

    many thanks for the usefull and informative post i have give it a go for some hours no no joy
    here is my set up i have server with sly in a 800hdse top slot with pli image and cccam 2.1.4 i think works perfect except for this friggin pick tv , now i want it to work for me and the clients the questions i need clearing up are

    ?1 are my files residing in the correct place var/etc/tuxbox/config

    ?2 have i configured the file correct as in the picture adding only as you said in the post just change caid and indent ,indent i dont know if its correct with brackets or evenn if it is the indent .
    ?3 do i have to put the box key in any where .
    do i have to do anything for the clients to clear the channels or is it once i clear them they can view many thansk for your time
    Attached Images Attached Images
    THE BLUE SH*TE BANG ON &quot;IF YER KNOW YER HISTORY&quot; IF ONLY THEY DID THEY WOULDNT BE TOO QUICK TO BRING ATTENTION TO IT!

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.