[asterisk-users] Zap PRI failed with Cause 34 - Where to check for problems?

[bruce bruce]

I have already done an "amportal restart" which restarted Asterisk and
everything works fine now.

Here is the output of "pri show span 1":

Primary D-channel: 24
Status: Provisioned, Up, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 1
Retrans: 0
Busy: 0
Overlap Dial: 0
Logical Channel Mapping: 0
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3


thanks,
Bruce

On Mon, Apr 19, 2010 at 3:00 PM, Doug Lytle <support at drdos.info> wrote:

> bruce bruce wrote:
> >
> > [2010-04-19 08:45:50] WARNING[29707] app_dial.c: Unable to create
> > channel of type 'ZAP' (cause 34 - Circuit/channel congestion)
> >
> >
> > Where can I look to debug the problem?
> >
>
> What does the:
>
> pri show span 1
>
> Output look like?
>
> Doug
>
> --
>
> Ben Franklin quote:
>
> "Those who would give up Essential Liberty to purchase a little Temporary
> Safety, deserve neither Liberty nor Safety."
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100419/d3fcf010/attachment.htm