[arm-allstar] arm-allstar Digest, Vol 37, Issue 19

Tue Jun 13 17:51:21 EST 2017

I've been using there HobbyPCB RS-UV3 for over a year now and had very good
luck with the radio and have a couple of them. I've been using RX PL never
tied the TX PL. But there is one thing you have to use the latest firmware
and use the Windows Program not the command line and that was from the guys
at HobbyPCB.

73,
Marty KD4HLV

> Message: 1
> Date: Tue, 13 Jun 2017 10:48:22 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] HobbyPCB RS-UV3
> Message-ID:
>         <CAMp6vsuNyYjFgkEzJpnXXDyJ9hGBaDWLNFHapTz55fAwZZ82Ww at mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Be cautious. I have one and I have been using it for almost a year. I had
> planned to do a howto on it but ran into problems. In theory it is a nice
> board. It uses a Baofeng tri-band chip, the one used in many Baofeng
> transceivers. To make it really clean it has added switched filters on the
> front-end. RF wise it seems OK, very clean. I primarily use mine on 222 Mhz
> as a local node.
>
> But here is the problem. The PL does not work well. I went around and
> around with hobbypcb about this. I got several firmware updates which put a
> band-aid on the problem but never fixed it. It had talk off issues on PL. I
> kind of figured it was in narrow mode but it was latter confirmed that it
> was not. I currently use mine in squelch only mode locally with the squelch
> set high to avoid noise keyups. You really need reliable PL or DCS on an
> Allstar node. I forget if I tried DCS but I am thinking I did and it too
> was not working correctly.
>
> This falls under the category of the seller says they are being used all
> over successfully as Allstar,
> IRLP, Echolink nodes but I don't buy it. I spend a lot of time on this
> board and never got it the way I wanted it. I was very disappointed as it
> would have made a great programmable node where you could easily set the
> band, frequency, PL etc. via Allstar. The programming works fine.
>
> Maybe I got bad hardware but I find that unlikely. I have had several
> others with boards confirm my findings.
>
> I suppose you could use it with an external PL board or with usbradio if
> that worked better. I have tried neither.
>
> One other more minor thing is there is a battery charger chip on the board
> that apparently has a high failure rate. Like 20% or something like that
> confirmed by Hobbypcb. Apparently there was a bad run of the chips. Mine
> failed right out of the box and I had to cut it out of the circuit. It was
> not a big deal to me as I would never have used it. This is probably under
> control now depending on how many potentially bad ones he has on the shelf.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
> On Tue, Jun 13, 2017 at 8:51 AM, "Jeremy Utley via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Hey all!  Has anyone tried to use the HobbyPCB RS-UV3 shield as a node
> > tranciever yet?  I just found this, and it looks intriguing.  Thinking
> > about
> > getting one for myself for a possible micro-node build.
> >
> >
> >
> > Jeremy, NQ0M
> >
> > _______________________________________________
> >
> > 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
> >
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 13 Jun 2017 11:16:56 -0400
> From: Stephen - K1LNX <k1lnx at k1lnx.net>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Doug Crompton <wa3dsp at gmail.com>
> Subject: Re: [arm-allstar] HobbyPCB RS-UV3
> Message-ID:
>         <CABbxpd85vaCT7kcc004AV2f08Qt=vCm_Bo8Ujn2tYku5RiJP9Q at mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Good info Doug, I have a couple of them that I spent a ton of money on with
> this same idea in mind, but never got around to working on it :(
>
> One other more minor thing is there is a battery charger chip on the board
> > that apparently has a high failure rate. Like 20% or something like that
> > confirmed by Hobbypcb. Apparently there was a bad run of the chips. Mine
> > failed right out of the box and I had to cut it out of the circuit. It
> was
> > not a big deal to me as I would never have used it. This is probably
> under
> > control now depending on how many potentially bad ones he has on the
> shelf.
>
>
> I was part of the 20%, I had it burn up on me. I would have never used it
> either, but was a little concerned when I smelled something burning and
> that was the end result.  In fairness, I can't remember if I accidentally
> overvolted it though, so that may have been part of the cause.
>
> Stephen
> K1LNX
>
> On Tue, Jun 13, 2017 at 10:48 AM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Be cautious. I have one and I have been using it for almost a year. I had
> > planned to do a howto on it but ran into problems. In theory it is a nice
> > board. It uses a Baofeng tri-band chip, the one used in many Baofeng
> > transceivers. To make it really clean it has added switched filters on
> the
> > front-end. RF wise it seems OK, very clean. I primarily use mine on 222
> Mhz
> > as a local node.
> >
> > But here is the problem. The PL does not work well. I went around and
> > around with hobbypcb about this. I got several firmware updates which
> put a
> > band-aid on the problem but never fixed it. It had talk off issues on
> PL. I
> > kind of figured it was in narrow mode but it was latter confirmed that it
> > was not. I currently use mine in squelch only mode locally with the
> squelch
> > set high to avoid noise keyups. You really need reliable PL or DCS on an
> > Allstar node. I forget if I tried DCS but I am thinking I did and it too
> > was not working correctly.
> >
> > This falls under the category of the seller says they are being used all
> > over successfully as Allstar,
> > IRLP, Echolink nodes but I don't buy it. I spend a lot of time on this
> > board and never got it the way I wanted it. I was very disappointed as it
> > would have made a great programmable node where you could easily set the
> > band, frequency, PL etc. via Allstar. The programming works fine.
> >
> > Maybe I got bad hardware but I find that unlikely. I have had several
> > others with boards confirm my findings.
> >
> > I suppose you could use it with an external PL board or with usbradio if
> > that worked better. I have tried neither.
> >
> > One other more minor thing is there is a battery charger chip on the
> board
> > that apparently has a high failure rate. Like 20% or something like that
> > confirmed by Hobbypcb. Apparently there was a bad run of the chips. Mine
> > failed right out of the box and I had to cut it out of the circuit. It
> was
> > not a big deal to me as I would never have used it. This is probably
> under
> > control now depending on how many potentially bad ones he has on the
> shelf.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> >
> > On Tue, Jun 13, 2017 at 8:51 AM, "Jeremy Utley via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Hey all!  Has anyone tried to use the HobbyPCB RS-UV3 shield as a node
> > > tranciever yet?  I just found this, and it looks intriguing.  Thinking
> > > about
> > > getting one for myself for a possible micro-node build.
> > >
> > >
> > >
> > > Jeremy, NQ0M
> > >
> > > _______________________________________________
> > >
> > > 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
> >
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 13 Jun 2017 12:05:43 -0400 (GMT-04:00)
> From: Harry Romano <hromano at earthlink.net>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] RPi3 WiFi
> Message-ID:
>         <17490982.8014.1497369943468 at elwamui-royal.atl.sa.earthlink.net>
> Content-Type: text/plain; charset=UTF-8
>
> How do i post a question on this forum?
>
> Harry
> KC4RPP
>
>
> -----Original Message-----
> >From: "\"Doug Crompton via arm-allstar\"" <arm-allstar at hamvoip.org>
> >Sent: Jun 12, 2017 11:22 AM
> >To: ARM Allstar <arm-allstar at hamvoip.org>
> >Cc: Doug Crompton <wa3dsp at gmail.com>
> >Subject: Re: [arm-allstar] RPi3 WiFi
> >
> >iaxrpt connects TO Allstar not the other way around. I doubt it has
> >anything to do with wireless but rather something is not setup correctly.
> >One gotcha is if your Allstar IAX port is on other than 4569 you must
> >specify the port in the iaxrpt setup. It does not sound like that is the
> >problem in your case though. Remember that wireless will be a different IP
> >address than wired when using DHCP as it is a different MAC address. Make
> >sure you are trying to connect to the right IP address. You can make the
> IP
> >address reserved in the router based on the MAC address of the Pi BUT you
> >can't reserve the same IP for both wire and wireless as they are different
> >MAC addresses.
> >
> >
> >*73 Doug*
> >
> >*WA3DSP*
> >
> >*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> >On Mon, Jun 12, 2017 at 10:34 AM, "John Isabella via arm-allstar" <
> >arm-allstar at hamvoip.org> wrote:
> >
> >> Fresh install 1.5 from hamvoip The config creates the WPA_suppliment and
> >> connects to all star servers and can do updates. However, I can not
> connect
> >> to iaxrpt on my windows machine.
> >> I took a RPi 2 and a usb WiFi adapter and put the sd card in it and it
> can
> >> connect to the iax windows client. So all the settings in .conf files
> are
> >> correct as well as iax windows client.
> >> If I use a hardwire to RPi3 it works. So I know the port forwarding and
> >> internal IP address are correct.
> >> I even took back the RPi3 and exchanged it for a different to eliminate
> >> the Pi3 WiFI as being defective.
> >> Anyone else have this problem or know of solution?
> >> Thanks K1IF
> >>
> >> _______________________________________________
> >>
> >> 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
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 13 Jun 2017 12:20:39 -0400
> From: dan at ozment.net
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Doug Crompton <wa3dsp at gmail.com>
> Subject: Re: [arm-allstar] Echolink Conferences
> Message-ID: <53dfb50a8917f22cdc70a56bf7e9b145 at ozment.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> No, they are at different locations.  The Allstar node and Echolink
> W4DTO-L is at our repeater location.  W4DTO-L is being managed by
> Allstar.  The other Echolink node, WB4QOJ-R, is offsite and is a stand
> alone Echolink node.  Plan # 1 was for users to connect to WB4QOJ-R
> remotely, and we use Allstar to link -L to -R.  That's the case where we
> aren't getting audio back from the RF side to -R.
>
> The other thing we discussed was just shutting down W4DTO-L and defining
> the -R node on Allstar.  Users would connect directly to it.  But, I can
> see that we might over power the Pi if we go that route.
>
> I'm stumped as to why the first method isn't working.  If I connect
> directliy to W4DTO-L with an Echolink client on the outside of that
> network I get two way audio.  So, I thing port forwrding is good there.
> Same thing is true of the -R node.  If we connect to it from a client al
> is good.  But, when I connect the two together I don't see to get audio
> routed all the way through.
>
>
>
> On 2017-06-13 10:30, "Doug Crompton via arm-allstar" wrote:
> > Dan,
> >
> >  I don't have a good enough picture of what you are doing? When you say
> > -L
> > and -R Echolink nodes are you saying they are both on the same public
> > IP
> > address? That would not work. Give me a map of what Echolink is on what
> > network?
> >
> > I have an Echolink -L node connected to a separate node on my hub
> > server.
> > That node is in turn connected to the hub on the same server. Echolink
> > port
> > forwarding is to that server. I can connect and disconnet the Echolink
> > at
> > will but just connecting/disconnecting the two Allstar nodes. I could
> > not
> > have any other Echolink on my public IP even if it was on another
> > Allstar
> > server unless I used a proxy.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> > On Tue, Jun 13, 2017 at 8:50 AM, "Dan Ozment via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> Still working with Echolink on my repeater connected node, and I
> >> wondered if someone could give me some advice on a direction.
> >>
> >> I set up Echolink on the node as a "-L" node with the default Echolink
> >> configuration (no conference mode).  I was able to connect to Echolink
> >> from my phone, and it works well with two way audio between Echolink
> >> and
> >> the RF side.
> >>
> >> My plan was to connect our public "-R" node to that one from an
> >> external
> >> source and let our users come in on the "-R" node.  It connects up
> >> great.  Audio from Echolink is sent out over the repeater, but we
> >> don't
> >> get audio from the repeater back to the Echolink "-R" node.  Any
> >> thoughts as to why that would happen?
> >>
> >> Another idea was to run the "-R" node from the Pi that is hosting
> >> Allstar.  I would need to allow conference mode and up to 20 users
> >> (although 5 to 10 is more realistic).  I'm using one of the later
> >> versions of the Pi 2.   Could it handle both?
> >>
> >> When we tried putting the "-R" node on the Allstar Pi we had mixed
> >> results keeping three users connected.  I wonder if I was just
> >> overpowering the Pi.
> >>
> >> I realize I'm not providing much configuration info here so that folks
> >> can help me diagnose what's going on.  At this point I'm trying to
> >> decide on the best approach to get our main Echolink node (WB4QOJ-R)
> >> successfully operational through our main Allstar node.
> >>
> >> Thanks for any input.
> >>
> >> 73,
> >>
> >> Dan
> >>
> >> W4DTO
> >> _______________________________________________
> >>
> >> 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
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 13 Jun 2017 12:24:03 -0400 (EDT)
> From: David McGough <kb4fxc at inttek.net>
> To: "\"Dan Ozment via arm-allstar\"" <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Echolink Conferences
> Message-ID:
>         <Pine.LNX.4.44.1706131200210.13761-100000 at goliath.inttek.net>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Hi Dan,
>
> First, I'll mention that the echolink node designation (like: "-R" or
> "-L" or nothing) doesn't matter to the chan_echolink driver, all nodes are
> treated the same way by AllStar.
>
> Second, for general info, I'll mention that only ONE instance of
> chan_echolink can be used on any running instance of Asterisk, even though
> the config file does allow you to attempt to setup multiple echolink nodes
> on a single Asterisk instance....By single Asterisk instance, I'm implying
> only one copy of Asterisk running on a single device, like a RPi2 or 3
> (or PC).
>
> Note that the echolink.conf conference parameter (e.g.: "confmode=yes" or
> "confmode=no") is deprecated and does nothing. This parameter was removed
> from the source code a long time ago, predating the hamvoip project. All
> echolink connections are effectively treated as "confmode=yes".
>
> As for the number of active echolink connections supported, I would think
> 10+ concurrent connections on a RPi2 should work fine, however I've not
> personally tried this. I expect the limiting factor is more likely to
> Internet bandwidth, rather than RP2/3 processing power--all echolink
> connections use the GSM CODEC, so no Asterisk transcoding is required.
> Any time Transcoding is required, that is probably the first limiting
> factor for processor horsepower that you'll hit with large numbers of
> users. I know several hams are currently running RPi3 boards as hubs and
> frequently have 40+ simultaneously connected AllStar nodes with no
> problems.
>
> 73, David KB4FXC
>
>
>
> On Tue, 13 Jun 2017, "Dan Ozment via arm-allstar" wrote:
>
> > Still working with Echolink on my repeater connected node, and I
> > wondered if someone could give me some advice on a direction.
> >
> > I set up Echolink on the node as a "-L" node with the default Echolink
> > configuration (no conference mode).  I was able to connect to Echolink
> > from my phone, and it works well with two way audio between Echolink and
> > the RF side.
> >
> > My plan was to connect our public "-R" node to that one from an external
> > source and let our users come in on the "-R" node.  It connects up
> > great.  Audio from Echolink is sent out over the repeater, but we don't
> > get audio from the repeater back to the Echolink "-R" node.  Any
> > thoughts as to why that would happen?
> >
> > Another idea was to run the "-R" node from the Pi that is hosting
> > Allstar.  I would need to allow conference mode and up to 20 users
> > (although 5 to 10 is more realistic).  I'm using one of the later
> > versions of the Pi 2.   Could it handle both?
> >
> > When we tried putting the "-R" node on the Allstar Pi we had mixed
> > results keeping three users connected.  I wonder if I was just
> > overpowering the Pi.
> >
> > I realize I'm not providing much configuration info here so that folks
> > can help me diagnose what's going on.  At this point I'm trying to
> > decide on the best approach to get our main Echolink node (WB4QOJ-R)
> > successfully operational through our main Allstar node.
> >
> > Thanks for any input.
> >
> > 73,
> >
> > Dan
> >
> > W4DTO
> > _______________________________________________
> >
> > 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
> >
>
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 13 Jun 2017 12:32:37 -0400
> From: Jim Fisher <jedijf at myfisher.org>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] RPi3 WiFi
> Message-ID:
>         <CAHVUCOciR5dLjZ3rYxiQNb5kYgrx-HZx0Ge4kqgSA=aYQcSVvQ at mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Solved!
>
> On 6/13/17, "Harry Romano via arm-allstar" <arm-allstar at hamvoip.org>
> wrote:
> > How do i post a question on this forum?
> >
> > Harry
> > KC4RPP
> >
> >
> > -----Original Message-----
> >>From: "\"Doug Crompton via arm-allstar\"" <arm-allstar at hamvoip.org>
> >>Sent: Jun 12, 2017 11:22 AM
> >>To: ARM Allstar <arm-allstar at hamvoip.org>
> >>Cc: Doug Crompton <wa3dsp at gmail.com>
> >>Subject: Re: [arm-allstar] RPi3 WiFi
> >>
> >>iaxrpt connects TO Allstar not the other way around. I doubt it has
> >>anything to do with wireless but rather something is not setup correctly.
> >>One gotcha is if your Allstar IAX port is on other than 4569 you must
> >>specify the port in the iaxrpt setup. It does not sound like that is the
> >>problem in your case though. Remember that wireless will be a different
> IP
> >>address than wired when using DHCP as it is a different MAC address. Make
> >>sure you are trying to connect to the right IP address. You can make the
> >> IP
> >>address reserved in the router based on the MAC address of the Pi BUT you
> >>can't reserve the same IP for both wire and wireless as they are
> different
> >>MAC addresses.
> >>
> >>
> >>*73 Doug*
> >>
> >>*WA3DSP*
> >>
> >>*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>
> >>
> >>On Mon, Jun 12, 2017 at 10:34 AM, "John Isabella via arm-allstar" <
> >>arm-allstar at hamvoip.org> wrote:
> >>
> >>> Fresh install 1.5 from hamvoip The config creates the WPA_suppliment
> and
> >>> connects to all star servers and can do updates. However, I can not
> >>> connect
> >>> to iaxrpt on my windows machine.
> >>> I took a RPi 2 and a usb WiFi adapter and put the sd card in it and it
> >>> can
> >>> connect to the iax windows client. So all the settings in .conf files
> >>> are
> >>> correct as well as iax windows client.
> >>> If I use a hardwire to RPi3 it works. So I know the port forwarding and
> >>> internal IP address are correct.
> >>> I even took back the RPi3 and exchanged it for a different to eliminate
> >>> the Pi3 WiFI as being defective.
> >>> Anyone else have this problem or know of solution?
> >>> Thanks K1IF
> >>>
> >>> _______________________________________________
> >>>
> >>> 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
> > _______________________________________________
> >
> > 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
> >
>
>
> --
> jim fisher
> Jedijf
> AJ3DI
> www.aj3di.com/
> www.myfisher.org
>
> "Do, or do not. There is no 'try.'"
>   --  Jedi Master Yoda
>
>
> ------------------------------
>
> Message: 7
> Date: Tue, 13 Jun 2017 12:49:09 -0400 (EDT)
> From: David McGough <kb4fxc at inttek.net>
> To: "\"Dan Ozment via arm-allstar\"" <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Echolink Conferences
> Message-ID:
>         <Pine.LNX.4.44.1706131243450.13761-100000 at goliath.inttek.net>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Hi Dan,
>
> Do you have any VPNs connecting the different sites?
>
> Is the WB4QOJ-R system running AllStar, the "real" echolink PC software or
> other (e.g.: theBridge)?
>
> 73, David KB4FXC
>
>
> On Tue, 13 Jun 2017, "Dan Ozment via arm-allstar" wrote:
>
> > No, they are at different locations.  The Allstar node and Echolink
> > W4DTO-L is at our repeater location.  W4DTO-L is being managed by
> > Allstar.  The other Echolink node, WB4QOJ-R, is offsite and is a stand
> > alone Echolink node.  Plan # 1 was for users to connect to WB4QOJ-R
> > remotely, and we use Allstar to link -L to -R.  That's the case where we
> > aren't getting audio back from the RF side to -R.
> >
> > The other thing we discussed was just shutting down W4DTO-L and defining
> > the -R node on Allstar.  Users would connect directly to it.  But, I can
> > see that we might over power the Pi if we go that route.
> >
> > I'm stumped as to why the first method isn't working.  If I connect
> > directliy to W4DTO-L with an Echolink client on the outside of that
> > network I get two way audio.  So, I thing port forwrding is good there.
> > Same thing is true of the -R node.  If we connect to it from a client al
> > is good.  But, when I connect the two together I don't see to get audio
> > routed all the way through.
> >
> >
> >
> > On 2017-06-13 10:30, "Doug Crompton via arm-allstar" wrote:
> > > Dan,
> > >
> > >  I don't have a good enough picture of what you are doing? When you say
> > > -L
> > > and -R Echolink nodes are you saying they are both on the same public
> > > IP
> > > address? That would not work. Give me a map of what Echolink is on what
> > > network?
> > >
> > > I have an Echolink -L node connected to a separate node on my hub
> > > server.
> > > That node is in turn connected to the hub on the same server. Echolink
> > > port
> > > forwarding is to that server. I can connect and disconnet the Echolink
> > > at
> > > will but just connecting/disconnecting the two Allstar nodes. I could
> > > not
> > > have any other Echolink on my public IP even if it was on another
> > > Allstar
> > > server unless I used a proxy.
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > >
> > > On Tue, Jun 13, 2017 at 8:50 AM, "Dan Ozment via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > >> Still working with Echolink on my repeater connected node, and I
> > >> wondered if someone could give me some advice on a direction.
> > >>
> > >> I set up Echolink on the node as a "-L" node with the default Echolink
> > >> configuration (no conference mode).  I was able to connect to Echolink
> > >> from my phone, and it works well with two way audio between Echolink
> > >> and
> > >> the RF side.
> > >>
> > >> My plan was to connect our public "-R" node to that one from an
> > >> external
> > >> source and let our users come in on the "-R" node.  It connects up
> > >> great.  Audio from Echolink is sent out over the repeater, but we
> > >> don't
> > >> get audio from the repeater back to the Echolink "-R" node.  Any
> > >> thoughts as to why that would happen?
> > >>
> > >> Another idea was to run the "-R" node from the Pi that is hosting
> > >> Allstar.  I would need to allow conference mode and up to 20 users
> > >> (although 5 to 10 is more realistic).  I'm using one of the later
> > >> versions of the Pi 2.   Could it handle both?
> > >>
> > >> When we tried putting the "-R" node on the Allstar Pi we had mixed
> > >> results keeping three users connected.  I wonder if I was just
> > >> overpowering the Pi.
> > >>
> > >> I realize I'm not providing much configuration info here so that folks
> > >> can help me diagnose what's going on.  At this point I'm trying to
> > >> decide on the best approach to get our main Echolink node (WB4QOJ-R)
> > >> successfully operational through our main Allstar node.
> > >>
> > >> Thanks for any input.
> > >>
> > >> 73,
> > >>
> > >> Dan
> > >>
> > >> W4DTO
> > >> _______________________________________________
> > >>
> > >> 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
> > _______________________________________________
> >
> > 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
> >
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ------------------------------
>
> End of arm-allstar Digest, Vol 37, Issue 19
> *******************************************
>