<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Which channel are you using when you have this problem? I had channel A for the repeater audio and channel B for a monitor and when I lost channel A, channel B would still be working fine. Recently moved everything to channel B only and so far it has been fine. </div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Sent from my Verizon Wireless 4G LTE smartphone</div></div><div></div><br><br>-------- Original message --------<br>From: app_rpt-users-request@ohnosec.org <br>Date: 12/15/2014 02:23 (GMT-05:00) <br>To: app_rpt-users@ohnosec.org <br>Subject: App_rpt-users Digest, Vol 70, Issue 25 <br><br>Send App_rpt-users mailing list submissions to<br> app_rpt-users@ohnosec.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br>or, via email, send a message with subject or body 'help' to<br> app_rpt-users-request@ohnosec.org<br><br>You can reach the person managing the list at<br> app_rpt-users-owner@ohnosec.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of App_rpt-users digest..."<br><br><br>Today's Topics:<br><br> 1. Occasional URI Glitch (Dave)<br> 2. Re: Occasional URI Glitch (Tim Sawyer)<br> 3. FW: AllStarLink Financial Donation (Marshall Oldham)<br> 4. Re: Show link topology from cli? (Salik Satti)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 14 Dec 2014 11:30:18 -0700<br>From: Dave <k7dmk.1@gmail.com><br>To: app_rpt-users@ohnosec.org<br>Subject: [App_rpt-users] Occasional URI Glitch<br>Message-ID: <548DD73A.2040904@gmail.com><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>have a later model URI (CM119A) on my backyard repeater currently <br>running the newest build of Acid. I use WOL to start up the 1U <br>Supermicro Atom powered server every AM to bring up the repeater since <br>it is only on about 14-16 Hrs/day. I do this by dialling an extension on <br>my Asterisk home phone system. A WOL command gets fired off to start the <br>server. When Asterisk starts on the Acid box, a GPIO pin on the URI <br>turns on a SSR to power up the repeater hardware.<br><br>Occasionally, maybe once in 15 or 20 times, the machine seems to come up <br>normally, but the id and transmit audio is very low level and distorted. <br>The only way to fix it is to unplug the USB connector from the URI and <br>plug it back in. This resets the URI and all is good until the next time <br>it happens. Updating CentOS/Acid/Asterisk over the last year has not <br>helped. I suspect that some register in the CM119A is getting corrupted <br>while the machine is down.<br><br>I have tried a USB reset script I found that sends a bus reset command <br>to the C-Media USB port. I identified it's device id with the lsusb <br>command and inserted the proper bus and device id into the script. I <br>then added the script to rc.local to run it each time the computer <br>boots. It does appear to reset the bus, but it does not clear the <br>problem. Remotely rebooting or powering down the computer via DTMF does <br>not help either since USB power normally stays on. The only way to clear <br>the problem is to interrupt the USB power and create a power up reset <br>state for the URI.<br><br>Has anyone else seen this behavior? Any ideas short of some actual <br>hardware to interact with the USB power supply? A IP controlled power <br>switch could work, but it seems a bit of a overkill.<br><br>It's not a show-stopper with the repeater in my house, but when the <br>system gets moved to a remote location it will be.<br><br>Sorry if this gets double-posted, I inadvertently used a different email <br>address the first time.<br><br>Thanks, K7DMK<br><br><br>------------------------------<br><br>Message: 2<br>Date: Sun, 14 Dec 2014 10:44:00 -0800<br>From: Tim Sawyer <tim.sawyer@mac.com><br>To: Dave <k7dmk.1@gmail.com><br>Cc: app_rpt-users@ohnosec.org<br>Subject: Re: [App_rpt-users] Occasional URI Glitch<br>Message-ID: <5BF2AF12-B5E4-45A0-8CA6-6DF913195AF5@mac.com><br>Content-Type: text/plain; charset=utf-8<br><br>I don?t know if there is some bug in WOL but Linux likes to run all the time. If you leave the system on does it run ok?<br><br>> On Dec 14, 2014, at 10:30 AM, Dave <k7dmk.1@gmail.com> wrote:<br>> <br>> have a later model URI (CM119A) on my backyard repeater currently running the newest build of Acid. I use WOL to start up the 1U Supermicro Atom powered server every AM to bring up the repeater since it is only on about 14-16 Hrs/day. I do this by dialling an extension on my Asterisk home phone system. A WOL command gets fired off to start the server. When Asterisk starts on the Acid box, a GPIO pin on the URI turns on a SSR to power up the repeater hardware.<br>> <br>> Occasionally, maybe once in 15 or 20 times, the machine seems to come up normally, but the id and transmit audio is very low level and distorted. The only way to fix it is to unplug the USB connector from the URI and plug it back in. This resets the URI and all is good until the next time it happens. Updating CentOS/Acid/Asterisk over the last year has not helped. I suspect that some register in the CM119A is getting corrupted while the machine is down.<br>> <br>> I have tried a USB reset script I found that sends a bus reset command to the C-Media USB port. I identified it's device id with the lsusb command and inserted the proper bus and device id into the script. I then added the script to rc.local to run it each time the computer boots. It does appear to reset the bus, but it does not clear the problem. Remotely rebooting or powering down the computer via DTMF does not help either since USB power normally stays on. The only way to clear the problem is to interrupt the USB power and create a power up reset state for the URI.<br>> <br>> Has anyone else seen this behavior? Any ideas short of some actual hardware to interact with the USB power supply? A IP controlled power switch could work, but it seems a bit of a overkill.<br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Sun, 14 Dec 2014 18:11:32 -0800<br>From: "Marshall Oldham" <ke6pcv@cal-net.org><br>To: <app_rpt-users@ohnosec.org><br>Subject: [App_rpt-users] FW: AllStarLink Financial Donation<br>Message-ID: <019d01d0180c$71e6ce10$55b46a30$@org><br>Content-Type: text/plain; charset="us-ascii"<br><br>Greetings, <br> <br>I am reposting this message as I know some folks may not have caught this original message. <br> <br>The donations so far have been rather underwhelming and will not even begin to cover the<br>associated cost for <br>running the various servers which support Allstarlink.<br> <br>If you can spare the funds please help out. <br> <br>You can donate by using the following URL. <br> <br>https://allstarlink.org/<br> <br> <br>At the top of the webpage just slightly down there is a PayPal donate button<br> <br>73<br> <br>Marshall - ke6pcv<br><br> <br><br>From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of<br>Marshall Oldham<br>Sent: Saturday, November 29, 2014 10:24 AM<br>To: app_rpt-users@ohnosec.org<br>Subject: [App_rpt-users] AllStarLink Financial Donation<br><br> <br><br>Greetings fellow AllStarLink members, <br><br> <br><br>Once again I am reposting this email which is very similar to last year with the hopes that we<br>as the amateur community can step forward and support our hobby, mainly the app_rpt and<br>AllStarLink technology that we all enjoy today. <br><br> <br><br>As many of you that are new to app_rpt might NOT know. The creator of app_rpt and the<br>Allstarlink network has never charged or asked for financial support to keep the system going<br>for use in amateur radio.<br><br> <br><br>He has never charged users money to be a part of app_rpt or for use of the network, nor has he<br>ever made any profit off of specific hardware sales for the Allstarlink network. Through the<br>years he has put in a great deal of time and dedication along with his exceptional talents to<br>make app_rpt and the Allstarlink network the great VOIP technology that it has become today.<br>No other VOIP technology in the amateur radio community can even compare to the technology,<br>features and capability that is offered for free to anyone wishing to setup a node. <br><br> <br><br>Another understated fact is that there are monthly costs associated with keeping things running<br>smoothly for the system. These costs are for server collocation, domain certifications and so<br>on, amounting to roughly $175 per month. Jim pays these monthly fees from donations, but<br>mostly out of his own pocket. It would be nice if we could all pitch in and help him to at the<br>least cover these monthly costs for this coming year? <br><br> <br><br>I am proposing that we all donate to this cause via PayPal at the following URL. <br><br> <br><br>https://allstarlink.org/<br><br> <br><br>At the top of this webpage just slightly down there is a PayPal donate button.<br><br> <br><br>In the spirit and season of giving, let's all try and help out with the financial side, so we<br>can continue to use and enjoy this great technology that we have all come to know and love!<br><br> <br><br>I would also like to thank Jim, WB6NIL for all the many hours of work and support that he and<br>others have donated to this hobby so that the amateur community at large can benefit and enjoy<br>the use of his technology on a daily basis for free. <br><br> <br><br>73<br><br> <br><br>Marshall - ke6pcv<br><br>Node 2065, 2066, 2067, 2068, 29147, 29148, 29149, 29947, 29948, 29949 <br><br> <br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20141214/396eb16d/attachment-0001.html><br><br>------------------------------<br><br>Message: 4<br>Date: Mon, 15 Dec 2014 07:23:36 +0000 (UTC)<br>From: Salik Satti <saliksatti@yahoo.com><br>To: Doug Crompton <doug@crompton.com>, k5tra <k5tra@austin.rr.com><br>Cc: "app_rpt-users@ohnosec.org" <app_rpt-users@ohnosec.org><br>Subject: Re: [App_rpt-users] Show link topology from cli?<br>Message-ID:<br> <783962974.71192.1418628216605.JavaMail.yahoo@jws10069.mail.ne1.yahoo.com><br> <br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Doug,???????? I have setup a DMK Uri to work with XIPAR. And from asterisk cli when i issue radio tune command like:<br>radio tune rxnoise or rxvoiceit says:Done tries=12, Setting=5.000000, meas=505.000000ERROR: RX VOICE GAIN ADJUST FAILED.<br>?Salik Mumtaz Satti, Assistant Exective Engineer<br>National Radio And Telecommunication Corporation, Haripur kpk Pakistan <br>www.nrtc.com.pk<br>salik.satti@nrtc.com.pk<br>Contact: +923155414048<br>Skype: salik.satti6<br><br> <br><br> On Wednesday, November 19, 2014 11:12 AM, Salik Satti <saliksatti@yahoo.com> wrote:<br> <br><br> Hi <br>why do i need to connect my node with allstar or echolink i just want to set it up locally. how to set all this totally locally between two nodes. <br>Regards,<br>?Salik Mumtaz Satti, A-EXEN<br>National Radio And Telecommunication Corporation, Haripur Pakistan <br>www.nrtc.com.pk<br>salik.satti@nrtc.com.pk<br>Contact: +923155414048<br>Skype: salik.satti6<br><br> <br><br> On Monday, November 17, 2014 11:27 PM, Doug Crompton <doug@crompton.com> wrote:<br> <br><br> #yiv5996377240 --.yiv5996377240hmmessage P{margin:0px;padding:0px;}#yiv5996377240 body.yiv5996377240hmmessage{font-size:12pt;font-family:Calibri;}#yiv5996377240 That is certainly a way to do it. Here is another option that doesn't mess with the CLI. The 'archivedir' command in rpt.conf creates dated text files of all node activity. Unfortunately it also saves wav files of all of the audio. This is not a problem on a large disk based system but on the BBB it would just not work. So new in the BBB code is a command called 'archiveaudio' which was created to turn off the saving of the audio portion of the archive thus greatly reducing the storage load. I am not sure if this command has made its way to Acid. If you do use this on the BBB make sure you archive to a tmpfs like /tmp and also delete past files periodically because even they get large depending on you nodes activity. 'archivedir' saves based on date, creating one file per calendar day. <br><br>Example of using command in rpt.conf:<br><br>[27225]<br>rxchannel = SimpleUSB/usb<br>duplex=1<br>erxgain=-3<br>etxgain=3<br>archivedir=/var/log/asterisk/audio<br>archiveaudio=0????????? ; Disable saving .wav files<br><br>This creates a directory under the archivedir path of the node number.? Multiple archives can be stored if you put these commands in each node stanza. This listing shows files dating back to July 31 of all node activity. This is an Acid system modified to not save audio files.<br><br>[root@WA3DSP_Allstar asterisk]# cd /var/log/asterisk/audio/27225/<br>[root@WA3DSP_Allstar 27225]# ls<br>20140731.txt? 20140815.txt? 20140830.txt? 20140914.txt? 20140929.txt? 20141014.txt? 20141029.txt? 20141113.txt<br>20140801.txt? 20140816.txt? 20140831.txt? 20140915.txt? 20140930.txt? 20141015.txt? 20141030.txt? 20141114.txt<br>20140802.txt? 20140817.txt? 20140901.txt? 20140916.txt? 20141001.txt? 20141016.txt? 20141031.txt? 20141115.txt<br>20140803.txt? 20140818.txt? 20140902.txt? 20140917.txt? 20141002.txt? 20141017.txt? 20141101.txt? 20141116.txt<br>20140804.txt? 20140819.txt? 20140903.txt? 20140918.txt? 20141003.txt? 20141018.txt? 20141102.txt? 20141117.txt<br>20140805.txt? 20140820.txt? 20140904.txt? 20140919.txt? 20141004.txt? 20141019.txt? 20141103.txt? rxlog.txt<br>20140806.txt? 20140821.txt? 20140905.txt? 20140920.txt? 20141005.txt? 20141020.txt? 20141104.txt? tail.pl<br>20140807.txt? 20140822.txt? 20140906.txt? 20140921.txt? 20141006.txt? 20141021.txt? 20141105.txt? <br>20140808.txt? 20140823.txt? 20140907.txt? 20140922.txt? 20141007.txt? 20141022.txt? 20141106.txt<br>20140809.txt? 20140824.txt? 20140908.txt? 20140923.txt? 20141008.txt? 20141023.txt? 20141107.txt<br>20140810.txt? 20140825.txt? 20140909.txt? 20140924.txt? 20141009.txt? 20141024.txt? 20141108.txt<br>20140811.txt? 20140826.txt? 20140910.txt? 20140925.txt? 20141010.txt? 20141025.txt? 20141109.txt<br>20140812.txt? 20140827.txt? 20140911.txt? 20140926.txt? 20141011.txt? 20141026.txt? 20141110.txt<br>20140813.txt? 20140828.txt? 20140912.txt? 20140927.txt? 20141012.txt? 20141027.txt? 20141111.txt<br>20140814.txt? 20140829.txt? 20140913.txt? 20140928.txt? 20141013.txt? 20141028.txt? 20141112.txt<br><br>tail.pl, a Perl script which is attached, deals with the extraction of the data. In this case the RXKEY's only indicating who key the circuit. I also pull in the database file to nicely display the node QTH and location.<br><br>Here is what the processed rxlog looks like:<br><br>09/09/2014 08:41:26 RXKEY 40865?? WD9EQD? 147.435 Simplex?????? Smithville, NJ<br>09/09/2014 08:41:39 RXKEY 40561?? WA3DSP? ECHOLINK - 147090???? Richboro, PA - Hub<br>09/09/2014 08:41:45 RXKEY 40865?? WD9EQD? 147.435 Simplex?????? Smithville, NJ<br>09/09/2014 08:41:49 RXKEY 40561?? WA3DSP? ECHOLINK - 147090???? Richboro, PA - Hub<br>09/09/2014 08:41:59 RXKEY 29817?? NY3J??? 446.150 Simplex 91.5? Bensalem, PA<br><br>The rxlog is read by a simple script which keeps tabs on what the system is doing. The Perl script, tail.pl, is run in the background constantly monitoring the current archive file and saving parsed data to rxlog.txt :<br><br>[root@WA3DSP_Allstar 27225]# cat /usr/local/sbin/rxlog.sh<br>#! /bin/bash<br><br>tail -f /var/log/asterisk/audio/27225/rxlog.txt<br><br>Of course this could be expanded to view other parameters as all of the control data is in the individual text files. In my case the only thing that was important to me was who keyed or who is keyed in a situation where someone is hanging a circuit. It would be easy to show keyed status in a display using RXKEY and RXUNKEY <br><br>Where you put the files and how you deal with the data is your option. These are only examples.<br><br>73 Doug<br>WA3DSP<br>http://www.crompton.com/hamradio<br><br><br> <br>_______________________________________________<br>App_rpt-users mailing list<br>App_rpt-users@ohnosec.org<br>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br><br>To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. <br><br> <br><br> <br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20141215/c3a1af14/attachment.html><br><br>------------------------------<br><br>_______________________________________________<br>App_rpt-users mailing list<br>App_rpt-users@ohnosec.org<br>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br><br><br>End of App_rpt-users Digest, Vol 70, Issue 25<br>*********************************************<br><br></body>