[arm-allstar] Echolink questions
Robert Conklin
n4wgy.ham at gmail.com
Fri Jan 8 20:41:56 EST 2016
Thank you immensely Doug, you were a big help. Was indeed a port forwarding
issue, it now works fabulously.
autopatch - check
echolink - check
What nifty cool things can I do next with it?
--
Robert Conklin
*N4WGY <http://qrz.com/db/N4WGY>*
On Thu, Jan 7, 2016 at 9:35 PM, Doug Crompton <doug at crompton.com> wrote:
> Robert,
>
> First of all Echolink works fine when setup correctly. Make sure you have
> the proper ports forwarded to your Allstar server where Echolink is running
> and you do not have any other Echolink forwarded or running on the same
> public IP. Port forwarding is the number one problem and usually it is
> because it is not setup correctly in your router. Every router is a little
> different.
>
> If you are sure that is correct and all is correct in your echolink.conf
> file then go into the client and make sure you can see the Echolink
> database.
>
> asterisk -rvvv
> echolink dbdump
>
> A long list will go by. That is good.
>
> echolink dbget c <your call>
>
> This should list your call. It has to be uppercase and include the -L or
> -R if you are using that.
>
> If that looks good then use a cell phone (NOT WIFI) or internet not on
> your public IP and try to connect to your echolink address. You should have
> established at least your call and your call-l or -r so you have two
> echolink you can use at different public IP's. Both can have the same
> password if you want. To establish a -L or -R you need to become a sysop in
> the Echolink on Windows, then go to the Echolink site and establish the
> additional call(s).
>
> I think all this and more in in the echolink howto on the hamvoip.org
> webapge.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Thu, 7 Jan 2016 21:08:25 -0600
> From: n4wgy.ham at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] Echolink questions
>
>
> Greeting everyone, hope you are all well & happy.
>
> Just attempted adding echolink to my node.
> Ability to connect to the added echolink node is intermittent.
> No audio coming into the allstar node from an echolink connection.
> Audio from the allstar node to echolink comes out fine on echolink side.
>
> What might I be doing incorrectly? Any troubleshooting tips will be much
> appreciated.
>
>
> --
> Robert Conklin
> *N4WGY <http://qrz.com/db/N4WGY>*
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
> BBB and RPi2 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 web page - http://hamvoip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160108/964fa9db/attachment.html>
More information about the arm-allstar
mailing list