[arm-allstar] Echolink on Pseudo making a connection

[W2YMM]

Thanks for the Info Doug.


*First if you ssh to the server for your main node and 1999 you can use the
client to connect directly.Using your example -*


*asterisk -rvvvCLI>rpt fun 1999 *33009999*

*THIS WORKED*
*BUT*
And you can try this on the radio on your main node -
*41999*33009999#
*THIS DID work from node 28183 server 1 but not from node 41899 server 2*.
(41899 and 1999 were connected together)

I was just trying to do something a little different and find a round about
way
to use Echolink that was on my VPN on server 1 from Server 2.
Not a big deal, Just seeing if it could be done.

Also Feel Free to use any info I have posted on my site.
When ever I figure something out I like to post it
not only for others but for me to refer back to when
doing things away from my notebook.

http://www.w2ymm.com/allstar.html

I like to pay it forward when I figure something out.
Hope it helps someone when they get stuck.

Bob W2YMM


Robert Prybyzerski Jr
W2YMM
631-960-1051
http://www.w2ymm.com

On Sat, Jan 16, 2016 at 12:45 PM, Doug Crompton <doug at crompton.com> wrote:

> I don't think Echolink cares if the Allstar node linked to your Echolink
> node is registered. All it sees at the other end is your Echolink node and
> if that is registered there should be no problem.
>
> In other words you should be able to bring up an unregistered Allstar node
> and use it strictly for Echolink if you desire. Not that I am suggesting
> that is a good idea.
>
> So if you can connect directly from 1999 to an Echolink node using iaxrpot
> then you should be able to remote from your main node and do the same
> things.
>
> Again I have not tried this so interested in your results.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> From: w2ymm1 at gmail.com
> Date: Sat, 16 Jan 2016 11:52:29 -0500
> To: FredM at FredsPortraits.com; arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Echolink on Pseudo making a connection
>
>
> Thanks. That was the way I was doing it.
> To make things more complicated, i am trying to connect to 1999 which is
> on my "server1" which happens to be on a vpn from a node on "server 2"
>
> I can make the allstar connection fine. When 1999 on server1 is connected
> to my allstar node from server2. Then with the Echolink app on my phone I
> connect to my echolink node and it works fine as an incoming connection.
>
> Trying to figure out how to make an outgoing call when  connected to my
> pseudo node from server2.
>
> I think I'm confusing myself now :-)
>
> Sent from my iPhone
> Bob Prybyzerski
> 631-960-1051
>
> On Jan 16, 2016, at 11:07 AM, Fred McLean <FredM at FredsPortraits.com>
> wrote:
>
> Bob,
>
>
>
> You very likely cannot link 1999 to any EchoLink node as 1999 is a private
> node and not resolvable by the far end EchoLink node.
>
> Try connecting 28183 to a far end EchoLink node instead. You will not have
> to change anything on your .conf files.
>
>
>
> When I link to a far end echolink node such as The Danvers Repeater in
> Massachusetts I do the following on my main RF node.
>
> *33314375
>
>
>
> I hope that helps.
>
>
>
> Fred
>
> w0fcm
>
> 832-906-9793
>
>
>
> *From:* W2YMM [mailto:w2ymm1 at gmail.com <w2ymm1 at gmail.com>]
> *Sent:* Saturday, January 16, 2016 8:50 AM
> *To:* BeagleBone Black ARM Allstar <arm-allstar at hamvoip.org>
> *Subject:* [arm-allstar] Echolink on Pseudo making a connection
>
>
>
> I have Echolink enabled on node 28183 and it is working fine.
> I have just changed it to my Pseudo node 1999 on the same computer.
> That part seems to be ok.  (edited the files)
> My question is when I connect 28183 or any other nodes I have configured
> on my network to pseudo node 1999,
> How do I, Can I make a connection to another  Echolink station ?
> Is there another DTMF prefix I should be using ?
> I can connect via radio 28183 to 1999 but how do I then
> do I further connect 1999 to say Echolink *3009999 ?
> I've tried *33009999 for example and get a "Remote already in this mode"
> warning.
>
> Thanks Bob W2YMM
>
> Robert Prybyzerski Jr
> W2YMM
> 631-960-1051
> http://www.w2ymm.com
>
>
> _______________________________________________ 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/20160116/70f471ce/attachment-0001.html>