[arm-allstar] need some help with LAN node linking
Sam Skolfield
kj6qfs at gmail.com
Sun Apr 5 21:22:48 EST 2015
Thank you, Doug and others, for the help.
Unfortunately, it looks like I already have everything set up the way you
have prescribed, but my problems persist.
I took Doug's advice and did a -rvvv on both servers.
Here is the "nodes" section for my BBB "A" (my repeater's allstar node and
a pseudo note for remote base frequency control)
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your local nodes, and private (off of allstar link) nodes here.
41531 = radio at 192.168.1.35/41531,NONE
1993 = radio at 192.168.1.35/1993,NONE,y
1994 = radio at 192.168.1.36:4568/1994,NONE,y
Here is the "nodes" section for my BBB "B" (Another group's VOTER backup
node, and a pseudo note for remote base frequency control of a second
radio)
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your local nodes, and private (off of allstar link) nodes here.
29733 = radio at 127.0.0.1/29733,NONE
1994 = radio at 127.0.0.1/1994,NONE,y
1992 = radio at 127.0.0.1/1992,NONE,y
1998 = radio at 192.168.1.35/41531,NONE
So, 41531 is my allstar node, 1993 is the local pseudo node, and 1994 is a
pseudo node on another Beaglebone. I changed the iax.conf for the
additional Beaglebone to port 4568.
Connecting from my main allstar node to the secondary Beaglebone looks
like this:
*Main Server CLI (**-rvvv) (my repeater's all-star node, primary remote
base node)*
[root at tester1 ~]# asterisk -rvvv
Asterisk , Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster at digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for
details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk currently running on tester1 (pid = 365)
Verbosity is at least 3
== Refreshing DNS lookups.
tester1*CLI> rpt fun 41531 *31994
-- Call accepted by 192.168.1.36 (format ilbc)
-- Format for call is ilbc
-- Hungup 'IAX2/192.168.1.36:4568-4142'
-- Hungup 'DAHDI/pseudo-617239376'
-- Hungup 'DAHDI/pseudo-542901585'
-- <DAHDI/pseudo-1866457995> Playing 'rpt/node' (language 'en')
-- <DAHDI/pseudo-1866457995> Playing 'digits/1' (language 'en')
-- <DAHDI/pseudo-1866457995> Playing 'digits/9' (language 'en')
-- <DAHDI/pseudo-1866457995> Playing 'digits/9' (language 'en')
-- <DAHDI/pseudo-1866457995> Playing 'digits/4' (language 'en')
-- <DAHDI/pseudo-1866457995> Playing 'rpt/connection_failed' (language
'en')
-- Hungup 'DAHDI/pseudo-1866457995'
tester1*CLI>
*Second Server CLI (**-rvvv) (VOTER backup server/ the second remote base
node)*
[root at tester2 ~]# asterisk -rvvv
Asterisk , Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster at digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for
details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk currently running on tester2 (pid = 371)
Verbosity is at least 3
tester2*CLI> rpt fun 29733 *31994
-- Hungup 'DAHDI/pseudo-102213755'
[Apr 5 22:07:38] NOTICE[624]: chan_iax2.c:4087 __auto_congest:
Auto-congesting call due to slow response
-- Hungup 'IAX2/127.0.0.1:4569-2856'
-- Hungup 'DAHDI/pseudo-231519670'
-- Hungup 'DAHDI/pseudo-835425161'
-- <DAHDI/pseudo-1001192220> Playing 'rpt/node' (language 'en')
-- <DAHDI/pseudo-1001192220> Playing 'digits/1' (language 'en')
-- <DAHDI/pseudo-1001192220> Playing 'digits/9' (language 'en')
-- <DAHDI/pseudo-1001192220> Playing 'digits/9' (language 'en')
-- <DAHDI/pseudo-1001192220> Playing 'digits/4' (language 'en')
-- <DAHDI/pseudo-1001192220> Playing 'rpt/connection_failed' (language
'en')
-- Hungup 'DAHDI/pseudo-1001192220'
tester2*CLI>
tester2*CLI>
tester2*CLI>
tester2*CLI>
tester2*CLI>
tester2*CLI>
tester2*CLI>
-- Accepting UNAUTHENTICATED call from 192.168.1.35:
> requested format = ulaw,
> requested prefs = (ulaw|ilbc|g726aal2|gsm),
> actual format = ilbc,
> host prefs = (ilbc|g726aal2|gsm),
> priority = mine
-- Executing [1994 at radio-secure:1] Rpt("IAX2/192.168.1.35:4569-10234",
"1994") in new stack
[Apr 5 22:08:17] WARNING[1288]: app_rpt.c:22691 rpt_exec: Reported node
41531 cannot be found!!
== Spawn extension (radio-secure, 1994, 1) exited non-zero on
'IAX2/192.168.1.35:4569-10234'
-- Hungup 'IAX2/192.168.1.35:4569-10234'
== Refreshing DNS lookups.
tester2*CLI> quit
Executing last minute cleanups
Thanks again for the help and 73.
On Sat, Apr 4, 2015 at 8:34 AM, Doug Crompton <doug at crompton.com> wrote:
> Sam,
>
> Two (or more) local nodes on different servers will talk to each other
> fine as long as things are setup correctly. Each server should be on a
> different iax port especially if you want outside connectivity. So in the
> case of two nodes, one could be the default 4569 and the other 4568.
>
> You would then need routing info in each nodes rpt.conf [nodes] stanza.
> Each node has to know how to reach the other including the port. As an
> example if you had two nodes, 1998 port 4569 at 192.168.1.100 and 1999
> port 4568 at 192.168.1.101 then it would look like this -
>
> at node 1999 -
>
> 1998 = radio at 192.168.0.100:4569/1998,NONE
>
> at node 1998
>
> 1999 = radio at 192.168.0.101:4568/1999,NONE
>
> The :4569 port in the 1998 could be left out as it is the default.I like
> to put it in so I can readily see what is going on.
>
> Also observe the log data as you connect. Put both nodes in the Asterisk
> client - asterisk -rvvv and connect from there - rpt fun <yournode#>
> *3<node>
>
> See what the log info says at both ends. It will tell you a lot. If you
> are not seeing anything at the receiving end then you have something wrong
> in your config.
>
> Also make sure you can actually ping both BBB servers.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Sat, 4 Apr 2015 00:50:45 -0700
> From: kj6qfs at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] need some help with LAN node linking
>
>
> Hello,
> I'm looking for a little "offline" help getting a couple of BBBs talking
> to each other via LAN. I've followed Doug's post to a tee, and after a
> night of very intense troubleshooting to try and avoid asking for help, I'm
> ready for some help.
>
> I have two functional BBB setups, both of which have a pseudo node in
> addition to a simpleusb node. The pseudo node on each BBB is used for
> serial frequency control of a remote radio. This works great. Now, I want
> to be able to connect the two BBBs together. This simple stuff is kicking
> my butt!!
>
> Thank you
>
> --
> KJ6QFS
> Sam Skolfield
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
> BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
--
KJ6QFS
Sam Skolfield
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150405/8a384653/attachment.html>
More information about the arm-allstar
mailing list