---
title: "Natalia On-Premise PBX Error Codes | 5 Wizard Codes - Natalia"
description: "The 5 PBX connection test codes of Natalia On-Premise: AUTH_FAILED, HOST_UNREACHABLE, SSH_HOST_KEY, CDR_PATH_NOT_FOUND, TLS_INVALID."
url: https://getnatalia.com/en/documentation/natalia-analytics-on-premise/error-codes
lang: en
---

[Home](https://getnatalia.com/en/) / [Documentation](https://getnatalia.com/en/documentation) / [On-Premise](https://getnatalia.com/en/documentation/natalia-analytics-on-premise) / Error codes

# PBX connection error codes

The five codes returned by the "Test the connection" button of the appliance wizard. Each code: meaning, causes, resolution.

## Summary

| Code | Meaning |
| --- | --- |
| [AUTH\_FAILED](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/error-codes#auth) | The PBX refused the login, or the account cannot read the ticket files. |
| [HOST\_UNREACHABLE](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/error-codes#network) | The appliance could not reach the PBX within 10 seconds. |
| [SSH\_HOST\_KEY](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/error-codes#hostkey) | The OXE presents an SSH key different from the one pinned at the first connection. Collection of this site stops. |
| [CDR\_PATH\_NOT\_FOUND](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/error-codes#cdr-path) | The ticket folder does not exist on the PBX. |
| [TLS\_INVALID](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/error-codes#tls) | The connection test failed on a certificate error. |

## AUTH\_FAILED

The PBX refused the login, or the account cannot read the ticket files.

Causes

Wrong password. OXE: account other than `mtcl` without read right on `/usr4/account`. OXO: wrong `ftp_nmc` password.

Resolution

Retype the credentials. OXE: grant read access to the folder ([step 2](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/oxe-configuration)). OXO: ask your Alcatel-Lucent integrator for the `ftp_nmc` password.

## HOST\_UNREACHABLE

The appliance could not reach the PBX within 10 seconds.

Causes

Empty or wrong IP, port filtered by a firewall, SSH disabled on the OXE, FTP passive data ports blocked on the OXO. Also returned when the failure matches no other code.

Resolution

From the appliance network, test the port: `nc -v <PBX-IP> 22` (OXE) or `30021` (OXO). Open the flow from the appliance to the PBX.

## SSH\_HOST\_KEY

The OXE presents an SSH key different from the one pinned at the first connection. Collection of this site stops.

Causes

OXE reinstalled, CPU replaced, key renewed, or a third-party machine answering on the PBX address.

Resolution

Confirm the change with your telephony team. If it is legitimate, click "Re-approve the PBX key" on the "PBX SSH key changed" card of the dashboard. The re-approval is recorded in the audit log.

## CDR\_PATH\_NOT\_FOUND

The ticket folder does not exist on the PBX.

Causes

OXE: Taxation over IP license inactive, so `/usr4/account` is missing, or non-standard path on a virtualized OXE. OXO: custom CDR path entered by mistake.

Resolution

OXE: check the license ([step 1](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/oxe-configuration#taxation)) and locate the folder with `find /usr -name "TAXA*"`. OXO: empty the CDR path field.

## TLS\_INVALID

The connection test failed on a certificate error.

Causes

Most often, an HTTPS port (443, 30443) entered instead of the collection port.

Resolution

Collection does not use TLS: enter port 22 (OXE) or 30021 (OXO). See [OXO configuration](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/oxo-configuration).

Test OK but no ticket collected, or raw SSH messages: see [troubleshooting](https://getnatalia.com/en/documentation/natalia-analytics-on-premise/troubleshooting).

Last updated : October 5, 2026

[Suggest an edit](mailto:doc@getnatalia.com?subject=Doc%20edit%3A%20natalia-analytics-on-premise%2Ferror-codes)