It was defined as a friend on the remote end. I tried adding the same entry to my iax.conf verbatim and trying the call again, still providing it in the dial string though Asterisk usually seems to detect if that corresponds to something in iax.conf or sip.conf, even if I don’t want it too.
[Jan 25 11:43:43] -- Called IAX2/redacted
[Jan 25 11:43:47] -- IAX2/redacted-2007 is circuit-busy
[Jan 25 11:43:47] -- Hungup 'IAX2/redacted-2007'
It doesn’t work even with the entry locally defined if I dial it normally, but when I try it with just the local IAX2 section/user name for it, which has the remote host defined as well, it works, although on the remote end’s CLI, it still says Accepting UNAUTHENTICATED call. Not sure if it’s supposed to say “Accepting authenticated call” or something of that sort, but I do set those encryption settings on the channel and the call goes through, so it does work.
Unfortunately, there are 130 remote peers and defining them all in iax.conf and updating constantly would be utterly impractical, not to say anything of the other 130 nodes, so I guess I will have to give up on it for now, unless there is a way to do this dynamically in the dialplan without modifying iax.conf on the calling side (obviously, it would be expected that the secret is defined on the remote side). I can get the secret through a lookup, and I’m not really sure what difference it makes if it’s defined locally or not, so this seems like an oversight to me. If it’s not by design, maybe a possible feature request I guess.
Maybe off topic, but is IAX2 no longer “the thing” like it used to be? I’m a huge fan of IAX2 for several reasons but it seems like outside of a few niche communities, the protocol isn’t very well liked/used for whatever reason. Just curious. As long as it doesn’t get removed in a later release though I guess it shouldn’t matter much.