[Asterisk-Dev] libpri: mgt controls

Mike M no-linux-support at earthlink.net
Sat Jun 11 17:43:52 MST 2005

On Sat, Jun 11, 2005 at 06:36:21PM -0400, C. Maj wrote:
> On Fri, 10 Jun 2005, Mike M waxed:
> > On Fri, Jun 10, 2005 at 03:19:19PM -0400, izo wrote:
> > > > Is it true that Asterisk PRI D channels always try to be "up" and there
> > > > are no user level controls to disable/enable it?
> > >
> > > AFAIK you can disable channels by not including them in
> > > /etc/zaptel.conf and /etc/asterisk/zapata.conf but to make changes
> > > you'd have to restart application which in that case means that if you
> > > had other PRI's that were up they'll go down.
> >
> > I was looking for controls to change the D channel state under user
> > control while Asterisk is running.  I was curious because I wanted to
> > see how they worked in the code if they existed.  I think you're indirectly
> > telling such controls don't exist.
> You'd need to hack a CLI control into chan_zap and let it
> call stuff in libpri.  Some masking of the propagated
> d-channel down events from libpri to chan_zap would be
> needed, otherwise, * will try to get it up for you.

I think Asterisk is fine as written.  I just didn't want to miss reading
the functions if they existed.  That last clue is interesting.
> > I'm going to trying patching q931.c to display contents of the "struct pri"
> > objects so I can watch them change as they go through their lifecycle.
> > I only have one PRI right now so I guess that I would have a single
> > "struct pri" object.
> There's also "pri debug" and "pri intense debug" CLI
> commands to log d-channel activity.

I've used those.  They may do everthing I need, and if not, then I
should extend them.  Thanks.  I might have reinvented something without
your reminder.

More information about the asterisk-dev mailing list