Archivedir not captureing node traffic

AllStarLink
1

I put archivedir into my ASL3 install.

It capture audio from a) station ids and anyone who has come INTO my node. It does not capture anything originating when I call directly into the node (I have an antenna hat with a freq of xxxx pl yyyy).

The config entries are:

archivedir=/var/log/asterisk/audio
archiveaudio=1 ; 0 Disable saving .wav files

Any ideas?

2

What’s the node configuration? Radio-less? simplex? voter?
archiveaudio won’t capture anything sent directly to the node if duplex=3, in my experience.
To get around that on a node that was configured this way, I set up a second private node on the same system with archiving, then connected the two.

3

Try adding a trailing “/” to the end of your archivedir entry. e.g.

archivedir = /var/log/asterisk/audio/

Make sure user “asterisk” owns or has write permission for that directory path. A new directory for your node number will be created under that path containing the audio files.

David McAnally
WD5M

1 Like
4

WD5M - followed your instructions. Rebooted server. It recreated "…/audio/62499/

Double checked permissions asterisk: asterisk

Same issue…

Thanks

5

Make sure you are using the latest revision of the software.

6

Latest and greatest version.

7

It’s been a longstanding issue for local audio. I haven’t heard anything that can fix it (yet), other than standing up a second node (even private, in the same hardware) and permalinking the two and archiving off of that node instead.

Carl/K6CRS

8

Trying to do that (2nd private node on same Pi) but not able to connect between private node and anything or the public node and the private.

See: Broadcastify limiting broadcast times - #14 by KC2NJV

Any ideas?

9

I did a workaround, suggested by someone that has my node traffic go through my private node. This seems to work.

10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.