[App_rpt-users] proxy registraltion

Steve Zingman szingman at msgstor.com
Sat Jan 23 18:53:23 UTC 2016


Did you try a second register line in iax.conf?

Sent via smoke signal (Verizon)
On Jan 23, 2016 1:51 PM, "Bryan D. Boyle" <bdboyle at bdboyle.com> wrote:

read the proxy docs that scott referenced on ohnosec; I'm pretty much doing
EXACTLY what it says there.  I've a Pi, running DIAL , connected via a wifi
dongle plugged into the Pi into an LTE hotspot, which I can throw in my car
along with the radios and duplexer and have a mobile repeater with full
allstar capabilities.  The reason the proxy, it seems, exists is that the
LTE IP address is a fungible/transient  thing, which allstar doesn't handle
very well as you traverse across tower boundaries.  So, in order to have a
mobile node, you stand up a proxy, as Scott has done to handle a few of us
hackers on our network, and configure alkstar to talk TO IT instead of
directly to the mother ship of the allstar network.

I'm using an Official Node Assignment. It has registered with Allstarlink
before. It's number is 42761.  it shows up in the master node list, in my
server listing, and in my allmon.  It does NOT, however, show up in the
active nodes listing, which means that, regardless of whether i can connect
to it, according to allstar, it's not marked as active.  My question
revolves around how to get it to show up in the active nodes list when it
registers via a proxy server.  I can connect it, but it's hidden in the
active node list, even though even my allmon instance sees it.

--
Bryan
Sent from my iPhone 6S...No electrons were harmed in the sending of this
message.



On Jan 23, 2016, at 12:19, Stacy <kg7qin at arrl.net> wrote:

Sounds like you are asking if you can register with more than one system
using the same node ID number.

If you look at your iax.conf file, you will see a line similar to:

register=<nodenumber>:<password>@site

<nodenumber> = your node number
<password> = your password

What you haven't told us is what node number you are registering as.  Are
you actually using your AllStar node number or are you using a private node
number in the range of 1xxx?

I'm not sure how AppRpt will handle having a single node number registered
on multple systems, although the underlying registration process is handled
by asterisk and not AppRpt itself.  It "should" work, but you never know
until you try it out.  You would just have to make sure that if you tried
this, you aren't bringing in the same audio source from multiple channels
(effectively bridging them), since the results would not be pretty --
especially if there are any delays.



You can setup multiple nodes with different node numbers and register to
different systems.

Take a look here for more information:

http://ohnosec.org/drupal/node/49

-Stacy

On 01/22/2016 08:03 PM, Bryan D. Boyle wrote:

Have a quick question...I've built a DIAL node on a Pi and have (with some
great help from Scott KB2EAR) successufully brought it up on an LTE hotspot
via wifi, and am using his hub as a proxy, successfully registering (and
working) through his hub.

I'm registering to his hub, not the allstarlink registry; so this means
that, for whatever reason (assuming because I don't touch the
registry...but wouldn't the proxy do that?) I don't show up in the active
nodes list.

If this is correct, and assuming you can't register to more than one
registry (is that redundant?), is there a work around that would let me
proxy my connection, but still also show me as active in the allstar
database?

Does this make sense (I'm building out a portable repeater, but want to
have a full asterisk instance running rather than an RTCM solution, and the
Pi, couple GM300s, URI, and mobile duplexer makes for a nice portable
node.  Not to mention that if I take the Pi, URI, and hotspot sans radios,
I built a speaker amp & Mic interface that plugs into the URI that gives me
asterisk connectivity without the radios...in a hotel room or some such...)

Just throwing this out there...TIA.
-- 
Bryan
Sent from my iPhone 6S...No electrons were harmed in the sending of this
message.




_______________________________________________
App_rpt-users mailing
listApp_rpt-users at ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll
down to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message
to the list detailing the problem.



_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20160123/ce7a8a93/attachment.html>


More information about the App_rpt-users mailing list