asterisk users - Feb 2006 - problem with outgoing calls Unable tocreatechannel of type 'ZAP' (cause 34 - Circuit/channel congestion)

When Asterisk first starts up, it will attempt to "bring up" the B
channels on any PRI circuits.  If you are using A@H then you can log on
to the Asterisk CLI (asterisk -r) and then do "stop now" to stop
asterisk.  Start up Asterisk again by typing asterisk -cvvv at the Linux
command line.  You should see a bunch of messages on the terminal and
then you'll get the Asterisk CLI prompt.  A few moments later you should
see some more messages saying something like "B channel 1/1 successfully
started on span 0" and then "B channel 1/2 successfully
started..."  I
don't have my system active at the moment but when I do I'll email you a
screen capture of the messages I see on my PRI.

-MC

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of nik600
Sent: Monday, February 13, 2006 6:02 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] problem with outgoing calls Unable
tocreatechannel of type 'ZAP' (cause 34 - Circuit/channel congestion)

On 2/13/06, Michael Collins <mcollins@fcnetwork.biz>
wrote:
> Nik,
>
> Just curious - what is your telco setup?  Do you have PRI with the
> specified D channels?  You need to make sure that your telco is set up
> to have the D channels on 16 and 47.  When you first start Asterisk,
or
> when you log on to the CLI, do you ever see messages stating the B
> channels are successfully started?
>
sorry, i don't uderstand the question....

do you ever see messages stating the B channels are successfully
started?

how can i check this?

thanks
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

On 2/13/06, Michael Collins <mcollins@fcnetwork.biz>
wrote:
> When Asterisk first starts up, it will attempt to "bring up" the
B
> channels on any PRI circuits.  If you are using A@H then you can log on
> to the Asterisk CLI (asterisk -r) and then do "stop now" to stop
> asterisk.  Start up Asterisk again by typing asterisk -cvvv at the Linux
> command line.  You should see a bunch of messages on the terminal and
> then you'll get the Asterisk CLI prompt.  A few moments later you
should
> see some more messages saying something like "B channel 1/1
successfully
> started on span 0" and then "B channel 1/2 successfully
started..."  I
> don't have my system active at the moment but when I do I'll email
you a
> screen capture of the messages I see on my PRI.
>
i get:
*CLI>   == Primary D-Channel on span 1 up

at the moment i've got only one span connected...il the message correct?