[arm-allstar] Connect OUT but not IN

David dvd at dalfonso.us
Tue Nov 7 15:03:47 EST 2017 

Doug,

Eureka, that is the answer!  It all works great now with connection 
possible in both directions as it should.  Thanks very much for you 
guidance.

-Dave


On 11/6/2017 9:40 PM, "Doug Crompton via arm-allstar" wrote:
> Dave,
>
>   Sorry to take so long to get back to you. Now that I look at it I see the
> problem.  301 is NOT a valid private node number. Private nodes are
> 1000-1999. What is probably happening is that *33xxxxxx is an Echolink
> connect. It probably thinks you are doing an Echolink connection and
> ignoring the invalid node number. Change you private node to a valid number
> and make all the adjustments in the various files and it should work.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
> On Mon, Nov 6, 2017 at 12:03 AM, "David via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Doug,  thanks for guiding the troubleshooting on this for me. The result
>> as you see below is that connection still fails when 46704 tries to connect
>> to 301. No message appears,only the prompt returns.
>>
>> DVD2*CLI> rpt fun 46704 *3301
>> DVD2*CLI> rpt lookup 301
>> Node:   301, Method:  FILE, Actual: LOCAL, Data:
>> radio at 127.0.0.1:4579/301,NONE
>> Node: 46704, Method:  FILE, Actual: LOCAL, Data:
>> radio at 127.0.0.1:4579/301,NONE
>> DVD2*CLI> rpt lookup 46704
>> Node:   301, Method:  FILE, Actual: LOCAL, Data:
>> radio at 127.0.0.1:4579/46704,NONE
>> Node: 46704, Method:  FILE, Actual: LOCAL, Data:
>> radio at 127.0.0.1:4579/46704,NONE
>>
>> These connection commands all work correctly:
>>
>> DVD2*CLI> rpt fun 301 *346704
>>
>>   DVD2*CLI> rpt fun 301 *146704
>>
>> DVD2*CLI> rpt fun 46704 *1301
>>
>> Results of the lookup on 301 and 46704 after the three successful commands
>> were the same as after the unsuccessful one shown above.
>> -Dave
>> On 11/5/2017 6:24 PM, "Doug Crompton via arm-allstar" wrote:
>>
>>> Dave,
>>>
>>>     I would suggest you get supermon out of the mix. Go into the client and
>>> connect the nodes together. Let say you have node 40000 and 1800 -
>>>
>>> rpt fun 40000 *31800
>>>
>>> Then what do you get? If it connects disconnect it -
>>>
>>> rpt fun 40000 *11800
>>>
>>> Then go the other way -
>>>
>>> rpt fun 1600 *340000
>>>
>>> What messages do you see in both directions?
>>>
>>> Also give the output of
>>>
>>> rpt lookup 1600
>>>
>>> and
>>>
>>> rpt lookup 40000
>>>
>>> Of course replace all these node numbers with the numbers you are using.
>>>
>>>
>>> *73 Doug*
>>>
>>> *WA3DSP*
>>>
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>
>>>
>>> On Sun, Nov 5, 2017 at 8:52 PM, "David via arm-allstar" <
>>> arm-allstar at hamvoip.org> wrote:
>>>
>>> Doug,
>>>> Here is the CLI output when failing to connect IN to the private node:
>>>>
>>>> DVD2*CLI>
>>>>     == Manager 'admin' logged on from 127.0.0.1
>>>>     == Manager 'admin' logged off from 127.0.0.1
>>>>
>>>> Going the other way the connection is successful and the CLI output
>>>> starts
>>>> the same way but continues on with many additional lines.
>>>>
>>>> In my extensions.conf file there are uncommented entries for both nodes
>>>> under [radio-secure], [radio-iaxrpt], and just the private node under
>>>> [radio-secure-proxy].
>>>> I also have the Zoiper setup for the private node at the bottom under
>>>> [myphone].
>>>> -Dave
>>>>
>>>>
>>>> On 11/5/2017 2:20 PM, "Doug Crompton via arm-allstar" wrote:
>>>>
>>>> Dave,
>>>>>     My guess is you have no extension entry for the private node in
>>>>> extensions.conf. In this case the client is your friend. Open a client
>>>>> screen -  asterisk -rvvv - and monitor it when you connect from one to
>>>>> the
>>>>> other obviously only one at a time. See what the error messages say.
>>>>>
>>>>>
>>>>> *73 Doug*
>>>>>
>>>>> *WA3DSP*
>>>>>
>>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 5, 2017 at 3:48 PM, "David via arm-allstar" <
>>>>> arm-allstar at hamvoip.org> wrote:
>>>>>
>>>>> I have an RPi3 server running V1.5 with two nodes.  The main node is
>>>>>
>>>>>> connected to a repeater and is private.  The second node is registered
>>>>>> and
>>>>>> is configured as pseudo.
>>>>>> Using Supermon I can connect the private node to the registered node
>>>>>> but
>>>>>> not the other way.
>>>>>> This is also true connecting to other private nodes outside of my LAN,
>>>>>> that is, this one private node only connects going OUT to other
>>>>>> nodes.  I
>>>>>> believe I understand how private nodes are configured since I have
>>>>>> others
>>>>>> connecting just fine going IN or OUT.
>>>>>>
>>>>>> How is it that connection between two nodes on the same server can only
>>>>>> be
>>>>>> initiated from one of them?
>>>>>>
>>>>>> I don't see any errors on the Asterisk or Linux logs after the connect
>>>>>> attempt fails.
>>>>>> -David
>>>>>> _______________________________________________
>>>>>>
>>>>>> 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
>>>>
>>>> _______________________________________________
>>> 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

More information about the arm-allstar mailing list