Transceive generates 'WARNING[485] app_rpt.c: Unable to parse link string !IAXKEY! 1 1 0 0' notices

Transceive
1

Hi folks,

Happy transcieve 1.3.0 (3) user, but I notice I’m seeing the following in the logs when connecting to my node:

[2025-07-28 19:28:44.302] WARNING[485] app_rpt.c: Unable to parse link string !IAXKEY! 1 1 0 0
[2025-07-28 19:53:55.120] WARNING[485] app_rpt.c: Unable to parse link string !IAXKEY! 1 1 0 0

which looks like it could be caused by app_rpt: Remove iaxkey and associated logic by mkmer · Pull Request #588 · AllStarLink/app_rpt · GitHub. ASL have reverted some of this (see app_rpt: ignore !IAXKEY! message (#716) · AllStarLink/app_rpt@55d529e · GitHub ) but can whatever part of transcieve’s generating the IAXKEY stuff be updated to match current ASL3 codebase?

(or documented so I can at least work out where the message is coming from)

Many thanks

Andrew

root@allstar:/etc/asterisk# asl-show-version
********** AllStarLink [ASL] Version Info **********

OS            : Debian GNU/Linux 12 (bookworm)
OS Kernel     : 6.1.0-37-cloud-amd64

Asterisk      : 22.4.1+asl3-3.5.4-1.deb12
ASL [app_rpt] : 3.5.4

Installed ASL packages :

  Package                         Version
  ==============================  ==============================
  asl3                            3.8-1.deb
  asl3-asterisk                   2:22.4.1+asl3-3.5.4-1.deb12
  asl3-asterisk-config            2:22.4.1+asl3-3.5.4-1.deb12
  asl3-asterisk-modules           2:22.4.1+asl3-3.5.4-1.deb12
  asl3-menu                       1.14-1.deb12
  dahdi                           1:3.1.0-2
  dahdi-dkms                      1:3.4.0-6+asl
  dahdi-linux                     1:3.4.0-6+asl
root@allstar:/etc/asterisk#
2

Ah yes, the infamous !IAXKEY! message. No idea what it’s for or what it does. Nobody could ever provide an answer back when Transceive was first built. I tried to document it here for posterity, but it was always a bit of a black box:

https://wiki.allstarlink.org/wiki/IAX_Text_Protocol

I’ll mark that for removal in the next release. Appreciate you including the links to the relevant ASL commits. That helps confirm it’s safe to deprecate now. Thanks!

3

I’ll mark that for removal in the next release.

I upgraded my ASL instance to the 3.5.5 beta and it’s successfully suppressed the warning from the logs.

So assuming everyone (ha!) patches ASL when it’s released to stable they’ll never notice.

Andrew

1 Like