[arm-allstar] Two Node System - One node connects, second node does not.
Randy Neals
randy at neals.ca
Thu Apr 5 11:17:06 EST 2018
Thanks!
On Thu, Apr 5, 2018 at 9:14 AM Doug Crompton <wa3dsp at gmail.com> wrote:
> Randy,
>
> I fixed the problem on your server but I also wanted to let others know
> how this was resolved. I tried to call you on your node but you were not
> around. You made a mistake that others might make also and I wanted to show
> others how this was resolved in case they have the same problem.
>
> Every node defined in rpt.conf needs to have a functions stanza (and all
> others shown below) so the commands on that node are defined. Typically we
> use stanza's of the first node for all nodes but you can use a separate
> stanza for each node and define them separately.
>
> In your case you created a second node to replace node 1999 but you also
> renamed all the mapping to the second node and they did not exist. Below is
> what I did. I changed all of the mappings in the node 28706 node to point
> to the 28705 node since you had not created any new ones for 28706. If you
> do in fact want different functions, macros, wait times etc. for these two
> nodes then you would have to define a new stanza with the new commands
> like [functions=finctions28706] etc.
>
> ; Context mapping
>
> controlstates=controlstates
> ; Defines groups of control operator
> commands
> ; to be executed all at once. Can be
> combined
> ; with macros to allow changes to a nodes
> ; operating mode to be made quickly.
>
> scheduler=schedule28705
> ; Defines macros to be executed at a
> specific
> ; time and date. Uses a cron-like syntax
>
> morse=morse28705
> ; Contains definitions for morse code
> messages.
> ; One common morse stanza is shared across
> ; multiple nodes
>
> macro=macro28705
> ; Defines DTMF macro sequences
>
> functions=functions28705
> ; Defines DTMF function digit sequences. A
> ; function stanza has a reference to it
> defined
> ; inside a node stanza. Multiple function
> stanzas
> ; may be defined and used to provide
> different
> ; function lists for different sources
> ; (radio.phone, and link)
>
> phone_functions=functions28705
> link_functions=functions28705
>
> telemetry=telemetry
> ; Contains definitions for telemetry tones
> ; (courtesy tones, roger beeps, etc). A
> telemetry
> ; stanza has a reference to it defined
> inside
> ; a node stanza.
>
> wait_times=wait-times28705
> ; Contains time delays used to time audio
> ; telemetry events
>
> An easy way to do this when creating a second node is when you define the
> first node in setup the second 1999 node gets all these defined as the
> first node. Then when you come along later and change all 1999 to the new
> second node number it will not change the mappings for the second node as
> they have already been changed. Using nano with the "control \" option
> makes this easy.
>
> Also remember whenever you change anything in the config files you need to
> either reload them or restart asterisk.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, Apr 4, 2018 at 7:17 AM, "Randy Neals via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Hi there,
>>
>> I just upgraded my Raspberry Pi to the latest April 2 code using the menu
>> system.
>>
>> The second node on the system (28706) works normally.
>> The first node on the system (28705) doesn't want to connect to anything.
>>
>> First I checked the Registration Status.
>>
>>
>> VE3RTR1*CLI> iax2 show registry
>>
>> Host dnsmgr Username Perceived
>> Refresh
>> State
>>
>> 67.215.233.178:4569 Y 28706 72.142.152.114:4569
>> 60
>> Registered
>>
>> 67.215.233.178:4569 Y 28705 72.142.152.114:4569
>> 60
>> Registered
>>
>>
>> Then I turned on Asterisk debug @ level 7 and tried a connection with the
>> not working node, and then the working node to compare the debug output.
>>
>>
>> VE3RTR1*CLI> rpt fun 28706 *328700
>>
>> [Apr 4 07:04:04] NOTICE[431]: app_rpt.c:2838 cancel_pfxtone:
>> cancel_pfxfone!![Apr 4 07:04:04] NOTICE[431]: app_rpt.c:11292
>> collect_function_digits: digits=3 source=0
>>
>>
>> <Nothing further, prompt returns>
>>
>>
>> VE3RTR1*CLI> rpt fun 28705 *328700
>>
>> [Apr 4 07:04:13] NOTICE[430]: app_rpt.c:2838 cancel_pfxtone:
>> cancel_pfxfone!![Apr 4 07:04:13] NOTICE[430]: app_rpt.c:11292
>> collect_function_digits: digits=3 source=0
>>
>> [Apr 4 07:04:13] NOTICE[430]: app_rpt.c:11364 collect_function_digits:
>> rv=0
>>
>> [Apr 4 07:04:13] NOTICE[430]: app_rpt.c:2838 cancel_pfxtone:
>> cancel_pfxfone!![Apr 4 07:04:14] NOTICE[430]: app_rpt.c:11292
>> collect_function_digits: digits=32 source=0
>>
>> [Apr 4 07:04:14] NOTICE[430]: app_rpt.c:4087 node_lookup: Starting node
>> lookup: node = 2
>>
>> [Apr 4 07:04:14] NOTICE[430]: app_rpt.c:4071 nodes_stanza_node_lookup:
>> Not
>> found in nodes stanza: node = 2
>>
>> [Apr 4 07:04:14] NOTICE[430]: app_rpt.c:4016 flat_nodelist_node_lookup:
>> Looking for rpt_extnodes! filename = /var/lib/asterisk/rpt_extnodes
>>
>> [Apr 4 07:04:14] NOTICE[430]: app_rpt.c:11364 collect_function_digits:
>> rv=0
>> <Debug continues and node connects>
>>
>> Q. Any suggestion as to what I should check next?
>>
>> Thanks,
>> Randy
>> W3RWN
>> Seattle, WA
>>
> _______________________________________________
>>
>> 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
>>
>
More information about the arm-allstar
mailing list