[asterisk-users] pri CLI command not available

[Anthony Francis - Handy Networks LLC]

This is often caused by the dahdi module not loading, check /var/log/asterisk/messages for the reason, or better yet, from the cli load the module manually and see the error in real time. If I had to guess I would say it is a configuration error.

Thank you and have a  nice day,
Anthony Francis

From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Eric Merkel (Mail Lists)
Sent: Thursday, January 21, 2010 1:41 PM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] pri CLI command not available

I am in the process of trying to terminate a PRI into a new * server. The server has an old T100P T1/PRI card in it. I have compiled the following on Centos 5.4.

dahdi-linux-complete-2.2.1+2.2.1
libpri-1.4.10.2
asterisk-1.4.29

Everything seems to have compiled fine. DAHDI reports "Found a Wildcard: Digium Wildcard T100P T1/PRI" on bootup. Dahdi_tool shows that the span is up and active with no alarms however the phone company is not seeing the trunkgroup going into service. I was wanting to take a look at the PRI debugs but for some reason the CLI "pri" option is not available. I libpri compiled without any issues prior to compiling asterisk. What would cause the "pri debug" commands to not be available in the CLI?


=====
Eric Merkel
ejmerkel.lists at gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100121/336daec3/attachment.htm