August 2018 - App_rpt-users - lists.keekles.org

localplay / local time
by Darren Carleton 27 Aug '18

27 Aug '18

Is this a bug or by design? localplay and time functions do not seem to work when rpt.config is configured with duplex = 0 Execution of these:rpt localplay #### digits/2711 = status,11 ; Force ID (local only)712 = status,12 ; Give Time of Day (local only) Results in playback without PTT.

1 0

Integrating Echolink (and IRLP?) to an Allstar based repeater
by Doug Kingston 26 Aug '18

26 Aug '18

One suggestion that has been made in some of the howto's is to put the Echolink to a pseudo node and then permanently link that to the primary Allstar node at startup so its easier to disconnect if needed. I have not see a good sample rpt.conf file that implements that. Does someone run in that configuration would would be willing to share a suitably redacted version of their config file(s)? Should we do the same thing with IRLP? -Doug-, KD7DK

3 2

Pi Zero
by George Csahanin 25 Aug '18

25 Aug '18

Tried DIAL on s Pi Zero with WiFi. The os runs ok, WiFi ok asterisk gives a segmentation fault snd just sits retrying every ten seconds. Am I trying the impossible with the Pi Zero? Aug 24 14:53:35 repeater systemd[1]: asterisk.service: Failed with result 'signal'. Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart. Aug 24 14:53:45 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon. Aug 24 14:53:45 repeater systemd[1]: Started Asterisk PBX and telephony daemon. Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Main process exited, code=killed, status=11/SEGV Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Control process exited, code=killed status=11 Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Unit entered failed state. Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Failed with result 'signal'. -- George Csahanin 10100 Carson Ranch Rd. Crowley, TX 76036 682-708-5716 home 401-338-0568 cel

2 1

Web Transceiver Update
by Bryan Fields 23 Aug '18

23 Aug '18

Wanted to give a quick update as the ops team believes we have this licked. If you're able to get it to run in your browser, it should work now. If you have Java issues, that sadly between you and the PC, but I've tested the in a windows 7 VM in IE (ick) and it works. I'd give out a special thanks to the team members who re-coded the undocumented server-side program to make this work in a very short time. Reminder, not all nodes support this, they must allow it. Please reach out to helpdesk(a)allstarlink.org if you have issues that are not java related. 73s -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

2 1

Fwd: ASL DAHDI error- asterisk not working
by Clifford Novey 22 Aug '18

22 Aug '18

Subject: DAHDI error- asterisk not working RPi3 and stock Allstar (not hamvoip/Crompton etc.) I just did apt-get upgrade then update. Looked like there were some big kernel updates possibly. Asterisk stopped working. 3 blocks of info below- 1- output of "service asterisk status" 2- output of "service asterisk start" 3- output of "journalctl -xe" Any suggestions appreciated- thanks very much. Clifford KK6QMS pi@KK6QMS-ASL-48654:~ $ sudo su root@KK6QMS-ASL-48654:/home/pi# service asterisk status ● asterisk.service - Asterisk PBX and telephony daemon Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:asterisk(8) Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk PBX and telephony daemon. Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job asterisk.service/start failed with result 'dependency'. Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk PBX and telephony daemon. Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job asterisk.service/start failed with result 'dependency'. root@KK6QMS-ASL-48654:/home/pi# then------------------------------>>>>> root@KK6QMS-ASL-48654:/home/pi# service asterisk start A dependency job for asterisk.service failed. See 'journalctl -xe' for details. root@KK6QMS-ASL-48654:/home/pi# ----------------------------------------------- > > > pi@KK6QMS-ASL-48654:~ $ sudo su > > root@KK6QMS-ASL-48654:/home/pi# journalctl -xe > > Aug 21 12:40:02 KK6QMS-ASL-48654 CRON[4240]: pam_unix(cron:session): > session closed for user smmsp > > Aug 21 12:42:37 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: > connected: 192.168.0.6::51946 > > Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: session started: user > pi permissions f > > Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: > authenticated: 192.168.0.6::51946, as pi (f permissions) > > Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: SPrintConnMgr: Failed > to add printer: server-error-service-unavailable > > Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pi : TTY=pts/1 ; > PWD=/home/pi ; USER=root ; COMMAND=/bin/su > > Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pam_unix(sudo:session): > session opened for user root by (uid=0) > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: Successful su for root by root > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: + /dev/pts/1 root:root > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_unix(su:session): session > opened for user root by (uid=0) > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_systemd(su:session): Cannot > create session: Already running in a session > > Aug 21 12:43:40 KK6QMS-ASL-48654 su[3496]: pam_unix(su:session): session > closed for user root > > Aug 21 12:43:40 KK6QMS-ASL-48654 sudo[3492]: pam_unix(sudo:session): > session closed for user root > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job > dev-dahdi-pseudo.device/start timed out. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Timed out waiting for device > dev-dahdi-pseudo.device. > > -- Subject: Unit dev-dahdi-pseudo.device has failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > -- > > -- Unit dev-dahdi-pseudo.device has failed. > > -- > > -- The result is timeout. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for > Asterisk PBX and telephony daemon. > > -- Subject: Unit asterisk.service has failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > -- > > -- Unit asterisk.service has failed. > > -- > > -- The result is dependency. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job > asterisk.service/start failed with result 'dependency'. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job > dev-dahdi-pseudo.device/start failed with result 'timeout'. > > Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pi : TTY=pts/0 ; > PWD=/home/pi ; USER=root ; COMMAND=/bin/su > > Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pam_unix(sudo:session): > session opened for user root by (uid=0) > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: Successful su for root by root > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: + /dev/pts/0 root:root > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_unix(su:session): session > opened for user root by (uid=0) > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_systemd(su:session): Cannot > create session: Already running in a session >

4 3

UPS for a PI 3 B+
by Ramesh Dhami 21 Aug '18

21 Aug '18

Hi All: This topic comes up from time-to-time! Does anyone have experience with the following UPS HAT: http://www.pimodulescart.com/shop/item.aspx?itemid=50 The ordering options seems to be a little confusing! Additionally, what I am looking for is: 1. Does this fully restore power once the battery has been discharged and the AC power is restored? - i.e., no buttons to press (my application is in an unattended / remote location) 2. Is this the s/w that I need to install: https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> Any incompatibility / will it break a DIAL install? Thanks, Ramesh. VA3UV / KN4RSD #27919 (and others!)

6 7

Issue with Node 45467 No PTT on node actions
by Keith Dobbins 20 Aug '18

20 Aug '18

I'm having an issue with my node that just started recently. It appears to be dead from the perspective that no action will cause a PTT to occur. I can execute susb key and it works fine from asterisk -rv but when I issue a rpt fun 45467 *722 to speak the time, I see the commands in the asterisk console, BUT no PTT action takes place and my node doesn't key up. Anywhere I can look to find out what the heck is going on? This a weird problem to me and like I said it has been working fine for months. I did a full re-install and it worked fine for a day or so then it's right back to where it was before. Latest version of the 1.1 install. DMK URI and Intel D525 Atom Board. Thanks for any guidance! Keith DobbinsSr. IT Systems EngineerManaged File Transfer/Mainframe Networks3402 Linden Street Parkersburg, WV 26104-1608 Amateur Radio Call Sign: N8KLD

3 2

SSH Access
by TGundo 2003 20 Aug '18

20 Aug '18

Hi all- I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. A few items I need some direction on: 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? 2. CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. Thank you all for the help! Tom W9SRV

3 11

Setting Up a Chicken Link With ASL
by Bob Pyke 19 Aug '18

19 Aug '18

The local club wants to link two repeaters (local and remote) using a 440 link. I’d like to see just how serious folks are about this before we go to all that expense. I’m looking for some pointers as I attempt to setup a “chicken link” with our remote repeater using a local radio attached to an Allstarlink node. The radio operates in half-duplex with the receive audio out over the internet, and the audio coming in from the internet is transmitted to the remote repeater. My first attempt resulted in ping ponging between the repeater and my local radio. I’m certainly missing something. I’m looking for some added insights. I started by using duplex=0 in rpt.conf Thanks, Bob K6ECM Sent from iPad

3 5

Registration refused
by lengriff＠optimum.net 17 Aug '18

17 Aug '18

On both my local system and our club systems, registration is refused from server 44.98.254.145. The others servers are OK, and the nodes list shows us all active. Any reason for the refusal? Message log shows: [Aug 16 10:20:06] NOTICE[457] Chan_iax2.c: Registration of '42690' rejected: '<unknown>' from: '44.98.254.145' [Aug 16 13:20:08] NOTICE[452] Chan_iax2.c: Registration of '42690' rejected: '<unknown>' from: '44.98.254.145' [Aug 16 21:28:20] NOTICE[461] chan_iax2.c: Registration of '42690' rejected: 'Registration Refused' from: '44.98.254.145' Len WB2HKK 　

2 1