So… having an Allstar node I wanted to configure it for Echolink. It seemed this was just a matter of editing the pre-prepared configuration file echolink.xxx and renaming it to echolink.conf. Edits in place, this I did. Oh yes, and I set our broadband router up to forward the relevant ports to the hub. On restarting asterisk it gave numerous errors of the form ‘Error in parsing header on servers.echolink.org’. Hmmm.
Ok, scratching around the web I found that Echolink has a firewall test service at https://secure.echolink.org/pingTest.jsp. It failed. Ugh.
Then it dawned on me (meaning I read the documentation a little better!). I had set a callsign with ‘-L’ at the end which appeared to be the way to go. But this needed separate validation! Once that was done it all sprang into life.
Simple, and also obvious when I realised. Old age?
http://km6uso.net/index.php/2021/02/27/adding-echolink-to-your-allstar-hub/ is an excellent guide – there are others of course but this one pointed out clearly the need to register the -L or -R callsign.