Network Management

VNQM doesn't display data for PRI trunks on some or all VoIP Gateways

This article describes an issue when you don't see PRI trunks on some or all VoIP Gateways. There is no indication of what the issue is in regular logging. Enabling DEBUG logging for VNQM displays the following error: DEBUG SwTelnet9CommandProcessor - [41334] SWTelnet Command Complete. Output: [Name=cmd0,Command='terminal length 0'] Command authorization failed.

First published date

11/2/2018 12:21 PM

Last published date

5/2/2023 12:33 PM

Overview

This article describes an issue when you don't see PRI trunks on some or all VoIP Gateways.

There is no indication of what the issue is in regular logging. Enabling DEBUG logging for VNQM displays the following error:

DEBUG SwTelnet9CommandProcessor - [41334] SWTelnet Command Complete. Output: [Name=cmd0,Command='terminal length 0']
Command authorization failed.

Product section

VoIP & Network Quality Manager

Cause

You don't have the required permissions/access for logging in to the VoIP Gateway.

Resolution

Check the permissions on the VoIP Gateway to make sure the credentials used by VNQM have access to privileged EXEC mode.

This is a requirement for VNQM to poll the data.