[Asterisk-Users] problem with outgoingcallsUnabletocreatechannelof type 'ZAP' (cause 34 -Circuit/channelcongestion)

[Michael Collins]

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of nik600
Sent: Saturday, February 18, 2006 2:00 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] problem with
outgoingcallsUnabletocreatechannelof type 'ZAP' (cause 34
-Circuit/channelcongestion)

On 2/17/06, Michael Collins <mcollins at fcnetwork.biz> wrote:
> Nik,
>
> This definitely helps!  Please check your dial command. You've got
> "Dial(Zap/0/mynumber)" and I think you might possibly want it to be
> something like this:
> Dial(Zap/1/mynumber)   or
> Dial(Zap/g0/mynumber)
>
> I don't recall there being a zap channel zero, but it is common to
have
> a group zero.  I would recommend trying Zap channel 1 -
> Dial(Zap/1/mynumber) - before trying the group.  Again, please get the
> debug info.  The "CHANUNAVAIL" message made it easier to diagnose this
> issue.
>
> Don't give up!  The education you are getting will help you in the
long
> run and in a few months you'll be able to help a * newbie with the
same
> issues!
>
> -MC
>

ok, thanks for your help, please, be patient because now i've got many
logs to post ... :-)

so, i've made this new entry in extension.conf:

exten => 444,1,Dial(Zap/0/0465670127)
exten => 445,1,Dial(Zap/g0/0465670127)
exten => 446,1,Dial(Zap/1/0465670127)
exten => 447,1,Dial(Zap/g1/0465670127)


and i've reloaded asterisk with:

asterisk -r
>reload
>quit

and then:

 tail -f /var/log/asterisk/full



I CALL 445 or 446:
<snip>
Feb 18 04:53:20 VERBOSE[3608] logger.c: < Cause (len= 5) [ Ext: 1 
Coding: CCITT (ITU) standard (0) 0: 0   Location: Public network s
erving the local user (2)
Feb 18 04:53:20 VERBOSE[3608] logger.c: <                  Ext: 1 
Cause: Unknown (99), class = Protocol Error (6) ]
</snip>

now i'll read and search on the network about all this warnings and
error and verbose report, but i hope that your experience will found
where is the problem...thanks



Nik,

It looks like your exten 445 and exten 446 are communicating on the
D-channel!  Again, that's progress.  It looks like there is a protocol
error (see snipped portion of log) when dialing out.  I can't quite
figure out what the source of that protocol error is.  However, at this
point it would be good to review what ISDN settings your telephone
carrier is providing.  Specifically, can they tell you which protocol
(sometimes we yanks will call it a "protocol variant") they are using?
If they are set for NI2 or "National" then perhaps there's something
going on within their equipment.  Hard to say without doing some
testing.  I've had some strange occurrences with my telephone carriers
here in California.  For example, I had the telco set their equipment to
"4ess" and I set mine to the same - it would NOT work, no matter what.
I had them leave theirs on "4ess" and I set mine to "5ess" and it worked
perfectly!  Go figure.  

Are you in a position to have one of the carrier's engineers do some
debugging?  You can call them and let them know that you are making test
calls but your equipment is showing protocol errors.  They should be
able to do a trace on the D-channel on their end.  Hopefully you'll get
an engineer who knows Q.931.  (I've had technicians who couldn't even
spell P-R-I and I've had to escalate the phone call to their respective
supervisors!)

There are several debugging options right now, but I wouldn't continue
without getting your carrier involved.  They may look at the D-Channel
messages and make an adjustment on their end, or they might suggest
changing protocols, at least for testing.  Don't worry - if this is your
first foray into the wacky world of PRI then you're just getting the
obligatory baptism by fire.  I've set up dozens of PRI's here in the
states and at first it always took hours, even for an experienced PBX
technician.  But now that I've been through the wringer I know which
questions to ask and what tinkering to do.  Please don't give up - PRI
is pretty nice once you getting it working.

If you have any questions about talking to your carrier, please contact
me offline.  I'll be happy to help!

-MC