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

NODE 7632300000 Telephone Portal
by Skyler F 09 Jan '18

09 Jan '18

When I call the Telephone Portal at (763) 230-0000 It tells me " welcome to the AllStar Network Telephone Portal " " Node 7632300000" "That Option is invalid, please enter the number of the node followed by the pound symbol" Then, I am able to proceed and connect. Does anybody know why the telephone portal is automatically entering it's own number as a node when I call it? Skyler

3 2

Remote recevier not being voted (new setup)
by Brian Perry 09 Jan '18

09 Jan '18

I was told to try to direct this to Tim Sawyer. I have a new system I have built. It is a repeater as the main site and a remote receive-only site. The main site is working just fine. If you key up a radio, it will key the repeater and repeat the audio. If you key up a radio on the remote site, you will see indications on the RTCM that it is receiving (and can verify using the 98 status option from the menu) but it is not being selected as a vote site and will not cause the transmitter to key up. Both sites are logging into the host server and you can see both in the CLI through the various debug levels, but there is never any indication in there that the remote site is receiving and routing audio to the server. The main repeater site shows all kinds of activity when you key a radio to it. If Tim or anyone else has an idea, I am open to just about anything. I have been working on this for weeks. Thanks, Brian Perry

4 8

Bridging AllStarLink to other modes.
by Steve Zingman 06 Jan '18

06 Jan '18

I was forwarded a post from Doug WA3DSP concerning interconnection to other services/modes on the HAMVOIP list. I have seen in the past that Doug considers himself the guardian of all good audio and AllStarLink. That is open to discussion. I think this needs to be addressed in the community. Great audio quality is a hallmark of AllStarLink and no one wants to compromise that. Another feature that singles out AllStarLink is flexibility. People have done some amazing things with AllStarLink. There are nodes and hubs that control what type of traffic pass through the node or hub. There are quite a few nodes and hubs that welcome experimentation. Connecting a foreign mode or service to a AllStarLink node is never a good idea without prior discussion. One of the many features of AllStarLink that drew me in over 10 years ago, was the ability to add features and devices. One very important fact is that it is open source. Well, at least the official AllStarLink distribution is. Channel drivers are available for EchoLink, D-Star, TLB and USRP. If it's not there, it can be added. AllStarLink welcomes people to add to and modify the open source available in github. If you have an idea, bring it up, submit a pull request and let's see how it fits. People are going to extend the capabilities of AllStarLink, that is a given. Those extensions may not be to everyone's liking. Under the banner of DVSwitch, a few of us have been building tools for bridging between different voice networks. One of those is AllStarLink. It does not matter if the purpose of the bridge is to expose analog users to the capabilities of a digital network or to display the capabilities of AllStarLink to a group of digital voice users that are not aware of a large network of open source analog nodes. There are quite a few hams that do not know about AllStarLink. This gives them a taste. I'm pretty sure every one of the digital voice radios in use support analog. Do we really want to display a negative attitude to other communities? I can tell you that not everyone on the digital voice networks want to see a bridge to analog. They don't want "those noisy analog signals" on their network. This is not a discussion of which voice mode is better. Nor is it about how to make digital voice sound better. I tell people building bridges the same thing, Don't just drop a analog bridge onto a digital channel without discussion first. One digital network I have seen is reporting over 10K calls per hour. (That might be a interesting stat to collect for AllStarLink) Bridging networks is not the purpose of AllStarLink and I would rather not see discussions of various networks on the AllStarLink user list. There are other places for that. The open source nature of AllStarLink lends itself to extension. Just be aware what you are doing and who it will effect. 73, Steve N4IRS

2 1

Thanks
by Steve Zingman 06 Jan '18

06 Jan '18

It's a new year, so happy new year. I just want to say THANK YOU! to everyone that has donated to help with the costs of maintaining the servers and services involved with keeping AllStarLink running. 73, Steve N4IRS

1 0

Issue with Morse ID - It doesn't
by Keith Dobbins 05 Jan '18

05 Jan '18

Okay, got all my issues with DIAL and my Allstar node figured out except for one. My original ACID node was a duplex repeater interface, my new node is a simplex node. Does the simplex node not Morse ID even if the beaconing=1 is set in the rpt.conf? I'd like it to ID every 10 minutes so for now till I'm comfortable everything hardware wise is playing nice and not locking up and so far I'm drawing a blank how to get that to happen. Keith DobbinsSr. IT Systems EngineerManaged File Transfer/Mainframe Networks3402 Linden Street Parkersburg, WV 26104-1608 Amateur Radio Call Sign: N8KLD

1 0

Remote already in this mode message
by Bryan Taylor 05 Jan '18

05 Jan '18

Hopefully a quick question, For a few days now I have one allstar node playing the “remote already in this mode” message about every 10 minutes. Anybody have any idea as to what could be causing it or where I could look to see what is causing it? It never did it before. I did add a new node to the network a few days ago but I did add the new node to it’s nodes stanza. It only connects to a hub node directly. There is nothing in the log files that points to anything. Google doesn’t find anything helpful either. Thanks Bryan Sent from my iPhone > On Jan 2, 2018, at 1:28 AM, Benjamin Naber <Benjamin(a)Project23D.com> wrote: > > Suppose one can copy the necessary php and other related files from a > hamvoip distro, and paste to another distro? > > Provided, some kind of http/https server is already installed. Probably > some other things need to be completed in that task line-up. > > ~Benjamin, KB9LFZ > > > >> On Fri, 2017-12-29 at 19:30 -0500, Pierre Martel wrote: >> nope not the same supermon ;-) >> >> >> 2017-12-29 18:54 GMT-05:00 Bob Pyke <k6ecm1(a)gmail.com>: >>> Try https://sourceforge.net/projects/supermon/ >>> >>> Thanks, >>> Bob >>> K6ECM >>> >>> Sent from iPad >>> >>> >>>> On Dec 29, 2017, at 2:37 PM, Tim Sawyer <tisawyer(a)gmail.com> wrote: >>>> >>>> Supermon code >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit http://lists.allstarlink >>> .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" >>> 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. >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.o >> rg/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" >> 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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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" > 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.

9 16

Re: [App_rpt-users] App_rpt-users Digest, Vol 107, Issue 3
by Barry Buelow 04 Jan '18

04 Jan '18

I'm not sure if this works the same in all flavors of ASL, but try a command using cop=37; disable remote telemetry. In rpt.conf, I have this entry. Sometimes I hear that "remote already..." and other annoying things coming from somewhere on a big hub system. This usually shuts it up. 834=cop,34 Barry w0iy 1. Remote already in this mode message (Bryan Taylor) > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 04 Jan 2018 11:36:36 -0330 > From: Bryan Taylor <overnite(a)me.com> > To: Users of Asterisk app_rpt <app_rpt-users(a)lists.allstarlink.org> > Subject: [App_rpt-users] Remote already in this mode message > Message-ID: <088DE2D6-9EA2-4DC3-8A43-2E78A0A7F5D5(a)me.com> > Content-Type: text/plain; charset=utf-8 > > > Hopefully a quick question, > > For a few days now I have one allstar node playing the “remote already in this mode” message about every 10 minutes. Anybody have any idea as to what could be causing it or where I could look to see what is causing it? It never did it before. I did add a new node to the network a few days ago but I did add the new node to it’s nodes stanza. It only connects to a hub node directly. > > There is nothing in the log files that points to anything. > > Google doesn’t find anything helpful either. > > Thanks > Bryan > Sent from my iPhone >

1 1

Supermon source
by john＠n2yp.com 02 Jan '18

02 Jan '18

I've done some reading and came across allmon2 and supermon where supermon seems to be the better option but I can't locate source information on implementing it. Is supermon only designed to work with hamvoip? If not where can I get the install information?

6 5

AllStarLink for the BeagleBoard-xM
by Steve Zingman 01 Jan '18

01 Jan '18

When the first versions of AllStarLink on Debian were created, one existing version was left out. That version was for the BeagleBoard-xM. The BBxM has a daughter board called the LOX for I/O to 2 radios. In my conversations with Jim, he really liked the Beagle and LOX combination. Or was it bagels and lox? I was never quite sure. Jim wanted me to make sure I continued to support the BBxM/LOX. We had existing users and they should not be left out in the cold. I agreed. I had problems making it work the way we wanted it, so it got shelved. I did not want to forget, so it I kept it very visible on the shelf. I could not help but see it. Something of a thorn in my side. I do not know how many users are out there. I do not know if the BBxM is still available. I do not know if DMK is still selling LOX board. But, a promise is a promise so here we go. I have built a proof of concept image for the BBxM. The image is built with Debian Stretch. The image requires a 8GB or larger SD card (for now) The login is repeater The password is allstarlink These are the things I still need to do: Build the image with apt-get install rather then building from source. You will then be able to do a apt-get upgrade and get the most current AllStarLink programs and upgraded Debian Stretch programs. Shrink the image so it will copy to a smaller SD card and then fill the root partition to fit the available space on the card. Regenerate the ssh keys on first boot. Set the user repeater to allow login with the password of allstarlink the first time then force setting a new password. Tweak the beagle.conf settings so a first time user (are there any?) will be able to make carrier access work and not get bit by the CTCSS setting. This image assumes you can edit config files in /etc/asterisk. <http://dvswitch.org/files/Testing/bbxm-asl.img.xz>

5 12