January 2011 - App_rpt-users - lists.keekles.org

Fan Script
by K&R Yoksh 25 Jan '11

25 Jan '11

Hello, I have another question for the group... I'm curious if it will be possible for me to write a script to control a fan for my transmitter to operate under app_rpt? I'm using my homebrew IRLP-compatible board for PTT and COS, and have managed to configure usbradio.conf to key the AUX1 port (pp3) along with the PTT using: pp3 = ptt I was considering building a hardware control circuit using a 555 timer, but thought I'd look into a software approach if possible. I used a similar script under IRLP/EchoIRLP by Robert Pectol, and it worked very well. Thanks. 73 Kyle K0KN

1 0

aprs password for app_gps
by Chuck Henderson 24 Jan '11

24 Jan '11

I would like to set up my allstarlink system to report position information to the aprs system. Can someone tell me how to set up this password? Also, are the default server and port listed in the example below what should be used? I have searched the aprs site and couldn't find who to request this information from. Chuck Henderson, WB9UUS > > ; Configuration for app_gps > ; > [general] > > call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password = 12345 ; Password for APRS-IS server for above callsign* > comment = AllStar Node 27468 ; Text to be displayed associated with this station*server = second.aprs.net ; APRS-IS server to report information to**port = 10151 ; port on server to send data* > icon = r ; A CAR (default) Icon do be displayed for station on APRS display (see below) > comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only if using GPS receiver) > baudrate = 4800 ; Baud rate for GPS receiver (specify this only if using GPS receiver) > ;debug = y ; set this for debug output > freq=442.700 ; Display Frequency of station > tone=107.2 ; CTCSS tone of station (0.0 for none) > lat=40.508 ; Fixed (default) latitude in decimal degrees > lon=-88.988 ; Fixed (default) longitude in decimal degrees > elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > power=9 ; Power level (see below) > height=5 ; Antenna Height in HAAT (see below) > gain=8 ; Antenna Gain (see below) > dir=0 ; Antenna Direction (see below) > > On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude <telesistant(a)hotmail.com>wrote: > >> There have (obviously) been some changes/improvements made to the >> Echolink and APRS/GPS subsystems within app_rpt. >> >> Included in these is the ability for a node to report its "fixed" GPS >> coordinates >> to the APRS network, even if it does not have a GPS receiver connected. >> >> Please see the following: >> >> Setting up Echolink Connectivity >> http://209.159.155.200/drupal/node/56 >> >> Setting Up APRS and GPS Configuration >> http://209.159.155.200/drupal/node/179 >> >> Of course, the latest copies of app_gps and chan_echolink need to be >> downloaded from the SVN. >> >> JIM WB6NIL >> >> >> >

7 12

DTMF passthru
by VE3GIH Gordon Hewit 24 Jan '11

24 Jan '11

KE2N Ken suggested using the propagate_dtmf command in the rpt.conf file, as a way to propagate DTMF signals to other nodes. I need this capacity to allow our members access to the local phone patch. However with all nodes set to duplex=2 (full duplex) and propagate_dtmf=yes, I'm still not getting DTMF on the other local repeaters. The asterisk console sees the DTMF, but Asterisk isn't passing the digits onwards. Does anyone have a suggestion about what else I can try? VE3GIH Gord ______________________________________________ Date: Sat, 22 Jan 2011 09:42:49 -0500 (EST) From: Ken <ke2n(a)cs.com> To: n3fe(a)repeater.net, telesistant(a)hotmail.com, app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] DTMF Allow Cory I think there is a setting for this propagate_dtmf= see http://209.159.155.200/drupal/node/134 <snipped> GL Ken KE2N Gordon Hewit 289-800-1473 (home)

3 3

One Way local connect
by KI6PSP (Ed) 24 Jan '11

24 Jan '11

Internal Allstar Connect works only one way. Run Macro for connect from 27178 to 27179 [Jan 24 07:10:19] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char * duration 255 ms [Jan 24 07:10:19] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 192 ms [Jan 24 07:10:20] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 234 ms [Jan 24 07:10:20] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 2 duration 256 ms [Jan 24 07:10:21] NOTICE[2699]: chan_iax2.c:9043 socket_process: Rejected connect attempt from 127.0.0.1, request '27179@radio-secure' does not exist [Jan 24 07:10:21] WARNING[2700]: chan_iax2.c:9221 socket_process: Call rejected by 127.0.0.1: No such context/extension -- Hungup 'IAX2/127.0.0.1:4569-1476' -- Hungup 'Zap/pseudo-1926956532' -- Hungup 'Zap/pseudo-1808547294' -- Hungup 'Zap/pseudo-1160049049' -- <Zap/pseudo-1659184301> Playing 'rpt/nodenames/27179' (language 'en') -- <Zap/pseudo-1659184301> Playing 'rpt/connection_failed' (language 'en') -- Hungup 'Zap/pseudo-1659184301' Run Macro for connect from 27179 to 27178 [Jan 24 07:11:37] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char * duration 277 ms [Jan 24 07:11:38] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 170 ms [Jan 24 07:11:38] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 216 ms [Jan 24 07:11:39] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 2 duration 256 ms -- Accepting UNAUTHENTICATED call from 127.0.0.1: > requested format = gsm, > requested prefs = (gsm|g726aal2|ulaw), > actual format = g726aal2, > host prefs = (g726aal2|gsm), > priority = mine -- Call accepted by 127.0.0.1 (format g726aal2) -- Format for call is g726aal2 -- Executing [27178@radio-secure:1] Rpt("IAX2/127.0.0.1:4569-2496", "27178") in new stack == Spawn extension (radio-secure, 27178, 1) exited KEEPALIVE on 'IAX2/127.0.0.1:4569-2496' -- <Zap/pseudo-360302433> Playing 'rpt/nodenames/27178' (language 'en') -- Hungup 'Zap/pseudo-1169767949' -- Hungup 'Zap/pseudo-1558440647' -- <Zap/pseudo-360302433> Playing 'rpt/connected' (language 'en') -- Hungup 'Zap/pseudo-1043702359' -- <Zap/pseudo-360302433> Playing 'digits/2' (language 'en') -- <Zap/pseudo-360302433> Playing 'rpt/nodenames/27179' (language 'en') -- <Zap/pseudo-128502133> Playing 'rpt/nodenames/27178' (language 'en') -- Hungup 'Zap/pseudo-360302433' -- <Zap/pseudo-128502133> Playing 'rpt/connected' (language 'en') -- <Zap/pseudo-128502133> Playing 'digits/2' (language 'en') -- <Zap/pseudo-128502133> Playing 'rpt/nodenames/27179' (language 'en') -- Hungup 'Zap/pseudo-128502133' -- Hungup 'Zap/pseudo-1357185046' -- Hungup 'Zap/pseudo-1756365411' I thought it had something to do with the "Node=" line in extensions.conf, so I commented it out, but it still does this. I already found the register lines in the IAX.conf and uncommented it. Both nodes in the rpt.conf file have the same context and account names. -- KI6PSP (Ed)

1 0

Suggested mod to default extensions.conf
by KI6PSP (Ed) 24 Jan '11

24 Jan '11

I am by no means an expert, but I have a suggestion. I nuked my extensions.conf file and rebuilt it from the web confuguration and I found a glitch in the default config. If the internet connection is down, and a call is made, the fast busy tone will sound, but it will not stop. If this is a simplex node, that is a problem. Here is my suggested default config: ; Un-comment out the following clause if you want Allstar Autopatch service [pstn-out] exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/\${EXTEN}) exten=_NXXNXXXXXX,2,Wait,3 exten=_NXXNXXXXXX,3,Hangup Thanks Ed KI6PSP

1 0

Problem with app_rpt configuration and URI's audio interface
by Alexander Alexandrov 24 Jan '11

24 Jan '11

Dear colleagues, I built a node configuration with ACID system and URI from DMKEngineering. After the import of the ACID/Asterisk/app_rpt configuration from Allstarlink.org I connected the URI to my reg and install IAX client to the PC. The system work well from IAX clent through URI to the reg - when I send audio or voice from IAX client to the reg through URI the reg transmit the audio very well and clear. The problem is that I can not send any audio signal from the REG to the IAX client. Practically the audio from the REG go to the MIC_AC pin of URI and after that dropped down. Practically I have only one way audio communication: Iax client ->Asterisk-> app_rpt -> URI -> reg Probably I use a wrong usbradio.conf configuration but have not idea where to start looking for the problem. I red in the mailing list content some similar cases and advices about URI MIC interface problems and tried to use them but unfortunately without success. I will be very grateful for any advice how to resolve the problem. 73! Alex LZ1AZA The configuration I use is the following: URI hardware interface: audio line output of the reg - to URI MIC_AC (pin 21) microphone input of the REG - to LEFT_AC(pin 22) PTT - to PTT pin of the URI (pin1) the URI's usbradio.conf file look like this: ; ; Usbradio channel driver Configuration File ; [general] [usb27371] hdwtype=0 rxboost=1 txboost=1 rxctcssrelax=1 txctcssdefault=100.0 rxctcssfreqs=100.0 txctcssfreqs=100.0 ;rxctcssoverride=0 carrierfrom=dsp ctcssfrom=dsp rxdemod=flat txprelim=yes txlimonly=no txtoctype=notone txmixa=composite txmixb=no invertptt=0 duplex=1 rxondelay=0 rxnoisefiltype=0 eeprom=0 #includeifexists custom/usbradio.conf

3 2

Re: [App_rpt-users] Echolink Link Status
by KI6PSP (Ed) 23 Jan '11

23 Jan '11

I updated my node with the whole SVN as I don't know how to update just the portion of the echolink, but I don't see the gps.conf file under /etc/asterisk/ Did I miss something, or do I have to build that conf file manually? -- KI6PSP (Ed)

2 1

new stuff
by Jim Duuuude 23 Jan '11

23 Jan '11

There have (obviously) been some changes/improvements made to the Echolink and APRS/GPS subsystems within app_rpt. Included in these is the ability for a node to report its "fixed" GPS coordinates to the APRS network, even if it does not have a GPS receiver connected. Please see the following: Setting up Echolink Connectivity http://209.159.155.200/drupal/node/56 Setting Up APRS and GPS Configuration http://209.159.155.200/drupal/node/179 Of course, the latest copies of app_gps and chan_echolink need to be downloaded from the SVN. JIM WB6NIL

1 0

Re: [App_rpt-users] Echolink Link Status
by K&R Yoksh 23 Jan '11

23 Jan '11

----- Original Message ----- > Date: Fri, 21 Jan 2011 18:27:15 -0800 > From: Jim Duuuude > Subject: Re: [App_rpt-users] Echolink Link Status > > Chan_echolink now supports proper display/reporting to the echolink server > stuff. Hello Jim (and the group), Many thanks for this great addition! 73. Kyle K0KN

4 5

Local squelch tail problem clarification. (copy of message to Ken) for comment.
by Peter Elke 22 Jan '11

22 Jan '11

From: Peter Elke [mailto:pete.elke@esquared.com] Sent: Saturday, January 22, 2011 3:26 AM To: Ken Subject: RE: [App_rpt-users] Location dependant squelch tail? Hi Ken, What I meant to get across was... There is a squelch tail when the local mobile unkeys (before the hang time) but you only hear it if you are monitoring the local node's transmit frequency. Remotely connected stations don't hear the tail, only a soft click or nothing from the same transmission. The local repeater transmitter dropping does not cause a tail if the mobile is in PL decode. I thought this was just strange, so much so that I sound ignorant reporting it... 73's Pete (WI6H)

2 2