asterisk users - Dec 2004 - Verizon PRI Setup Problems - Only Busy and Congestion

Hi -

We're moving up in the world to a PRI (Verizon), and I'm having some 
problems with it.  I'm new to this PRI thing, though, so maybe I've 
just screwed up a simple config detail.  I've got a TE410P on a Dell 
PE1600SC (ServerWorks Chipset).  The card itself has a green light for 
the PRI, and Zttool shows Span1 as "OK".  All I'm getting when I
call
into any of the pri lines, though, is a slow busy.  I can't see 
anything from the asterisk end - it looks as though I'm not calling.  
When I call out, I just get a fast busy congestion tone, and asterisk 
says all the channels are busy:

*CLI> pri debug span 1
Enabled debugging on span 1
     -- Executing Dial("SIP/2000-28df", "Zap/2/19142246402")
in new stack
Dec 14 21:01:52 NOTICE[1437]: app_dial.c:800 dial_exec: Unable to 
create channel of type 'Zap' (cause 0)
   == Everyone is busy/congested at this time
     -- Executing Congestion("SIP/2000-28df", "") in new
stack
   == Spawn extension (from-sip, 19142246402, 2) exited non-zero on 
'SIP/2000-28df'

Here are my configs for the TE410P:
zaptel.conf:
span=1,1,0,esf,b8zs
bchan=1-23
dchan=24

zapata.conf:
switchtype = national
context = incoming
signalling = pri_cpe
group = 1
channel => 1-23

Have I screwed up the config, or do I need to bug Verizon?

Thanks,
Noah

Noah Miller wrote:
> Here are my configs for the TE410P:
> zaptel.conf:
> span=1,1,0,esf,b8zs
Well, you say you have a green light, but this should be:

span=1,0,0,esf,b8zs

because you want your card to derive the clock from the Verizon-supplied 
end of the circuit.
> bchan=1-23
> dchan=24
> 
> zapata.conf:
> switchtype = national
> context = incoming
> signalling = pri_cpe
> group = 1
> channel => 1-23
This all looks reasonable at first glance. Do you know for sure that 
Verizon has configured your PRI for NI-2 signaling? What does "pri show 
span" say on your Asterisk console?

>> Slow busy tells me that the telco has busied all his channels out -- 
>> likely
>> waiting for a call from him to finish provisioning... Unless his 
>> dialplan has
>> _.,1,Busy or something.  :-)
>
> His "pri show span" said "Down", that's likely the
cause.
I guess I'll have to get Verizon on the case.  Thanks for all the help!