Allstar keeps disconnecting whilst listening

DavidKirk

Hi just got my m1ke and connected to allstar. Listening to nwag 47977. It keeps saying m1ke disconnected. Then drops the connection

HA2NON

Check the device log at the Console section on the Status page of the web interface to find out more about the disconnect.

DavidKirk

Here is the log.
11:38:10 pwr: batt 46% est. 9h21m 3721mv usb 0ma temp 23.1°C chg 0ma bcons -102ma
11:38:10 pwr: batt 46% est. 9h21m 3721mv usb 0ma temp 23.1°C chg 0ma bcons -102ma
11:38:17 net-chk: ok (15 ms)
11:38:37 iax2: got hangup, cause: unknown
11:38:37 iax2: init reconnect
11:38:37 net-conn: connect retry in 14977 ms
11:38:37 spk: start
11:38:37 spk: local play: OMDC
11:38:37 spk: cp OM
11:38:37 mic-a3k-dmr: new call, cid edf5175f7fbaa714
11:38:38 spk: cp DC
11:38:39 mic-a3k-dmr: call end, data timeout: 0
11:38:52 iax2: connecting to 47977.nodes.allstarlink.org:4569
11:38:52 iax2: calling 47977.nodes.allstarlink.org:4569/s callingnr/name: 47977/39cbd58c3e9e user/pass: allstar-public/allstar (no calltok)
11:38:52 iax2: calling 47977.nodes.allstarlink.org:4569/s callingnr/name: 47977/39cbd58c3e9e user/pass: allstar-public/allstar
11:38:53 iax2: got accept
11:38:53 iax2: ringing for outgoing call...
11:39:02 iax2: got answer
11:39:02 spk: start
11:39:03 spk: remote play: OMCTHS0407090707
11:39:03 spk-r: got first packet
11:39:03 mic-a3k-dmr: new call, cid f8f9a5d485d4c685
11:39:09 spk: remote disc
11:39:09 mic-a3k-dmr: call end, data timeout: 0
11:39:10 pwr: batt 46% est. 4h51m 3707mv usb 0ma temp 24.6°C chg 0ma bcons -225ma
11:39:17 net-chk: ok (15 ms)
11:39:46 iax2: got hangup, cause: unknown
11:39:46 iax2: init reconnect
11:39:46 net-conn: connect retry in 14977 ms
11:39:46 spk: start
11:39:46 spk: local play: OMDC
11:39:46 spk: cp OM
11:39:46 mic-a3k-dmr: new call, cid b50a8d48496a322e
11:39:47 spk: cp DC
11:39:48 mic-a3k-dmr: call end, data timeout: 0

HA2NON

The "11:39:46 iax2: got hangup, cause: unknown" indicates that the server sent a hangup packet so it closed the connection.

Note that AllStarLink nodes refresh the list of registered nodes every 5 minutes, so you may need to wait up to 5 minutes after enabling node mode for the servers to recognize your device as a node and allow you to connect.

DavidKirk

HA2NON so what does that mean. My allstar node has no issues and stays connected.

HA2NON

It means the server closed the connection for some unknown reason.

DavidKirk

Why would that be? As my allstar node does not have that issue.

Kreblon

This issue has to be addressed. Why don't all other nodes disconnect every 5 minutes? RX/TX turn-around is also very slow. You must wait about 5 seconds after RX drops or it mis-fires. The M1KE firmware will have to ignore the disconnect request. Checked into the East Coast Reflector net this morning and it promptly dumped me when it was my turn! This is fixable.

DavidKirk

Kreblon found solution for this.

DavidKirk

I’m glad it’s not just me. I did think was it because I had my node connected at home so turned that off and exactly the same thing happens. Get the disconnect message then reconnects.

HA2NON

The server does not request a disconnect, it signals that it has closed the connection. Try contacting the server admins to find out why the server drops the connection.

DavidKirk

Fixed it. Had to register for another node number. Then in the advanced settings for allstar, tick the node box and add node number and password. Works no problem now no drop outs or disconnect.