[Asterisk-Users] E100P errors with PRI D-channel problem

M.A. Ali
2003-12-19T09:42:47Z

Hi All,
I need help configuring my E100P digium card. I am testing it with a
marconi&nbsp;digital transmission analyzer. Although everything configures
fine. All channels get configured and the output of cat /proc/zaptel/1 verifies
that.
problems;
1. i dont know how to use the zttool for debugging purpose or any other
available such tool
2. The D-channel of the PRI is shown down by asterisk whenever i try to
make a call. the outpur follows:
*CLI> dial 9011@itedc
-- Executing Playback("OSS/dsp", "beep") in new
stack
<< Console call has been answered >>
-- Playing 'beep' (language 'en')
-- Executing Dial("OSS/dsp", "zap/g2/011") in new
stack
-- Called g2/011
== D-Channel on span 1 down
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
== D-Channel on span 1 down
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
WARNING[1265627968]: File app_dial.c, Line 318 (wait_for_answer):
Unable to forward voice
-- Hungup 'Zap/17-1'
== No one is available to answer at this time
-- Executing Congestion("OSS/dsp", "") in new
stack
and the call is disconnected......... but this is not always
the case.....when i tried it again it showed ans output like
this.....;
*CLI> pri debug span 1
Enabled debugging on span 1
*CLI> dial 91123@itedc
-- Executing Playback("OSS/dsp", "beep") in new
stack
<< Console call has been answered >>
-- Playing 'beep' (language 'en')
-- Executing Dial("OSS/dsp", "zap/g2/1123") in new
stack
NOTICE[1265627968]: File app_dial.c, Line 516 (dial_exec): Unable to
create channel of type 'zap' == Everyone is busy at this time
-- Executing Congestion("OSS/dsp", "") in new
stack

WARNING[1192437440]: File chan_zap.c, Line 5581 (zt_pri_error): PRI:
Read on 49 failed: Unknown error 500
PRI got event: 8
WARNING[1192437440]: File chan_zap.c, Line 5581 (zt_pri_error): PRI:
Read on 49 failed: Unknown error 500
PRI got event: 6

getting same behaviour when calling from SIP phones....I am getting
suspicious behaviour by the "pri debug span 1" command....sometimes it
shows the complete...but sometimes it just doesn't tell
anything....
one thing is for sure.......the D-channel is not working.....because i
cant dial asterisk from the analyzer or the other way....... the line has simply
no errors....evrything perfect.
<SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New" size=2># Zaptel Configuration
File #
<SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New
Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language:
EN-US; mso-fareast-language: EN-US; mso-bidi-language:
AR-SA">span=1,2,0,ccs,hdb3 <SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';
mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US;
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
<SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New"
size=2>bchan=1-15 dchan=16 bchan=17-31 <SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New" size=2>
<SPAN
style="mso-fareast-font-family: 'MS Mincho'">loadzone =
us defaultzone=us <SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New" size=2>
<SPAN
style="mso-fareast-font-family: 'MS
Mincho'">
<SPAN
style="mso-fareast-font-family: 'MS
Mincho'">
<SPAN
style="mso-fareast-font-family: 'MS Mincho'">; Zapata
telephony interface ; ; Configuration
file ; [channels] ; language=en
<SPAN
style="mso-fareast-font-family: 'MS
Mincho'">context=itedc
<SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New"
size=2>immediate=yes
<SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New"
size=2>musiconhold=default <SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New" size=2><SPAN
style="mso-fareast-font-family: 'MS Mincho'">
<SPAN
style="mso-fareast-font-family: 'MS
Mincho'">echocancel=no
<SPAN
style="mso-fareast-font-family: 'MS
Mincho'">relaxdtmf=no <SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New"
size=2>jitterbuffers=8 <SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT
face="Courier New"
size=2>switchtype=euroisdn pridialplan=unknown signalling=pri_cpe group=1 channel=>1,2-15 group=2 channel=>17-21,22-31
<P class=MsoPlainText style="MARGIN: 0in 0in
0pt">
I need help on this.....anybody having similar problem......or the
manufacturers regards,
M.A Ali Janjua
MSN 8
helps ELIMINATE
E-MAIL VIRUSES. Get 2 months FREE*.