[arm-allstar] Erratic ability to connect, or not

[Jim Aspinwall No1PC]

1. Yesterday was not able to connect via AllStarLink Webtransceiver, today, can connect.  My account, my nodes, etc.  The Webtransceiver does not provide for choice of CODEC - that I know of.
2.  The Android iaxRPT app does not provide for codec selection/config..  My install also variously has/has not connected.  Only one account/name and password has been used across related testing, from different clients.
3. Pertinent stanzas in iax.conf include:
disallow=all                                                                    allow=g726aal2                                                                  allow=ulaw                                                                      allow=gsm tos=0xBC 


[radio] has:[radio]type=userdisallow=allallow=g726aal2allow=ulawallow=gsmcodecpriority=hostcontext=radio-securetransfer=no
That order/those parameters per many suggestions, references.  
4. None of the configurations have changed between no-connect and can connect states of the node.  Could be old eyes or Murphy...
Thanks in advance for the 'consult' !

-----------------
Message: 1


Date: Sun, 12 Nov 2017 12:53:30 -0500
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Erratic ability to connect, or not
Message-ID:
    <CAMp6vst2y_Od1XD29E_i3VEx1RXGTjwRk=vKWya+OuA4Ci2Reg at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Jim,

 If you are seeing incoming connection attempts and failures in your client
it would indicate they are getting through so your port forwarding is
working. Two major things could cause an incoming connection to fail. One
is that you do not have return addressing information for them and the
other is that there is a codec mismatch. That is they are using a codec you
do not support. Neither should be happening in a default installation.
There are other less likely things that could cause this like some screwy
one way Internet connection.

If you can catch a connect that is not working in the client and post the
messages you are seeing it would be helpful. The client messages are the
log and can tell you what the problem is.

If you know the node number of the failed connect you can check if you have
addressing information for them in the client -

rpt lookup <node>      - node without <>

It will tell you what information your Allstar has about that node. Also
have you changed anything in your installation like allowed codecs, etc.


*73 Doug*

*WA3DSP*