just use a SIP client and make a phone call into the portal.. or just make a regular phone call into it JIM WB6NIL
CC: yokshs@sbcglobal.net; app_rpt-users@ohnosec.org From: wa4zlw@arrl.net Subject: Re: [App_rpt-users] Multiple Echolink Nodes Date: Sun, 31 Jul 2011 17:22:34 -0400 To: telesistant@hotmail.com
Jim
Any chance of a allstar client (mobile/PC) that could be java based for PC? That way we can get away from the echolink client?
Leon
Sent from my iPhone
On Jul 31, 2011, at 4:44 PM, Jim Duuuude <telesistant@hotmail.com> wrote:
okay Kyle... we'll keep you all happy n stuff... :-)
What I did to attempt to address both of these needs is add a parameter in each node stanza in 'rpt.conf', called 'eloutbound'. If, in rpt.conf for a particular node, you specify 'eloutbound=el1', *that* node will make its outbound echolink connections through el1. Any/other nodes that do not have 'eloutbound' specified will do the default thing (use el0). This is available in the app_rpt.c that will be publically accessible when the SVN updates at 14:15 PDT today.
JIM WB6NIL
From: yokshs@sbcglobal.net To: app_rpt-users@ohnosec.org Date: Sun, 31 Jul 2011 15:21:46 -0500 Subject: Re: [App_rpt-users] Multiple Echolink Nodes
Secondly, *all* outbound connections from app_rpt originate from el0.
This works beautifully for my purposes. I have 2 RF nodes and a hub node here.. To provide Echolink functionality for both nodes, I have Echolink connected to the hub node (2210). Outbound connections from either RF node work seamlessly.
Inbound Echolink calls hit the hub node only, unless a RF node is specifically connected to the hub node. I'm able to avoid the Echolink "drive-by" connect/disconnects in this way.
I can understand others wanting a different configuration, such as the multiple IP setup that Jeremy described, but hopefully the current configuration will also remain? Please don't "fix" this! hi hi
73.
Kyle K0KN
--- Original Message ---
ok.. first of all, echolink protocol requires a one-on-one correspondence between node number and public IP address. The "multiple instance" architecture of chan_echolink is only for systems that have multiple public IP addresses on them.
Secondly, *all* outbound connections from app_rpt originate from el0.
JIM WB6NIL
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users