Re: [asterisk-users] pri CLI command not available
On Thu, Jan 21, 2010 at 05:12:32PM -0500, John Novack wrote: > In the "good old days" ( ZAPTEL ) Channel => had to be the last line in > a section. Everything after channel => was ignored. > > Seems that has not changed. > > A hard learned lesson by many ! This has not changed. However as of 1.6.1, a saner syntax is also supported (it is also supported in earlier versions, but only in users.conf) [some-section-name] dahdichan = 1-23 signalling = pri_cpe If you have 'dahdichan' in a certain section it is the same as if you have 'channel' in the end of it. Separate sections in dahdi_chan.conf (not only [channels]) are supported as of 1.6.1 . -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pri CLI command not available
In the "good old days" ( ZAPTEL ) Channel => had to be the last line in a section. Everything after channel => was ignored. Seems that has not changed. A hard learned lesson by many ! Eric Merkel (Mail Lists) wrote: > > Thanks you were exactly right. I had a problem in my chan_dadhi.conf > file. Basically, I had the channels defined before the signaling and > it wouldn’t load. It did not show any errors that I could see on > startup and there were no messages in the /var/log/asterisk/messages > but when doing a “load chan_dahdi.so” from the command line showed me > the problem. > > Thanks again! > > = > > Eric Merkel > > ejmerkel.li...@gmail.com > > *From:* asterisk-users-boun...@lists.digium.com > [mailto:asterisk-users-boun...@lists.digium.com] *On Behalf Of > *Anthony Francis - Handy Networks LLC > *Sent:* 2010-01-21 15:50 > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > *Subject:* Re: [asterisk-users] pri CLI command not available > > 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-boun...@lists.digium.com > [mailto:asterisk-users-boun...@lists.digium.com] *On Behalf Of *Eric > Merkel (Mail Lists) > *Sent:* Thursday, January 21, 2010 1:41 PM > *To:* asterisk-users@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.li...@gmail.com > > > > > > Checked by AVG - www.avg.com > Version: 9.0.730 / Virus Database: 271.1.1/2635 - Release Date: 01/20/10 > 14:18:00 > > -- Dog is my co-pilot -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pri CLI command not available
Thanks you were exactly right. I had a problem in my chan_dadhi.conf file. Basically, I had the channels defined before the signaling and it wouldn't load. It did not show any errors that I could see on startup and there were no messages in the /var/log/asterisk/messages but when doing a "load chan_dahdi.so" from the command line showed me the problem. Thanks again! = Eric Merkel ejmerkel.li...@gmail.com From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Anthony Francis - Handy Networks LLC Sent: 2010-01-21 15:50 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pri CLI command not available 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-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Eric Merkel (Mail Lists) Sent: Thursday, January 21, 2010 1:41 PM To: asterisk-users@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.li...@gmail.com -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pri CLI command not available
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-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Eric Merkel (Mail Lists) Sent: Thursday, January 21, 2010 1:41 PM To: asterisk-users@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.li...@gmail.com -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[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.li...@gmail.com -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
