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

Re: [App_rpt-users] Intel DN2800MT - 12V DC Powered Mobo
by Alan Adamson 14 Jan '13

14 Jan '13

I run 2 URI's in regular DSP mode and 3 RTCM's and the box doesn't break a sweat, it runs perfectly. Also the reason that I have more memory in mine. I use it for more than just Allstar :). Alan From: Randy Neals [mailto:randy@neals.ca] Sent: Monday, January 14, 2013 1:31 AM To: Alan Adamson Cc: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] Intel DN2800MT - 12V DC Powered Mobo Thanks Alan, Do you run the URI in regular (DSP) mode, or in simple mode with COR from radio? I'm curious how many radios it handles / system performance. -R On Sun, Jan 13, 2013 at 9:19 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote: I'm running ACID under debian on that exact board with a 60G SSD in a minibox case with 4 or 8G of memory can't remember. works just great From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Randy Neals Sent: Sunday, January 13, 2013 9:16 PM To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Intel DN2800MT - 12V DC Powered Mobo Hi, Has anyone tried ACID on the Intel DN2800MT motherboard? Fanless, built in DC Power supply 8V-19V DC., msata. Seems perfect for a repeater site. I'm going to try it unless someone has, and tells me they tried it and it didn't work :-) http://www.silentpcreview.com/article1251-page2.html -Randy

1 0

Upgrading node PC
by Ryan Collier 14 Jan '13

14 Jan '13

Mike, That very thing happened to me yesterday. If you look at asterisk -r, is it trying to connect? For some reason yesterday when I rebooted my machine it took 5 trying to get the node to register with the network then it took off. I was able to make connections again. 73 Ryan KB8PMY

3 3

Re: [App_rpt-users] Intel DN2800MT - 12V DC Powered Mobo
by Alan Adamson 14 Jan '13

14 Jan '13

I'm running ACID under debian on that exact board with a 60G SSD in a minibox case with 4 or 8G of memory can't remember. works just great From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Randy Neals Sent: Sunday, January 13, 2013 9:16 PM To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Intel DN2800MT - 12V DC Powered Mobo Hi, Has anyone tried ACID on the Intel DN2800MT motherboard? Fanless, built in DC Power supply 8V-19V DC., msata. Seems perfect for a repeater site. I'm going to try it unless someone has, and tells me they tried it and it didn't work :-) http://www.silentpcreview.com/article1251-page2.html -Randy

3 2

Raspberry
by jose 13 Jan '13

13 Jan '13

Anyone is using the URI DMK with rapsberry with success?

1 0

Upgrading node PC
by Michael Carey 13 Jan '13

13 Jan '13

Hi Everybody, I am in the process of upgrading my server PC to something a little less power hungry. I am running node 27871 on this server. The installation of ACID seemed to go OK, I've changed the network scripts to suit, set the timezone, resolv.conf, and moved my conf files over to the new PC. It all seemed to be working OK, the radio side is fine, I can connect to the node from my office PC with iaxRPT, BUT!!... I cannot seem to connect to any other nodes. My connect command does seem to be decoding OK while in an Asterisk shell, but nothing happens (apart from the normal telemetry tone back). The time command *81 works fine. I've tried to initiate a portal config download but I am not sure if this has happened or not. Any ideas on what I might be missing? I do this so infrequently that it's hard to get everything right each time. Michael. VK5ZEA

1 0

Echolink Connection Issue
by Matt Roberts 12 Jan '13

12 Jan '13

I am attempting to connect to Echolink 494492. I enter the command on my repeater, "*33494492." This is the *handiham* conference. The repeater acknowledges the command, and then I get a connection refused message from my repeater. The owner of the conference has tried to connect to my system, and could not do so either. Any other Echolink node I have ever connected to, or has connected to me has been able to do so. My repeater is set as a DMZ host on my router. With this configuration, no port forwarding should be required. I don't know if there is a log file which will allow me to diagnose this problem. I found one, but it was over 100MB in size. That file appeared to not have any useful information in it. I also tried from the CLI, and that didn't give me any information either. Has anyone else experienced this kind of problem? The owner of the conference is saying it's an issue with Allstar, but I don't think so! If it was an Allstar issue, I wouldn't be able to connect to Echolink nodes at all. Matt Roberts Phone: 386-679-1986 n9gmr(a)me.com Sent from my iPhone

3 4

Remote base using FT-817ND
by Michael Hebert 12 Jan '13

12 Jan '13

Hello group, I need help with a remote base setup using a Yaesu FT-817ND. I just setup a second node on my ACID box using an URIx for the remote base. Everything is working fine with tx audio, rx audio, COR and PTT. I am having issue with the CAT control. I connect from my UHF repeater node on the box using *3701 and try to issue remote base commands and the radio will not respond to CAT commands. Here is what I have in the rpt.conf [701] rxchannel = Radio/usb701 ; Rx audio/signaling channel remote = ft897 ; Radio Type functions = functions701 ; Function list from link phone_functions = functions701 ; Function list from phone ioport = /dev/ttyUSB0 ; Serial port for control iospeed = 4800 dusbabek = yes authlevel = 0 ; Authorization level ;; authlevel = 0 : Anyone can use it ;; authlevel = 1 : Requires log in, Waits for Tx key to ask for it ;; authlevel = 2 : Requires log in, asks for it automously ;mars = 0 ; set=1 for IC-706 w/MARS mods (optional) remote_inact_timeout=1800 ; Inactivity timer for remote base nodes only (set to 0 to disable). remote_timeout=5400 ; Session time out for remote base. (set to 0 to disable) ;remote_timeout=120 ; Session time out for remote base. (set to 0 to disable) ;remote_timeout_warning=30

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 47, Issue 15
by Chris Drummond 12 Jan '13

12 Jan '13

Matt, should it not be "*3494492. EchoLink is padded to 6 digits. You had two 3's Chris kc%izr On Fri, Jan 11, 2013 at 10:00 AM, <app_rpt-users-request(a)ohnosec.org> wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)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 > > You can reach the person managing the list at > app_rpt-users-owner(a)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 (Matt Roberts) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 11 Jan 2013 11:06:25 -0500 > From: Matt Roberts <n9gmr(a)me.com> > To: app_rpt-users(a)ohnosec.org > Subject: [App_rpt-users] Echolink Connection Issue > Message-ID: <517ECCE6-B152-4D6B-839E-1C7BBDACCF6D(a)me.com> > Content-Type: text/plain; CHARSET=US-ASCII > > I am attempting to connect to Echolink 494492. I enter the command on my > repeater, "*33494492." This is the *handiham* conference. The repeater > acknowledges the command, and then I get a connection refused message from > my repeater. The owner of the conference has tried to connect to my system, > and could not do so either. Any other Echolink node I have ever connected > to, or has connected to me has been able to do so. > My repeater is set as a DMZ host on my router. With this configuration, no > port forwarding should be required. I don't know if there is a log file > which will allow me to diagnose this problem. I found one, but it was over > 100MB in size. That file appeared to not have any useful information in it. > I also tried from the CLI, and that didn't give me any information either. > Has anyone else experienced this kind of problem? The owner of the > conference is saying it's an issue with Allstar, but I don't think so! If > it was an Allstar issue, I wouldn't be able to connect to Echolink nodes at > all. > > Matt Roberts > Phone: 386-679-1986 > n9gmr(a)me.com > > Sent from my iPhone > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 47, Issue 15 > ********************************************* >

2 1

Inactivity timeout message - will this work?
by Matt Beasant 10 Jan '13

10 Jan '13

I guess its obvious what I want to do but this doesn't seem to work: from my rpt.conf file.... lnkacttimerwarn=rpt/act-timeout-warning,digits/30,seconds so the question is, how do I add the "thirty seconds" to the "activity timeout in..." message? How is everyone else doing this? I'm sure I'm gonna kick myself when someone tells me! Many thanks, Matt G4RKY nodes 2250 and others...

2 1

Re: [App_rpt-users] no more streaming..
by Pawlowski, Adam 08 Jan '13

08 Jan '13

Check, if you haven't restarted the computer, that the ezstream process has terminated. I have to back out to the console and kill the sh and ezstream processes, since it will be running (and eating all my CPU). Asterisk won't say anything but it will not restart the streaming if it is already running. --- I recently set this up, and had to piece it together from several rpt messages. For RadioReference, the outstreamcmd: outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 --highpass 0.2 -r -m m -s 8 --bitwidth 16 --resample 22.05 - - | /usr/bin/ezstream -c /etc/ezstream.xml ezstream.xml: [root@W2SO-1 asterisk]# cat /etc/ezstream.xml <ezstream> <url>http://audio3.radioreference.com:80/[mount point]</url> <sourcepassword>[password]</sourcepassword> <format>MP3</format> <filename>stdin</filename> <svrinfoname>W2SO 147.255Mhz and 443.850Mhz Repeaters</svrinfoname> <svrinfourl>http://www.radioreference.com</svrinfourl> <svrinfogenre>Scanner</svrinfogenre> <svrinfodescription>W2SO Amateur Repeater</svrinfodescription> <svrinfobitrate>16</svrinfobitrate> <svrinfochannels>1</svrinfochannels> <svrinfosamplerate>22050</svrinfosamplerate> <svrinfopublic>1</svrinfopublic> </ezstream> Obviously change the information to match what you want. The description said it needed to match what you have for your feed on radioreference, which isn't the case technically, but it may be a policy thing.

1 0