March 2013 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] CTCSS decode
by Don Hackler 13 Mar '13

13 Mar '13

You don't need the tones brought out separate from the RX audio. As long as you can feed the discriminator audio to the RTCM, it will decode CTCSS tones using the built-in DSP. If you don't have access to the discriminator audio, you will need a COR logic output from the radio. On Mar 13, 2013, at 9:37 AM, Bill Hurlock <bill.hurlock(a)cpcomms.com> wrote: > How can I decode the CTCSS tones and use them for Tone Squelch when I'm using a RTCM interconnect to my transceiver. I do not have a rig that exports the tone as a separate output from the radio. The rig is a Yaesu 736R and I use Demod audio and direct TX mod connections. Outbound is working find. > > Bill Hurlock > CPCommunications > 856-234-1661 Home Office > 856-264-1010 Cell > 914-345-9292 Ext.429 > www.cpcomms.com > WA2TQI > > Providing Solutions for Audio and Video Communications > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

CTCSS decode
by Bill Hurlock 13 Mar '13

13 Mar '13

How can I decode the CTCSS tones and use them for Tone Squelch when I'm using a RTCM interconnect to my transceiver. I do not have a rig that exports the tone as a separate output from the radio. The rig is a Yaesu 736R and I use Demod audio and direct TX mod connections. Outbound is working find. Bill Hurlock CPCommunications 856-234-1661 Home Office 856-264-1010 Cell 914-345-9292 Ext.429 www.cpcomms.com WA2TQI Providing Solutions for Audio and Video Communications

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 49, Issue 30
by George Csahanin 13 Mar '13

13 Mar '13

OK, a clarification I received from Echolink is this: There are three callsigns that must not be blocked in the asterisk config: permit=k1rfd, k1rfd-l, k1rdf-r, vk2jtp, vk2jtp-l, vk2jtp-r, w1cdm, w1cdm-l, w1cdm-r If you're restricting access, as I am as well, the above needs to be there, according to the echolink folks as of this AM. I guess my permitting only a few thru made them think I was still running TBD..?? All's resolved now But this set of callsigns may be something the gang needs to keep in mind. And everybody gets to live happily ever after. GeorgeC W2DB On 03/13/2013 11:21 AM, James Smith wrote: > man, i have had echolink running on 3 of our nodes for about 6 months > and no problems. they run the -R instance. i also run a kd5oxm-L > instance on the traditional windows box because its easy to control > for public access (i wanted to block foriegners.) > > i the asterisk echolink i have to block everything and then allow a > few that i hand type in. > works very very well in asterisk. it sound wonderful since it runs > inside the box. > > but like i said we have had it going for about 6months. maybe you > stired the pot when you asked ofr permission to go TBD maybe? you > should know that. dont ask for permission, ask for forgiveness when > they catch you! > > james > kd5oxm > PS - you figured anything on the ppp16, i read the entire "using lpt > port" page. i would love to figure some that out too. > > thanks > > > > On Wed, Mar 13, 2013 at 11:00 AM, <app_rpt-users-request(a)ohnosec.org > <mailto:app_rpt-users-request@ohnosec.org>> wrote: > > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org <mailto:app_rpt-users@ohnosec.org> > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > <mailto:app_rpt-users-request@ohnosec.org> > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > <mailto:app_rpt-users-owner@ohnosec.org> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. echolink connection issue (George Csahanin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Mar 2013 23:33:02 -0500 > From: "George Csahanin" <george(a)dyb.com <mailto:george@dyb.com>> > To: "app_rpt mailing list" <app_rpt-users(a)ohnosec.org > <mailto:app_rpt-users@ohnosec.org>> > Subject: [App_rpt-users] echolink connection issue > Message-ID: <0301EEE1A2CD4004BDBB2D60B08CC1A2(a)lintv.com > <mailto:0301EEE1A2CD4004BDBB2D60B08CC1A2@lintv.com>> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > Something very odd took place. History:I had a TBD node running > with an > echolink id of W2DB-L. On October 2 I actually asked echolink > folks about it > and they said tbd was not permitted. I took it down. Now that > callsign is > blocked, and apparently (to them) an allstar/asterisk node looks > like tbd. > My node 2360 is also echolink W2DB-R and they just sent me an email of > accusing me of running a tbd box at W2DB-R. It isn't, it's an ACID > install > of asterisk/app_rpt. Now W2DB-R doesn't seem to want to connect to > anything > except the echotest also. So not sure what this is all about, but > if anybody > else has any echolink issue you might want to see if you've been > blocked/de-authorized because they think it is a tbd box. Too bad. > Echolink > is a nice service that allows hams around the world to keep up pc > to pc. And > nobody asks for any money, nice. But this is very, very out of the > norm for > them. > > (It would also have been nice if somewhere on their web site they > spelled > out that tbd and/or asterisk isn't permitted...) > > George > W2DB > > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 49, Issue 30 > ********************************************* > >

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 49, Issue 30
by George Csahanin 13 Mar '13

13 Mar '13

OK, a clarification I received from Echolink is this: There are three callsigns that must not be blocked in the asterisk config: permit=k1rfd, k1rfd-l, k1rdf-r, vk2jtp, vk2jtp-l, vk2jtp-r, w1cdm, w1cdm-l, w1cdm-r If you're restricting access, as I am as well, the above needs to be there, according to the echolink folks as of this AM. I guess my permitting only a few thru made them think I was still running TBD..?? All's resolved now But this set of callsigns may be something the gang needs to keep in mind. And everybody gets to live happily ever after. GeorgeC W2DB On 03/13/2013 11:21 AM, James Smith wrote: > man, i have had echolink running on 3 of our nodes for about 6 months > and no problems. they run the -R instance. i also run a kd5oxm-L > instance on the traditional windows box because its easy to control > for public access (i wanted to block foriegners.) > > i the asterisk echolink i have to block everything and then allow a > few that i hand type in. > works very very well in asterisk. it sound wonderful since it runs > inside the box. > > but like i said we have had it going for about 6months. maybe you > stired the pot when you asked ofr permission to go TBD maybe? you > should know that. dont ask for permission, ask for forgiveness when > they catch you! > > james > kd5oxm > PS - you figured anything on the ppp16, i read the entire "using lpt > port" page. i would love to figure some that out too. > > thanks > > > > On Wed, Mar 13, 2013 at 11:00 AM, <app_rpt-users-request(a)ohnosec.org > <mailto:app_rpt-users-request@ohnosec.org>> wrote: > > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org <mailto:app_rpt-users@ohnosec.org> > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > <mailto:app_rpt-users-request@ohnosec.org> > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > <mailto:app_rpt-users-owner@ohnosec.org> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. echolink connection issue (George Csahanin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Mar 2013 23:33:02 -0500 > From: "George Csahanin" <george(a)dyb.com <mailto:george@dyb.com>> > To: "app_rpt mailing list" <app_rpt-users(a)ohnosec.org > <mailto:app_rpt-users@ohnosec.org>> > Subject: [App_rpt-users] echolink connection issue > Message-ID: <0301EEE1A2CD4004BDBB2D60B08CC1A2(a)lintv.com > <mailto:0301EEE1A2CD4004BDBB2D60B08CC1A2@lintv.com>> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > Something very odd took place. History:I had a TBD node running > with an > echolink id of W2DB-L. On October 2 I actually asked echolink > folks about it > and they said tbd was not permitted. I took it down. Now that > callsign is > blocked, and apparently (to them) an allstar/asterisk node looks > like tbd. > My node 2360 is also echolink W2DB-R and they just sent me an email of > accusing me of running a tbd box at W2DB-R. It isn't, it's an ACID > install > of asterisk/app_rpt. Now W2DB-R doesn't seem to want to connect to > anything > except the echotest also. So not sure what this is all about, but > if anybody > else has any echolink issue you might want to see if you've been > blocked/de-authorized because they think it is a tbd box. Too bad. > Echolink > is a nice service that allows hams around the world to keep up pc > to pc. And > nobody asks for any money, nice. But this is very, very out of the > norm for > them. > > (It would also have been nice if somewhere on their web site they > spelled > out that tbd and/or asterisk isn't permitted...) > > George > W2DB > > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 49, Issue 30 > ********************************************* > >

1 0

echolink connection issue
by George Csahanin 13 Mar '13

13 Mar '13

Something very odd took place. History:I had a TBD node running with an echolink id of W2DB-L. On October 2 I actually asked echolink folks about it and they said tbd was not permitted. I took it down. Now that callsign is blocked, and apparently (to them) an allstar/asterisk node looks like tbd. My node 2360 is also echolink W2DB-R and they just sent me an email of accusing me of running a tbd box at W2DB-R. It isn't, it's an ACID install of asterisk/app_rpt. Now W2DB-R doesn't seem to want to connect to anything except the echotest also. So not sure what this is all about, but if anybody else has any echolink issue you might want to see if you've been blocked/de-authorized because they think it is a tbd box. Too bad. Echolink is a nice service that allows hams around the world to keep up pc to pc. And nobody asks for any money, nice. But this is very, very out of the norm for them. (It would also have been nice if somewhere on their web site they spelled out that tbd and/or asterisk isn't permitted...) George W2DB

1 0

Echolink logging/debug
by Tony KT9AC 10 Mar '13

10 Mar '13

I need to turn on Echolink logging within Asterisk, and see in chan_echolink a reference to "echolink debug <level>" but the CLI doesn't like that command. Is there a hidden parameter to enable basic logging (connects, callsign, IP address) mentioned in the chan_echolink file like "log=/tmp/..." Thanks! Tony

2 2

usbradio_tune_usb.conf XIPAR
by motorula＠gmail.com 08 Mar '13

08 Mar '13

Would somebody please tell me how to locate usbradio_tune_usb.conf file in XIPAR installation? I'm trying to add second usb interface but cannot find the file in which i have to map FOB interface name to physical address.

2 1

Re: [App_rpt-users] phase2.sh won't do the job
by Alan Adamson 08 Mar '13

08 Mar '13

Pete based upon this question, I probably know the answer to the next. There are a bunch of changes to make Asterisk compile on a 2.6.35 or 3.x kernel (not sure which Centos uses). Note the least of which there are some pretty significant USB changes that need to be made. I run Allstar on Debian Squeeze, and at the first time I brought it up, I had to go through all of this, but my sources don't match the Distro so I'm reluctant to share them. Also, I think Jim pushed some of the changes into the SVN, but from your error, he didn't push all of them in. I'm not sure what to tell you, but unless you are comfortable with linux and building applications and how the header files relate and have been changed over the various kernel versions, you are in a pretty steep uphill journey. Trudge on as you wish, but you've just reached the tip of the iceberg around this stuff on the newer kernels. If you are pretty comfortable with Linux, I'd be happy to share my sources, but you'd have to diff them against the SVN and make your changes from them. Sorry, Alan From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of pete M Sent: Thursday, March 07, 2013 8:30 PM To: APP RPT Subject: [App_rpt-users] phase2.sh wont do the job Ok Like a few here knows, I am trying to install the acid version of app_rpt on a centos 6 linux. Someone kind enough gave me good info to start with and I've been able to do a lot.. but after modifying phase2.sh so that it can find its repo, I start it and here is the output.. ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org... Getting files.tar.gz from http://dl.allstarlink.org... ****** Asterisk Installation ****** 7 Mar 20:19:01 ntpdate[5687]: the NTP socket is in use, exiting Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for newtBell in -lnewt... yes checking newt.h usability... yes checking newt.h presence... yes checking for newt.h... yes checking for usb_init in -lusb... yes checking usb.h usability... yes checking usb.h presence... yes checking for usb.h... yes configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for pkg-config... pkg-config configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -c -o menuselect_curses.o menuselect_curses.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_curses.o mxml/libmxml.a mxml/libmxml.a -lncurses make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... make[1]: Entering directory `/usr/src/astsrc/zaptel' make -C /lib/modules/2.6.32-279.22.1.el6.x86_64/build ARCH=x86_64 SUBDIRS=/usr/src/astsrc/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o wcfxo.o wct1xxp.o wctdm.o wcte11xp.o zaptel.o ztd-eth.o ztd-loc.o ztdummy.o ztdynamic.o zttranscode.o wctdm24xxp/" modules make[2]: Entering directory `/usr/src/kernels/2.6.32-279.22.1.el6.x86_64' gcc -o /usr/src/astsrc/zaptel/kernel/makefw /usr/src/astsrc/zaptel/kernel/makefw.c /usr/src/astsrc/zaptel/kernel/makefw /usr/src/astsrc/zaptel/kernel/pciradio.rbt radfw > /usr/src/astsrc/zaptel/kernel/radfw.h Loaded 42096 bytes from file CC [M] /usr/src/astsrc/zaptel/kernel/pciradio.o /usr/src/astsrc/zaptel/kernel/pciradio.c: In function 'pciradio_start_dma': /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: implicit declaration of function 'set_current_state' /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: 'TASK_INTERRUPTIBLE' undeclared (first use in this function) /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: (Each undeclared identifier is reported only once /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: for each function it appears in.) /usr/src/astsrc/zaptel/kernel/pciradio.c:1701: error: implicit declaration of function 'schedule_timeout' make[3]: *** [/usr/src/astsrc/zaptel/kernel/pciradio.o] Error 1 make[2]: *** [_module_/usr/src/astsrc/zaptel/kernel] Error 2 make[2]: Leaving directory `/usr/src/kernels/2.6.32-279.22.1.el6.x86_64' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/astsrc/zaptel' make: *** [all] Error 2 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! a bit long but I dont see where its bugging and why, at first it was asking for gtk, so I did a yum install gtk-devel this got care of the complaning about gtk.. Of course I did a yum -y update before stating this. now anyone can help?? p.s. runlevel of the machine is 3 now going to take a look at astinstall.sh if there is something there that I did not see.. Pierre VE2PF

4 3

phase2.sh wont do the job
by pete M 08 Mar '13

08 Mar '13

Ok Like a few here knows, I am trying to install the acid version of app_rpt on a centos 6 linux. Someone kind enough gave me good info to start with and I've been able to do a lot.. but after modifying phase2.sh so that it can find its repo, I start it and here is the output.. ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org... Getting files.tar.gz from http://dl.allstarlink.org... ****** Asterisk Installation ****** 7 Mar 20:19:01 ntpdate[5687]: the NTP socket is in use, exiting Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for newtBell in -lnewt... yes checking newt.h usability... yes checking newt.h presence... yes checking for newt.h... yes checking for usb_init in -lusb... yes checking usb.h usability... yes checking usb.h presence... yes checking for usb.h... yes configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for pkg-config... pkg-config configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -c -o menuselect_curses.o menuselect_curses.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_curses.o mxml/libmxml.a mxml/libmxml.a -lncurses make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... make[1]: Entering directory `/usr/src/astsrc/zaptel' make -C /lib/modules/2.6.32-279.22.1.el6.x86_64/build ARCH=x86_64 SUBDIRS=/usr/src/astsrc/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o wcfxo.o wct1xxp.o wctdm.o wcte11xp.o zaptel.o ztd-eth.o ztd-loc.o ztdummy.o ztdynamic.o zttranscode.o wctdm24xxp/" modules make[2]: Entering directory `/usr/src/kernels/2.6.32-279.22.1.el6.x86_64' gcc -o /usr/src/astsrc/zaptel/kernel/makefw /usr/src/astsrc/zaptel/kernel/makefw.c /usr/src/astsrc/zaptel/kernel/makefw /usr/src/astsrc/zaptel/kernel/pciradio.rbt radfw > /usr/src/astsrc/zaptel/kernel/radfw.h Loaded 42096 bytes from file CC [M] /usr/src/astsrc/zaptel/kernel/pciradio.o /usr/src/astsrc/zaptel/kernel/pciradio.c: In function ‘pciradio_start_dma’: /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: implicit declaration of function ‘set_current_state’ /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function) /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: (Each undeclared identifier is reported only once /usr/src/astsrc/zaptel/kernel/pciradio.c:1700: error: for each function it appears in.) /usr/src/astsrc/zaptel/kernel/pciradio.c:1701: error: implicit declaration of function ‘schedule_timeout’ make[3]: *** [/usr/src/astsrc/zaptel/kernel/pciradio.o] Error 1 make[2]: *** [_module_/usr/src/astsrc/zaptel/kernel] Error 2 make[2]: Leaving directory `/usr/src/kernels/2.6.32-279.22.1.el6.x86_64' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/astsrc/zaptel' make: *** [all] Error 2 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! a bit long but I dont see where its bugging and why, at first it was asking for gtk, so I did a yum install gtk-devel this got care of the complaning about gtk.. Of course I did a yum -y update before stating this. now anyone can help?? p.s. runlevel of the machine is 3 now going to take a look at astinstall.sh if there is something there that I did not see.. Pierre VE2PF

2 3

wont connect to nodes?
by Matt Roberts 07 Mar '13

07 Mar '13

Matt Roberts n9gmr(a)me.com 386-679-1986 Sent from my iPad Begin forwarded message: > From: Matt Roberts <n9gmr(a)icloud.com> > Date: March 7, 2013, 4:14:52 PM EST > To: David KE6UPI <dshaw(a)ke6upi.com> > Cc: "41.2 Jim" <41.2jim(a)gmail.com>, APP RPT <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] wont connect to nodes? > > Check the RPT-Extnodes file. See if the IP addresses of the nodes in question are listed. > > Matt Roberts > n9gmr(a)me.com > 386-679-1986 > > Sent from my iPad > > On Mar 7, 2013, at 3:34 PM, David KE6UPI <dshaw(a)ke6upi.com> wrote: > >> Are both nodes on the same network? >> >> David >> >> >> On Thu, Mar 7, 2013 at 10:45 AM, 41.2 Jim <41.2jim(a)gmail.com> wrote: >>> I have Allstar node 28839 and the problem is I cannot connect to nodes. 28839 will connect to any HUB but I get a connection failed when I try to connect to any node other than a HUB. Nodes can connect to me but.... I can't connect to them. when I try to connect to a single node I get this on the CLI :[Mar 6 19:17:17] NOTICE[327]: chan_iax2.c:4071 __auto_congest: Auto-congesting call due to slow response, and the announcement of "connection failed" also when connected to a HUB, in transceive and try to connect to another node, no matter the node # I get -- <Zap/pseudo-619610436> Playing 'rpt/remote_already' "remote already in this mode" announcement Help? >>> >>> Thank you all for your time >>> Jim Frederick KF6QBW >>> AllStar Node # 28839 >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0