Can’t connect with Allstar

AI7HL

No Authority Found…

Log below. BTW… my node number is one digit longer than normal because at one time I had split my node. Perhaps this is a problem? Firmware v24. Tried connecting to two different large networks. Both fail in the same way. Requesting the token seemed to be successful.

19:06:29 spk: remote disc
19:06:29 spk: remote disc
19:06:29 mic-a3k-dmr: call end, data timeout: 0
19:06:29 iax2: connecting to 74.196.158.135:4570
19:06:29 iax2-call: calling s
19:06:31 iax2: got reject, cause: No authority found
19:06:31 iax2: init reconnect
19:06:31 net-conn: connect retry in 14989 ms
19:06:46 iax2: connecting to 74.196.158.135:4570
19:06:46 iax2-call: calling s
19:06:49 iax2: got reject, cause: No authority found
19:06:49 iax2: init reconnect
19:06:49 net-conn: connect retry in 14994 ms
19:06:59 spk: start
19:06:59 spk: remote play: OMCOHSSV
19:06:59 spk-r: got first packet
19:06:59 mic-a3k-dmr: new call, cid e9f36a9925b45912
19:07:03 spk: remote disc
19:07:03 mic-a3k-dmr: call end, data timeout: 0
19:07:04 iax2: connecting to 74.196.158.135:4570
19:07:04 iax2-call: calling s
19:07:06 iax2: got reject, cause: No authority found
19:07:06 iax2: init reconnect
19:07:06 net-conn: connect retry in 14999 ms

HA2NON

The server sent the "No authority found" error message to the M1KE. This is usually sent if the server configuration is invalid for the stanza allstar-public (or web transceiver connections are disabled on the server).

radioman408

I am having the same problem as above
11:28:56 httpsrv-ws:Â [0]Â websocketÂ openedÂ withÂ tokenÂ f6adf155
11:28:56 httpsrv-ws:Â [0]Â websocketÂ openedÂ withÂ tokenÂ f6adf155
11:28:56 net-conn:Â connectÂ retryÂ inÂ 6728Â ms
11:28:59 spk:Â remoteÂ disc
11:28:59 mic-a3k-dmr:Â callÂ end,Â dataÂ timeout:Â 0
11:29:02 iax2:Â connectingÂ toÂ 12.17.28.222:4569
11:29:02 iax2-call:Â callingÂ s
11:29:05 iax2:Â gotÂ reject,Â cause:Â NoÂ authorityÂ found
11:29:05 iax2:Â initÂ reconnect
11:29:05 net-conn:Â connectÂ retryÂ inÂ 14998Â ms

I haven’t been able to connect to any Allstar node.

Jeff KD6RC

radioman408

radioman408
I also have a valid token

HA2NON

Try node 46331, it works great.

radioman408

I was able to connect to node 46331 but not other nodes.

cheezhead

If the node is not configured to accept web transceiver connections you will not connect to them with the M1KE.

AI7HL

So… that rules out two of the largest Allstar networks in the world. Each of them having hundreds of repeaters and nodes connected. Can’t connect to either one.

Bob_N5DEA

AI7HL what are the two largestest networks of AllStar? I’m new to AllStar.
Thanks

HA2NON

Our server list has servers which have indicated on their allstarlink.org node config that they support web transceiver connections. If they don't support it then ask them to fix their Asterisk or allstarlink.org config.

What you can also do is to connect to another node and link the desired server with DTMF commands.

AI7HL

Bob_N5DEA

Two of the largest. I have no idea who are the two largest.

HA2NON

It is one network itself.

FredFeddersen

There is a work around.
Check other nodes that are connected to the server you want to connect to that won't let the m1ke connect.
I can't connect to 41288, but I connect to another node that is connected to 41288.
Then I save it.

AI7HL

FredFeddersen

Yeah. I thought of that. But the networks I hang out on will call you out on that and ask you not to do it.

Bob_N5DEA

AI7HL yes, you brought it up 2 days ago about the largest networks.

FredFeddersen

I can't connect to 41288 but I can connect to 61891 which is connected to 41288.
Nobody has ever told me that I can't do that.
41288 is one of the largest, if not the largest.
Have a God blessed weekend.
73s