Allstar Hub Information

I’ve search and search…guess I’m missing something.

I want to create a hub to connect a node at my house, a portable node, and a few other nodes down the road. For the life of me can not locate any information on the process other than someone mentioning “it’s easy.” Can someone point me in the direction of a how to or briefly explain what I need to change in a standard ASL image.

A HUB is merely a radio-less set-up.
Being headless, so to speak, you do not define with a usb driver, but dahdi driver.

rxchannel = dahdi/pseudo

Then make it connectable with iaxrpt or whatever your fancy for control if you need it.
(you should be able to control directly it in some manner)

Iit will accept connections per your defined use.

Being years later, here is a follow-up question on this subject instead of creating an entire new thread.
I believe it is pounded in everyone’s head that a HUB is just a radio less node. You find that specific information all over the place. BUT…
What are some basic settings for a HUB such as what duplex choice (which has many opinions), telemetry settings and so on and so on?

There is a bundle of old data here on the site and Google, mainly referring to sites that don’t exist anymore or has been moved to some undisclosed location.

In my case, I just want a basic hub that has no courtesy tones or other SPECIAL Bells and Whistles but just serves to pass traffic like a HUB should. What are some good settings and pointers to having a less troublesome HUB.

Having a more recent step-by-step along with pointers would better the chances of having a network full of properly operating systems as demonstrated with using a standardized sound device.

Could someone who has setup a few of these and has a standard procedure they follow in doing so, provide some really cool information on this subject? What are the benefits in doing it your way?

Las Vegas

Yea, I probably misspoke a bit to give a skinny answer to what most people use them for.

A ‘HUB’ really is just a common connection point.

You make to order to your needs.

If you set CT’s or specific timers on it, it is only present on the node/HUB you adjust it on. For each node has it’s own settings.

so, a specific CT on the HUB is not audible on the connecting nodes as they have their own settings. Just like hang time. Speaking of which, since a HUB may or may not have a TX/radio,
the hang time set for the HUB would not affect any connecting node.

But this is just a general fact of any ASL connection.
The ID of a HUB does not play on other connecting nodes. If you have a non-asl RF connected link, any audio on that would likely play including cw id’s in inside it’s cos.

So, take your time in thinking this through with any settings in it. Generally will be specific only to the HUB. On the HUB, you might let it announce all connections so you can monitor it in that way, but they will not be herd on other connected nodes if they have their settings otherwise.
Past of the beauty of app_rpt/ASL.

Make it what you need, but it really is a term to describe a common connection point.

Most do use them headless on separate cloud based servers to provide additional bandwidth for connections. But none of that is set in stone.