September 2014 - App_rpt-users

XIPAR Dialing an extension from Repeater to IP phone failing....
by Bradley Haney 10 Sep '14

10 Sep '14

Hello all.. I am getting this error when i am trying to dial from the radio to a local PBX extension on Xipar.. Anyone know where to start? localhost*CLI> [Sep 9 20:29:54] WARNING[31176]: app_dial.c:1310 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Unknown) [Sep 9 20:29:54] WARNING[31176]: app_dial.c:1310 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Unknown) localhost*CLI> [Sep 9 20:29:59] WARNING[31177]: func_db.c:180 function_db_delete: DB_DELETE requires an argument, DB_DELETE(<family>/<key>) [Sep 9 20:29:59] WARNING[31177]: func_db.c:180 function_db_delete: DB_DELETE requires an argument, DB_DELETE(<family>/<key>) Thanks.. Bradley

1 0

Centos 5 with kernel 2.6.32-042stab093.4
by pete M 09 Sep '14

09 Sep '14

Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org... Getting files.tar.gz from http://dl.allstarlink.org... ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found 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... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no 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... i686-pc-linux-gnu checking host system type... i686-pc-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... no checking for initscr in -lncurses... no checking for pkg-config... No 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++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no 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 -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.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_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root@node rc.d]# I dont know where to go from there.. Anyone care to help a bit?

3 4

Asterisk Segmentation Fault when decode mdc1200 on ilink nodes
by Ismael Isuani 08 Sep '14

08 Sep '14

Hello to the group, I have 2 radios with different frequencies connected to the asterisk with 2 URI interfaces. I compiled asterisk with mdc 1200. MDC 1200 decoder works well, but if i link both nodes, such as: rpt cmd 1001 ilink 3 1002 now when mdc is decoded asterisk died with: Memory Allocation Failure - '-297310267' bytes in function ast_frdup at line 469 of frame.c I attached the backtrace file. app_rpt version 0.323 06/07/2014 asterisk 1.4.23-pre Is anyone to help me? Thanks in advance.

1 0

debian?
by pete M 08 Sep '14

08 Sep '14

I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon.. I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap.. But they are on debian. is it possible to install a node on a debian system? can someone point me in the right direction? Thanks Pierre VE2PFpresident VE2MRC for the curious.. here is the hosting company:https://www.beastnode.com/vps

3 5

Beagleboard-XM & LOX
by Bob 07 Sep '14

07 Sep '14

I've been running my Beagleboard-XM with LOX for about 9 months. It has recently stopped working; Asterisk stops running, and the LOX PTT LED lights. When I do a reboot (from the command line or by power reset) it works fine for a week or so, then does it again. I suspect the Beagleboard-XM is having memory errors, but since Asterisk stops running, I can't get into asterisk -r to see what it is doing (just returns me to the Linux command line). Other than this, it works fine. Has anyone had this experience? If so, did you find a solution other than using crontab to reboot weekly? Thanks, Bob kk6ecm

1 0

Fwd: EchoLink Policy Reminder
by Buddy Brannan 07 Sep '14

07 Sep '14

I wonder if anyone else got this Email? I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. — Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy(a)brannan.name > Begin forwarded message: > > From: "EchoLink Support" <support(a)echolink.org> > Subject: EchoLink Policy Reminder > To: "EchoLink Node Operators" <> > > We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm) > > In general, EchoLink does not permit cross-linking. > > More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. > > Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. > > In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. > > If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. > > Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. > > 73 > EchoLink Support > > (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)

11 12

WX Alert scripts
by Mike Lussier 06 Sep '14

06 Sep '14

Good afternoon to all, I have a question on the weather alert scripts that I have been reading about. Before I attempt to add this to my pair of nodes has any one else done this on the Beagle Bone Black ? I don't want to over load them but this is something that I feel is of great importance. Thank you Mike AE4ML -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan*

3 2

Re: [App_rpt-users] Problem with two repeaters..
by mike＠midnighteng.com 06 Sep '14

06 Sep '14

1 0

List of IRLP reflectors with allstar
by Skyler F 06 Sep '14

06 Sep '14

I want to communicate with someone using an IRLP node. The only way is through an IRLP reflector with allstar. Is there a list anywhere of all of the IRLP reflectors which have AllStar on them? I don't want to go through an echoIrlp because the audio sucks and echo-links new policy. 73 Skyler KDØWHB -- Skyler Fennell amsatnet.info KDØWHB electricity440(a)gmail.com

3 3

Problem with two repeaters..
by Loren Tedford 06 Sep '14

06 Sep '14

Hello having issues running both repeaters for some reason it is telling me that Device usb27103 currently not active what does this mean? its all plugged in was working then all the suddenly stopped working randomly is it not detecting the device number correctly with the URI? I am running 2 Cm200 on vhf for this repeater and node 29925 is running flawlessly with out any issues with 2 Cm200 on UHF Loren Tedford (KC9ZHV) Email: lorentedford(a)gmail.com http://kc9zhv.lorentedford.com

2 1