[App_rpt-users] Alternative to WebTransceiver java applet
kb4fxc at inttek.net
Mon Apr 17 14:27:50 EDT 2017
I'm all for using the hotspot approach, where applicable. But there are a
First, most hotspots are simplex, not duplex. Duplex is much more
desirable in various situations. To solve this, you can build backyard
repeaters out of a pair of 888 radios (I have 3 of them). But, that's even
more hardware to haul around.
Second, if you're traveling by plane, it's can be an adventure getting
this hardware past TSA! I haven't tried recently, but, in years past it
With a web application, these issues are largely eliminated.
...Just a few more thoughts.
73, David KB4FXC
On Mon, 17 Apr 2017, David Shaw wrote:
> Hello Everyone, The WebTransceiver is a great tool. But I think we should
> look at getting a hotspot going. Like the DVMega or the DV4Mini. A cheap
> low power hotspot would be great. But I can't code or build a hotspot so
> just a thought.
> Please not say, just build one out of a Baofeng radio. Rework W9SH's iaxRpt
> software or direct node to work with a USB Radio. Small and cheap that just
> works when you plug it in.
> OK I'm done. Thanks for your time.
> Thanks, David
> "Laws that forbid the carrying of arms...disarm only those who are neither
> inclined nor determined to commit crimes. Such laws make things worse for
> the assaulted and better for the assailants; they serve rather to encourage
> than prevent homicides, for an unarmed man may be attacked with greater
> confidence than an armed one."
> Thomas Jefferson
> On Mon, Apr 17, 2017 at 9:26 AM, Steve Zingman <szingman at msgstor.com> wrote:
> > I don't think anyone was referring to HTML5 as a programming language.
> > More of a shorthand to describe a possible solution.
> > That is the reason the dev team is looking at the existing code. we all
> > know java has to go. IAX would be the preferred stack.
> > 73, Steve N4IRS
> > On 4/17/2017 12:16 PM, David McGough wrote:
> >> Hi Everyone,
> >> I agree that the WebTransceiver is a powerful addition to the AllStar
> >> project. I've got several hams who use it on a regular basis for repeater
> >> access, so, I hate to see it go as well.
> >> As we all know, web browser developers are rapidly phasing out all support
> >> for java applets. And, along with this phasing out process, continuing to
> >> make java work is a constantly moving target---every time a browser update
> >> comes down the pipe, you have to go and tweak settings AGAIN make java
> >> work.
> >> The biggest problem I see with "upgrading" the WebTransceiver is replacing
> >> the IAX2 protocol stack with updated version which is modern-browser
> >> friendly. We need to remember that all the hoopla about HTML5 is fine,
> >> language used. Another large component required is the actual audio
> >> interface to the PC and some supported CODEC for communication across
> >> IAX2...For this requirement, I believe the WebRTC toolkit, which is
> >> included in modern browsers, could be leveraged.
> >> Thoughts?
> >> 73, David KB4FXC
> >> On Mon, 17 Apr 2017, Doug Kingston wrote:
> >> I see 2 significant use cases:
> >>> 1. User wants to connect to a public Allstar node
> >>> In this case, they don't have a prior relationship with the node and
> >>> there
> >>> is no account/password that the user knows that they can use to log in.
> >>> Today in the Java applet, my understanding is, they authenticate to the
> >>> Allstar central server with their Allstar username/password and the Java
> >>> traffic is proxies through that central site is some way and on to the
> >>> public node. Its possible the central node provides credentials to the
> >>> java applet and it connects directly, but Steve can say more
> >>> definitively.
> >>> 2. User has iaxrpt username/password credentials for a particular node
> >>> This is certainly true for private nodes and for public nodes where
> >>> people
> >>> want to use an app like iaxrpt. They need to receive credentials from
> >>> the
> >>> node operator before using the node.
> >>> I think this is a summary of the basic modes. The reason we need some
> >>> form
> >>> of authentication is to prevent random non-hams from accessing Allstar
> >>> nodes and initiating transmissions. It would be nice to take the central
> >>> node out of the normal path except for the authentication process.
> >>> -Doug-, KD7DK
> >>> _______________________________________________
> >> App_rpt-users mailing list
> >> App_rpt-users at 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/c
> >> gi-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 at 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/c
> > gi-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.
More information about the App_rpt-users