[Asterisk-Users] Problem with T100P card in a new chassis

John Todd jtodd at loligo.com
Wed Oct 15 01:47:07 MST 2003


>Due to some failed hardware on another platform, I've had to move a 
>T100P card to a different chassis.  After this move was completed, I 
>am seeing some strange results on the T100P card that do not display 
>to me any failure mode with which I am familiar.  The card comes up, 
>and shows "good" carrier and status, but Asterisk refuses to bring 
>the D-channel up.  Calls of course do not complete, inbound or 
>outbound.  The configuration on the system is identical to what I 
>had on the same PRI before I disconnected it.  The PRI checks out 
>clean when connected to another Asterisk system.  So, it must be 
>something with this particular motherboard or hardware 
>configuration, but is there anything I can do to solve the problem?
>
>Searches through the archives and Google do not show anything 
>relevant on this error message that I was able to find.
>
>Hardware Specs:
>  - Intel 440GX+ motherboard
>  - 500mhz PIII processor
>  - 1u case (horizontal PCI card - no, it's not shorting out)
>
>If I run asterisk -vvvvvvvvgcd I get a whole slew of these lines 
>(all identical) in the stderr output:
>
>DEBUG[13326]: File chan_zap.c, Line 6201 (pri_dchannel): Got event 
>No event (0) on D-channel for span 1
>
>From dmesg:
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users

Well, that was interesting.  I suppose I won't put "." characters on 
a line by themselves any more, since that is the SMTP "end of file" 
character.  I've never seen that actually chop up a message, though...

Here is the same transmission content, slightly altered:


Due to some failed hardware on another platform, I've had to move a 
T100P card to a different chassis.  After this move was completed, I 
am seeing some strange results on the T100P card that do not display 
to me any failure mode with which I am familiar.  The card comes up, 
and shows "good" carrier and status, but Asterisk refuses to bring 
the D-channel up.  Calls of course do not complete, inbound or 
outbound.  The configuration on the system is identical to what I had 
on the same PRI before I disconnected it.  The PRI checks out clean 
when connected to another Asterisk system.  So, it must be something 
with this particular motherboard or hardware configuration, but is 
there anything I can do to solve the problem?

Searches through the archives and Google do not show anything 
relevant on this error message that I was able to find.

Hardware Specs:
  - Intel 440GX+ motherboard
  - 500mhz PIII processor
  - 1u case (horizontal PCI card - no, it's not shorting out)

If I run asterisk -vvvvvvvvgcd I get a whole slew of these lines (all 
identical) in the stderr output:

DEBUG[13326]: File chan_zap.c, Line 6201 (pri_dchannel): Got event No 
event (0) on D-channel for span 1

 From dmesg:
...
Zapata Telephony Interface Registered on major 196
PCI: Assigned IRQ 5 for device 00:0b.0
Framer: DS21552, Revision: 3 (T1)
Found a Wildcard: Digium Wildcard T100P T1/PRI
Registered tone zone 0 (United States / North America)
Using ESF/B8ZS coding/framing
Calling startup (flags is 4099)
Using ESF/B8ZS coding/framing
Calling startup (flags is 4099)
Registered tone zone 0 (United States / North America)
...

[root at gw3 asterisk]# grep -v "#" /etc/zaptel.conf|uniq
loadzone = us
defaultzone=us
span=1,1,0,esf,b8zs
bchan=1-23
dchan=24

[root at gw3 asterisk]# grep -v ";" /etc/asterisk/zapata.conf
[channels]
signalling=pri_cpe
switchtype=national
pridialplan=unknown
group=1
usercallerid=yes
echocancel=yes
echocancelwhenbridged=yes
context=pri-inbound
channel => 1-23

[root at gw3 asterisk]# more /proc/interrupts
            CPU0      
   0:    8800665          XT-PIC  timer
   1:       4944          XT-PIC  keyboard
   2:          0          XT-PIC  cascade
   5:          0          XT-PIC  t1xxp
   8:          1          XT-PIC  rtc
  10:     226264          XT-PIC  usb-uhci, eth0
  12:       3230          XT-PIC  PS/2 Mouse
  14:      81878          XT-PIC  ide0
NMI:          0
ERR:          0

[root at gw3 asterisk]# ztcfg -vvvvvv

Zaptel Configuration
======================

SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Individual Clear channel (Default) (Slaves: 01)
Channel 02: Individual Clear channel (Default) (Slaves: 02)
Channel 03: Individual Clear channel (Default) (Slaves: 03)
Channel 04: Individual Clear channel (Default) (Slaves: 04)
Channel 05: Individual Clear channel (Default) (Slaves: 05)
Channel 06: Individual Clear channel (Default) (Slaves: 06)
Channel 07: Individual Clear channel (Default) (Slaves: 07)
Channel 08: Individual Clear channel (Default) (Slaves: 08)
Channel 09: Individual Clear channel (Default) (Slaves: 09)
Channel 10: Individual Clear channel (Default) (Slaves: 10)
Channel 11: Individual Clear channel (Default) (Slaves: 11)
Channel 12: Individual Clear channel (Default) (Slaves: 12)
Channel 13: Individual Clear channel (Default) (Slaves: 13)
Channel 14: Individual Clear channel (Default) (Slaves: 14)
Channel 15: Individual Clear channel (Default) (Slaves: 15)
Channel 16: Individual Clear channel (Default) (Slaves: 16)
Channel 17: Individual Clear channel (Default) (Slaves: 17)
Channel 18: Individual Clear channel (Default) (Slaves: 18)
Channel 19: Individual Clear channel (Default) (Slaves: 19)
Channel 20: Individual Clear channel (Default) (Slaves: 20)
Channel 21: Individual Clear channel (Default) (Slaves: 21)
Channel 22: Individual Clear channel (Default) (Slaves: 22)
Channel 23: Individual Clear channel (Default) (Slaves: 23)
Channel 24: HDLC with FCS check (Default) (Slaves: 24)

24 channels configured.

[root at gw3 asterisk]#


zttool shows "no alarms" but "internally clocked" despite my 
configuration to take timing from the external loop. Trying to loop 
up the T1 from zttool results in the "Looping UP span 1..." message 
to simply hang on the screen, and I have to kill the process manually.

Suggestions are welcome.

JT



More information about the asterisk-users mailing list