[arm-allstar] remote receivers for repeater

LaRoy McCann lmccann at dtisp.com
Mon Oct 23 08:37:07 EST 2017


Glenn,

Make sure you can ping 192.168.11.5 from 192.168.11.4.
You would do this from a command prompt on the Pi. ///ping 192.168.11.5/
If that is not successful, then you have a network problem.

I have not followed this thread, but I read something about using 
Ubiquiti for the wireless links.
I assume these are in bridge mode and not router mode. Can you ping each 
side of the wireless link?
Are the Pi's connected directly to the wireless units or are there any 
routers between them?


LaRoy McCann - K5TW


On 10/22/2017 6:35 PM, "KD0Q via arm-allstar" wrote:
> I may not be understanding what we need to do...
>
> Here's what we have:
>
> RCVR (IP=192.168.111.5)
>
>     iax.conf:
>
>         bindport=4570
>
>
>     ​rpt.conf
>
>         [1998]
>
>         ...
>
>         ​[1999]​
>
>         ...
>
>         [nodes]
>
>             1998 = radio at 127.0.0.1:4570/1998,NONE
>             <http://radio@127.0.0.1:4570/1998,NONE>
>
>             1999 = radio at 127.0.0.1/1999,NONE
>             <http://radio@127.0.0.1/1999,NONE>
>             1997 = radio at 192.168.111.4:4571/1997,NONE
>             <http://radio@192.168.111.4:4571/1997,NONE>
>
>
> XMTR (IP=192.168.111.4)
>
>     iax.conf:
>
>         bindport=4571
>
>
>     ​rpt.conf
>
>         [1997]
>
>         ...
>
>         ​[1999]​
>
>         ...
>
>         [nodes]
>
>             1997 = radio at 127.0.0.1:4571/1997,NONE
>             <http://radio@127.0.0.1:4571/1997,NONE>
>
>             1999 = radio at 127.0.0.1/1999,NONE
>             <http://radio@127.0.0.1/1999,NONE>
>             1998 = radio at 192.168.111.5:4570/1998,NONE
>             <http://radio@192.168.111.5:4570/1998,NONE>
>
>>
>
> What am I missing?
>
> Thanks, Glenn - kd0q
>
> On Sun, Oct 22, 2017 at 6:09 PM, "Doug Crompton via arm-allstar" 
> <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>
>     Glenn,
>
>      Whenever you have multiple servers on a LAN and your router does
>     not do
>     hairpin loopback and* <http://www.crompton.com/hamradio
>     <http://www.crompton.com/hamradio>>*especially when
>     ports are different and always when you use private nodes you have to
>     manually route from each server TO AND FROM every server you want to
>     connect to. See this howto at hamvoip.org <http://hamvoip.org> -
>
>     https://www.hamvoip.org/multi-server%20howto.pdf
>     <https://www.hamvoip.org/multi-server%20howto.pdf>
>
>     Allstar uses a database to lookup nodes. If they are private there
>     is no
>     lookup and even if they are not, the IP address returned is your
>     public IP
>     not LAN IP and many router do not know how to handle that. Also
>     always use
>     port in routing - IP_address:port
>
>
>     *73 Doug*
>
>     *WA3DSP*
>
>     *http://www.crompton.com/hamradio
>     <http://www.crompton.com/hamradio>
>     <http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>>*
>
>
>
>
>     On Sun, Oct 22, 2017 at 5:05 PM, "KD0Q via arm-allstar" <
>     arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>
>     > Doug,
>     >
>     > I'm helping Stan, wb0emj,  get his system configured.  We are
>     starting out
>     > with a simple system of a split receiver/transmitter repeater on
>     private
>     > nodes - same network so have different ports for both nodes
>     defined in the
>     > iax.conf files.  Have the nodes, IP addresses and ports defined
>     in the
>     > [nodes] section of each rpt.conf. Also, registration lines are
>     commented
>     > out in the iax.conf files as these are private nodes.
>     >
>     > We are not able to connect the 2 nodes.  No connection results
>     from running
>     > "rpt fun 1997 *31998" from the asterisk CLI.  Where 1997 is the
>     local xmit
>     > node and 1998 is the remote rcvr node.  There weren't any hints
>     on the
>     > asterisk CLI as to if the command worked or not.
>     >
>     > Where do we start to figure out what's wrong?
>     >
>     > Thanks, Glenn - kd0q
>     >
>     >
>     > On Sat, Oct 21, 2017 at 7:08 PM, "Doug Crompton via arm-allstar" <
>     > arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>     >
>     > > Stan,
>     > >
>     > >  The URI pin outs are printed on the interface. Here are the
>     pins you
>     > will
>     > > be using -
>     > >
>     > > 1 - PTT
>     > > 8 - COS
>     > > 19/20 - GND
>     > > 21 - RX audio
>     > > 22 - TX audio
>     > >
>     > > Levels depend on settings in simpleusb-tune-menu.  For RX you
>     have a wide
>     > > range of levels and an RX boost. If the incoming level is too
>     high you
>     > can
>     > > always use a resistive divider to attenuate it.
>     > >
>     > > We generally recommend no more than two FOBS per PI. But you could
>     > > experiment with more. The downside is possible audio glitches.
>     A better
>     > > choice would be to use multiple Pi boards. Think of each board
>     as a port
>     > on
>     > > a conventional controller. The ports are connected together on
>     your local
>     > > LAN. Everything does not have to be on one board. Even using
>     multiple
>     > > boards it is a much less expensive approach to a conventional
>     controller
>     > > and in many way more flexible.
>     > >
>     > > The ubiquity link is nothing more than an Ethernet extension
>     from one
>     > place
>     > > to another. If you get all you r IP addresses setup properly
>     and the link
>     > > is reliable it should work fine.
>     > >
>     > > When using a FOB (any FOB) with a repeater you simply split
>     the receive
>     > and
>     > > transmit sides.  TX audio and PTT go to the transmitter and RX
>     audio and
>     > > COS go to the receiver.  Pnly one FOB is needed for a
>     repeater. If you
>     > are
>     > > bringing in RX audio from other bands just wire it to the RX
>     and COS of
>     > the
>     > > FOB leaving the PTT and TX audio a NC.
>     > >
>     > > I may not have answered all your questions. If not ask again.
>     > >
>     > >
>     > > *73 Doug*
>     > >
>     > > *WA3DSP*
>     > >
>     > > *http://www.crompton.com/hamradio
>     <http://www.crompton.com/hamradio>
>     <http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>>*
>     > >
>     > >
>     > > On Sat, Oct 21, 2017 at 3:49 PM, "Stanley Stanukinos via
>     arm-allstar" <
>     > > arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>     > >
>     > > > Stan would you do a stick drawing and repost. I believe what
>     you are
>     > > doing
>     > > > is possible. Also are you going to be using public or
>     private IP’s at
>     > all
>     > > > locations.
>     > > >
>     > > > Stan
>     > > >
>     > > > Sent from my iPhone
>     > > >
>     > > > > On Oct 21, 2017, at 1:53 PM, stan siems via arm-allstar <
>     > > > arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>     > > > >
>     > > > > I have 2 split site repeaters one uhf and one vhf that I
>     want to
>     > > operate
>     > > > with a uri and ras pi . what level of audio do I need out of the
>     > receiver
>     > > > to the uri and to which input? can I use 2 uri's or up  to 4
>     on one ras
>     > > pi
>     > > > as I will be adding receivers for 220 and 6m? the ras pi will be
>     > > connected
>     > > > to a ubiquity wireless link to the transmitter site and
>     another ras pi
>     > > and
>     > > > 2 uri's to the transmitters.   these 2 repeaters will also
>     be conected
>     > to
>     > > > the grundy center repeater via internet.
>     > > > >
>     > > > > could you pass along some info On how I should set this up.
>     > > > >
>     > > > > --
>     > > > > Thanks Stan Siems
>     > > > >  WB0EMJ
>     > > > >  The difficult we do right away the impossible just takes
>     a little
>     > > > longer and the words it can't be done should never be spoken!
>     > > > >
>     > > > > _______________________________________________
>     > > > >
>     > > > > arm-allstar mailing list
>     > > > > arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>     > > > >
>     http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>     <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 <mailto:arm-allstar at hamvoip.org>
>     > > >
>     http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>     <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 <mailto:arm-allstar at hamvoip.org>
>     > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>     <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 <mailto:arm-allstar at hamvoip.org>
>     > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>     <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 <mailto:arm-allstar at hamvoip.org>
>     http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>     <http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar>
>
>     Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by the *DTISP MailScanner* <http://www.dtisp.com/>, 
> and is
> believed to be clean.
>
>
> _______________________________________________
>
> 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




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


More information about the arm-allstar mailing list