IRLP Error Codes

What do the Different Error Messages Actually Mean?

IRLP - Keeping the Radio in Amateur Radio

 The IRLP system has an elaborate system of error reporting. There are several error codes that help you troubleshoot problems with the node. Each error code signifies a different problem.

 The most common ones occur during calls to other nodes, conversations, and disconnecting.

 These will show up in your log files when the error is played over the air.


This error is caused by a call to a node which does not exist in the list of valid nodes. This list is always changing. For example, a DTMF sequence of 2987 will cause this error, because station 2987 does not exist (yet).

 This error can be silenced by changing the NOEXIST_INFORM directive in the environment file to NO.


The busy error is caused when the node you call is currently connected to another IRLP node. Your node will identify the node the called node is connected to.


This is returned as “the node you are calling is being used locally”. This means the COS was active on the node you called, when you tried to make the call.


This returns “the node you called is currently disabled”. This means that the remote node owner has disabled the node for some reason.


This returns “the node you called is not responding”. This means the timeout of 5 seconds for a node to respond to a call has elapsed.


This returns “The call could not be authenticated”. This occurs when there is an error in the PGP authentication process. This is often caused by bad PGP keys between the calling or called node.


This returns “Your security file is being updated, please try your call again later”. This occurs when the node you called has a valid IP on the server, but no valid PGP key in your keyring. Your system goes out to try to pull the latest keyring to verify the key. You must try the call again.


This returns “The node you are calling does not accept calls from your node”. This occurs if your node is added to a remote node (or reflectors) lockout list.


This returns “PTT Lockup detect” and resets your node PTT if it is continually keyed for 5 minutes with no breaks.


This returns “COS Lockup detect” and resets your node, and drops the current connection if COS is on for 4 minutes continuously.

INVALID_PGP (siggen)

This returns “Your PGP key is invalid. If this error persists, please contact”. This occurs when you have performed an install and your node has not yet been validated in the keyring.

 There are several codes that may ask the operator to contact the node owner. They are as follows:

01 Improper syntax for computer call. This indicates a software problem.
17 Invalid IP warning. This indicates the IP received from the connecting host is invalid, and is most likely "spoofed".
20, 21, 22,
23, 24
Failed to read from or write to temporary authentication files. This indicates a permissions problem in the /home/irlp/run directory.
25 PGP authentication error.  New nodes may experience this until PGP key is added to keyring.  Also can occur if you make any change to the 'export STATIONID=stnxxxx' line in your environment file.
30, 31, 32,
33, 34, 35, 36
Failed to read computer variables, such as the clock. This is caused by invalid file permissions, or possibly by hardware failure.
40 Failed to open/close audio device for read/write. This is caused by incorrect file permissions on the audio devices (/dev/audio*, /dev/dsp*, /dev/mixer*)
80 Failed to properly link between nodes to send authentication data.
99 Catch-all for undocumented errors that can occur in IRLP software. If you receive a continuous error 99, consult your log file, and contact for assistance


 Please email us at


Enjoy IRLP and please "Pass the Word"
If left menu bar is not visible, click here

last updated July 03, 2003
© 2003 IRLP.NET    
Privacy Policy

Print this Page