[arm-allstar] webtranceiver

[Doug Crompton]

Wayne,

    My question would be why do you need the web transceiver. I suspect it
is at the end of its life as most are not going to mess around with old
versions of browsers that are much less secure just to use it.

Much of what the transceiver did is now replaced by things like iaxrpt on a
smartphone or PC. Also supermon is a great Allstar remote system manager.
There are many ways to skin a cat. If you need to offer entrance to
non-node owners use echolink and encourage them to get an Allstar node.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Wed, Aug 22, 2018 at 12:12 PM, wayne hale <waynehale at mac.com> wrote:

> Webtranceiver has worked perfectly for me for several years.  I use
> Firefox ESR browsers which takes care of the non Java support issues.
> Palemoon browser also still supports Java and has worked fine on Windows
> and Linux.
>
> The current problem started about the same time as the registration server
> issues.  I just verified again this morning that webtranceiver on Mac OSX,
> Firefox ESR WILL connect to node 2000 but that is the ONLY node it will
> connect to.  Any other node looks like it is going to connect but it
> disconnects almost immediately.
>
> I can connect to 2000 via webtranceiver, then connect to my remote base
> node from within webtranceiver but cannot connect directly to my remote
> base 28146 via webtranceiver.  I can connect via IAXRPT, 28146 shows green
> in the node list.  Unfortunately 28146 is running a very old version of
> ACID on an ITX motherboard with a URI and an adapter board that uses a real
> RS-232 connection for PTT.
>
> I have no idea how to use a more recent hamvoip version on a pi to
> accomplish the same remote base functionality.  It has worked fine in the
> past using the old software and hardware.  28146 works except by
> webtranceiver.  I can connect to my hub node via IAXRPT and then connect to
> 28146 so I don’t really think it is a registration issue with my nodes or
> other nodes I’ve used in the past but won’t connect now via webtranceiver.
>
> Tim asked a question if someone had been working on the phone portal as it
> may be related to the recent webtranceiver issues.
>
> I know I’m in a very small minority of people who actually like the way
> webtranceiver worked, especially for remote bases where it shows you, on
> the screen, what the remote frequency, offset, PL and power are.
>
> I have no idea why node 2000 works like it always has.  2000 is connected
> to 2024 so someone else is playing with it too.  Tim Sawyer has looked at
> the issue but has no solution either.
>
> I realize that webtranceiver has fallen from grace for a variety of
> reasons, the JAVA issue probably foremost but there are easy ways around
> that by using the Firefox Extended Support Release (32 bit for Windows) or
> Palemoon and setting the security exception in the Java Control Panel.  If
> using Linux Mint 18.3 IcedTea works in place of Oracle Java.
>
> Regardless of platform, the webtranceiver issue is the same.  Nodes look
> like they are going to connect but immediately fail although the keypad
> screen looks normal.  For some reason node 2000 does work as expected??
>
> 73,
> Wayne W6IZK
> 28146 remote base
> 29629 927.700 simplex
> 40799 145.23 repeater Phoenix
> 40809 Hub
>
> > On Aug 22, 2018, at 7:06 AM, Doug Crompton via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
> >
> > Wayne,
> >
> > If you are talking about the web transceiver I don't know as it has been
> > hit or miss for quite sometime due to enhanced security restrictions in
> > browsers regarding java. If you are having general connection problems in
> > your nodes make sure you are using the latest V1.5.3-40 update which is
> > using DNS node lookup from our servers. If you are still having problems
> > check that the node(s) are registered using check_reg.sh - if not we
> could
> > issue a temporary registration line you could add that uses our servers.
> > The next update, coming soon, will add all hamvoip V1.5 users to the
> > hamvoip registration server.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> > On Tue, Aug 21, 2018 at 3:57 PM, "wayne hale via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> Somebody must be working on the Webtranceiver issue.  Node 2000 is now
> >> reachable via webtranceiver and when I checked today (08/21/2018) 2000
> was
> >> connected to 2040.  It recognized my login correctly but when I
> >> interrogated it with *70, it correctly id’d 2040 but recited “space” as
> >> tranceive as on the screen there was a blank space between 2040 and
> W6IZK
> >> as being connected.
> >>
> >> No other nodes I tried will stay connected more than a second or two.
> >>
> >> Wayne W6IZK
> >> _______________________________________________
> >>
> >> arm-allstar mailing list
> >> arm-allstar at hamvoip.org
> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>
> >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>