[arm-allstar] Connect OUT but not IN

[Doug Crompton]

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
>