Menu
▾
▴
[Astlinux-commits] SF.net SVN: astlinux: [272] trunk/package/zaptel
|
From: <kr...@us...> - 2006-08-17 04:41:40
|
Revision: 272 Author: krisk84 Date: 2006-08-16 21:41:24 -0700 (Wed, 16 Aug 2006) ViewCVS: http://svn.sourceforge.net/astlinux/?rev=272&view=rev Log Message: ----------- root fs fixes Modified Paths: -------------- trunk/package/minihttpd/minihttpd.mk trunk/package/zaptel/zaptel.mk trunk/target/generic/target_skeleton/stat/etc/rc.conf Added Paths: ----------- trunk/package/minihttpd/www.tar.gz Removed Paths: ------------- trunk/target/generic/target_skeleton/stat/etc/zaptel.conf.sample trunk/target/generic/target_skeleton/stat/var/ trunk/target/generic/target_skeleton/usr/sbin/addmailbox trunk/target/generic/target_skeleton/usr/sbin/astgenkey Modified: trunk/package/minihttpd/minihttpd.mk =================================================================== --- trunk/package/minihttpd/minihttpd.mk 2006-08-17 01:05:51 UTC (rev 271) +++ trunk/package/minihttpd/minihttpd.mk 2006-08-17 04:41:24 UTC (rev 272) @@ -32,6 +32,8 @@ $(TARGET_DIR)/$(MINIHTTPD_TARGET_BINARY): $(MINIHTTPD_DIR)/$(MINIHTTPD_BINARY) $(INSTALL) -D $(MINIHTTPD_DIR)/$(MINIHTTPD_BINARY) $(TARGET_DIR)/usr/$(MINIHTTPD_TARGET_BINARY) $(INSTALL) -D $(MINIHTTPD_DIR)/htpasswd $(TARGET_DIR)/usr/bin/htpasswd + mkdir -p $(TARGET_DIR)/stat/var + $(MINIHTTPD_CAT) package/minihttpd/www.tar.gz | tar -C $(TARGET_DIR)/stat/var $(TAR_OPTIONS) - $(INSTALL) -D -m 0755 package/minihttpd/mini_httpd.init $(TARGET_DIR)/etc/init.d/mini_httpd ln -sf /tmp/etc/mini_httpd.conf $(TARGET_DIR)/etc/mini_httpd.conf Added: trunk/package/minihttpd/www.tar.gz =================================================================== (Binary files differ) Property changes on: trunk/package/minihttpd/www.tar.gz ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/package/zaptel/zaptel.mk =================================================================== --- trunk/package/zaptel/zaptel.mk 2006-08-17 01:05:51 UTC (rev 271) +++ trunk/package/zaptel/zaptel.mk 2006-08-17 04:41:24 UTC (rev 272) @@ -80,6 +80,7 @@ cp -a $(STAGING_DIR)/$(ZAPTEL_TARGET_BINARY) $(TARGET_DIR)/$(ZAPTEL_TARGET_BINARY) cp -a $(STAGING_DIR)/sbin/zttool $(TARGET_DIR)/sbin/zttool install -D -m 0755 $(ZAPTEL_DIR)/ztmonitor $(TARGET_DIR)/sbin/ztmonitor + install -D -m 0644 $(ZAPTEL_DIR)/zaptel.conf.sample $(TARGET_DIR)/stat/etc/zaptel.conf.sample -$(STRIP) -g $(TARGET_DIR)/lib/modules/$(LINUX_VER)/misc/*.ko -$(STRIP) -g $(TARGET_DIR)/lib/libtone* -$(STRIP) -g $(TARGET_DIR)/$(ZAPTEL_TARGET_BINARY) Modified: trunk/target/generic/target_skeleton/stat/etc/rc.conf =================================================================== --- trunk/target/generic/target_skeleton/stat/etc/rc.conf 2006-08-17 01:05:51 UTC (rev 271) +++ trunk/target/generic/target_skeleton/stat/etc/rc.conf 2006-08-17 04:41:24 UTC (rev 272) @@ -230,6 +230,11 @@ AUTOMODS="rtc 3c59x typhoon tulip eepro100 natsemi forcedeth 8139cp 8139too via-rhine pcnet32 acenic e1000 ns83820 r8169 tg3" +##LMSensors Modules +##List your hardware modules, seperated by spaces +##You will also need to create a sensors.conf +#SENSEMODS="vt1211" + ##Zaptel hardware support (NOT Sangoma - use "wancfg") ##These are the modules that will get loaded\unloaded by the Zaptel ## ##Init script. Please move the zaptel modules from /etc/rc.modules ## Deleted: trunk/target/generic/target_skeleton/stat/etc/zaptel.conf.sample =================================================================== --- trunk/target/generic/target_skeleton/stat/etc/zaptel.conf.sample 2006-08-17 01:05:51 UTC (rev 271) +++ trunk/target/generic/target_skeleton/stat/etc/zaptel.conf.sample 2006-08-17 04:41:24 UTC (rev 272) @@ -1,206 +0,0 @@ -# -# Zaptel Configuration File -# -# This file is parsed by the Zaptel Configurator, ztcfg -# -# -# First come the span definitions, in the format -# span=<span num>,<timing>,<line build out (LBO)>,<framing>,<coding>[,yellow] -# -# The timing parameter determines the selection of primary, secondary, and -# so on sync sources. If this span should be considered a primary sync -# source, then give it a value of "1". For a secondary, use "2", and so on. -# To not use this as a sync source, just use "0" -# -# The line build-out (or LBO) is an integer, from the following table: -# 0: 0 db (CSU) / 0-133 feet (DSX-1) -# 1: 133-266 feet (DSX-1) -# 2: 266-399 feet (DSX-1) -# 3: 399-533 feet (DSX-1) -# 4: 533-655 feet (DSX-1) -# 5: -7.5db (CSU) -# 6: -15db (CSU) -# 7: -22.5db (CSU) -# -# The framing is one of "d4" or "esf" for T1 or "cas" or "ccs" for E1 -# -# Note: "d4" could be referred to as "sf" or "superframe" -# -# The coding is one of "ami" or "b8zs" for T1 or "ami" or "hdb3" for E1 -# -# E1's may have the additional keyword "crc4" to enable CRC4 checking -# -# If the keyword "yellow" follows, yellow alarm is transmitted when no -# channels are open. -# -#span=1,0,0,esf,b8zs -#span=2,1,0,esf,b8zs -#span=3,0,0,ccs,hdb3,crc4 -# -# Next come the dynamic span definitions, in the form: -# dynamic=<driver>,<address>,<numchans>,<timing> -# -# Where <driver> is the name of the driver (e.g. eth), <address> is the -# driver specific address (like a MAC for eth), <numchans> is the number -# of channels, and <timing> is a timing priority, like for a normal span. -# use "0" to not use this as a timing source, or prioritize them as -# primary, secondard, etc. Note that you MUST have a REAL zaptel device -# if you are not using external timing. -# -# dynamic=eth,eth0/00:02:b3:35:43:9c,24,0 -# -# Next come the definitions for using the channels. The format is: -# <device>=<channel list> -# -# Valid devices are: -# -# "e&m" : Channel(s) are signalled using E&M signalling (specific -# implementation, such as Immediate, Wink, or Feature Group D -# are handled by the userspace library). -# "fxsls" : Channel(s) are signalled using FXS Loopstart protocol. -# "fxsgs" : Channel(s) are signalled using FXS Groundstart protocol. -# "fxsks" : Channel(s) are signalled using FXS Koolstart protocol. -# "fxols" : Channel(s) are signalled using FXO Loopstart protocol. -# "fxogs" : Channel(s) are signalled using FXO Groundstart protocol. -# "fxoks" : Channel(s) are signalled using FXO Koolstart protocol. -# "sf" : Channel(s) are signalled using in-band single freq tone. -# Syntax as follows: -# channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> -# rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) -# bandwith in hz (typically 10.0), rxflag is either 'normal' or -# 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone -# level in dbm, txflag is either 'normal' or 'inverted'. Set -# rxfreq or txfreq to 0.0 if that tone is not desired. -# "unused" : No signalling is performed, each channel in the list remains idle -# "clear" : Channel(s) are bundled into a single span. No conversion or -# signalling is performed, and raw data is available on the master. -# "indclear": Like "clear" except all channels are treated individually and -# are not bundled. "bchan" is an alias for this. -# "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the -# bundle, and the resulting data is communicated via the master -# device. -# "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the -# bundle and also performs incoming and outgoing FCS insertion -# and verification. "dchan" is an alias for this. -# "nethdlc" : The zaptel driver bundles the channels together into an -# hdlc network device, which in turn can be configured with -# sethdlc (available separately). -# "dacs" : The zaptel driver cross connects the channels starting at -# the channel number listed at the end, after a colon -# "dacsrbs" : The zaptel driver cross connects the channels starting at -# the channel number listed at the end, after a colon and -# also performs the DACSing of RBS bits -# -# The channel list is a comma-separated list of channels or ranges, for -# example: -# -# 1,3,5 (channels one, three, and five) -# 16-23, 29 (channels 16 through 23, as well as channel 29 -# -# So, some complete examples are: -# e&m=1-12 -# nethdlc=13-24 -# fxsls=25,26,27,28 -# fxols=29-32 -# -#fxoks=1-24 -#bchan=25-47 -#dchan=48 -#fxols=1-12 -#fxols=13-24 -#e&m=25-29 -#nethdlc=30-33 -#clear=44 -#clear=45 -#clear=46 -#clear=47 -#fcshdlc=48 -#dacs=1-24:48 -#dacsrbs=1-24:48 -# -# Finally, you can preload some tone zones, to prevent them from getting -# overwritten by other users (if you allow non-root users to open /dev/zap/* -# interfaces anyway. Also this means they won't have to be loaded at runtime. -# The format is "loadzone=<zone>" where the zone is a two letter country code. -# -# You may also specify a default zone with "defaultzone=<zone>" where zone -# is a two letter country code. -# -# An up-to-date list of the zones can be found in the file zaptel/zonedata.c -# -loadzone = us -#loadzone = us-old -#loadzone=gr -#loadzone=it -#loadzone=fr -#loadzone=de -#loadzone=uk -#loadzone=fi -#loadzone=jp -#loadzone=sp -#loadzone=no -#loadzone=hu -#loadzone=lt -#loadzone=pl -defaultzone=us -# -# Section for PCI Radio Interface -# (see http://www.zapatatelephony.org/app_rpt.html) -# -# The PCI Radio Interface card interfaces up to 4 two-way radios (either -# a base/mobile radio or repeater system) to Zaptel channels. The driver -# may work either independent of an application, or with it, through -# the driver;s ioctl() interface. This file gives you access to specify -# load-time parameters for Radio channels, so that the driver may run -# by itself, and just act like a generic Zaptel radio interface. -# -# Unlike the rest of this file, you specify a block of parameters, and -# then the channel(s) to which they apply. CTCSS is specified as a frequency -# in tenths of hertz, for example 131.8 HZ is specified as 1318. DCS -# for receive is specified as the code directly, for example 223. DCS for -# transmit is specified as D and then the code, for example D223. -# -# The hardware supports a "community" CTCSS decoder system that has -# arbitrary transmit CTCSS or DCS codes associated with them, unlike -# traditional "community" systems that encode the same tone they decode. -# -# this example is a single tone DCS transmit and receive -# -# # specify the transmit tone (in DCS mode this stays constant) -# tx=D371 -# # specify the receive DCS code -# dcsrx=223 -# -# this example is a "community" CTCSS (if you only want a single tone, then -# only specify 1 in the ctcss list) -# -# # specify the default transmit tone (when not receiving) -# tx=1000 -# # Specify the receive freq, the tag (use 0 if none), and the transmit code. -# # The tag may be used by applications to determine classification of tones. -# # The tones are to be specified in order of presedence, most important first. -# # Currently, 15 tones may be specified.. -# ctcss=1318,1,1318 -# ctcss=1862,1,1862 -# -# The following parameters may be omitted if their default value is acceptible -# -# # set the receive debounce time in milliseconds -# debouncetime=123 -# # set the transmit quiet dropoff burst time in milliseconds -# bursttime=234 -# # set the COR level threshold (specified in tenths of millivolts) -# # valid values are {3125,6250,9375,12500,15625,18750,21875,25000} -# corthresh=12500 -# # Invert COR signal {y,n} -# invertcor=y -# # set the external tone mode; yes, no, internal {y,n,i} -# exttone=y -# -# Now apply the configuration to the specified channels: -# -# # We are all done with our channel parameters, so now we specify what -# # channels they apply to -# channels=1-4 - - Deleted: trunk/target/generic/target_skeleton/usr/sbin/addmailbox =================================================================== --- trunk/target/generic/target_skeleton/usr/sbin/addmailbox 2006-08-17 01:05:51 UTC (rev 271) +++ trunk/target/generic/target_skeleton/usr/sbin/addmailbox 2006-08-17 04:41:24 UTC (rev 272) @@ -1,45 +0,0 @@ -#!/bin/sh -clear -VMHOME=/var/spool/asterisk/voicemail -SNDHOME=/var/lib/asterisk/sounds -echo -echo "Enter Voicemail Context of the mailbox you are creating." -echo "The context is the value between the square brackets in" -echo "the voicemail.conf file." -echo "(DEFAULT: default)" -echo -n "Voicemail Context: " -read context -echo -echo "Enter the Mailbox number of the voicemail box you are creating." -echo -n "Mailbox Number: " -read mailbox - -context=${context:-default} - -if [ ! -e "${VMHOME}/${context}" ] - then - echo - echo "New Voicemail context.." - echo "Creating Voicemail context directory..." - mkdir -p ${VMHOME}/${context} -fi - -echo -echo "Creating Voicemail directory..." -mkdir -p ${VMHOME}/${context}/${mailbox} -echo "Creating INBOX..." -mkdir -p ${VMHOME}/${context}/${mailbox}/INBOX -echo "Creating Default greetings..." -cat ${SNDHOME}/vm-theperson.gsm > ${VMHOME}/${context}/${mailbox}/unavail.gsm -cat ${SNDHOME}/vm-theperson.gsm > ${VMHOME}/${context}/${mailbox}/busy.gsm -cat ${SNDHOME}/vm-extension.gsm > ${VMHOME}/${context}/${mailbox}/greet.gsm -nums=`echo $mailbox | sed 's/./ \0/g'` -for x in $nums; do - cat ${SNDHOME}/digits/${x}.gsm >> ${VMHOME}/${context}/${mailbox}/unavail.gsm - cat ${SNDHOME}/digits/${x}.gsm >> ${VMHOME}/${context}/${mailbox}/busy.gsm - cat ${SNDHOME}/digits/${x}.gsm >> ${VMHOME}/${context}/${mailbox}/greet.gsm -done -cat ${SNDHOME}/vm-isunavail.gsm >> ${VMHOME}/${context}/${mailbox}/unavail.gsm -cat ${SNDHOME}/vm-isonphone.gsm >> ${VMHOME}/${context}/${mailbox}/busy.gsm -echo "Complete." - Deleted: trunk/target/generic/target_skeleton/usr/sbin/astgenkey =================================================================== --- trunk/target/generic/target_skeleton/usr/sbin/astgenkey 2006-08-17 01:05:51 UTC (rev 271) +++ trunk/target/generic/target_skeleton/usr/sbin/astgenkey 2006-08-17 04:41:24 UTC (rev 272) @@ -1,61 +0,0 @@ -#!/bin/sh -# -# Usage: astgenkey [ -q ] [ -n ] [keyname] -# -DES3=-des3 -if [ "$1" = "-q" ]; then - QUIET='y' - if [ "$2" = "-n" ]; then - DES3= - KEY=$3 - else - KEY=$2 - fi -elif [ "$1" = "-n" ]; then - DES3= - if [ "$2" = "-q" ]; then - QUIET='y' - KEY=$3 - else - KEY=$2 - fi -else - KEY=$1 -fi - -if [ "$QUIET" != 'y' ]; then - echo "" - echo "This script generates an RSA private and public key pair" - echo "in PEM format for use by Asterisk. You will be asked to" - echo "enter a passcode for your key multiple times. Please" - echo "enter the same code each time. The resulting files will" - echo "need to be moved to /var/lib/asterisk/keys if you want" - echo "to use them, and any private keys (.key files) will" - echo "need to be initialized at runtime either by running" - echo "Asterisk with the '-i' option, or with the 'init keys'" - echo "command once Asterisk is running." - echo "" - echo "Press ENTER to continue or ^C to cancel." - read BLAH -fi - -while [ "$KEY" = "" ]; do - echo -n "Enter key name: " - read KEY -done - -rm -f ${KEY}.key ${KEY}.pub - -echo "Generating SSL key '$KEY': " -openssl genrsa -out ${KEY}.key ${DES3} 1024 -openssl rsa -in ${KEY}.key -pubout -out ${KEY}.pub - -if [ -f "${KEY}.key" ] && [ -f "${KEY}.pub" ]; then - if [ "$QUIET" != 'y' ]; then - echo "Key creation successful." - echo "Public key: ${KEY}.pub" - echo "Private key: ${KEY}.key" - fi -else - echo "Unknown error creating keys." -fi This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
