[Home]

Summary:DAHLIN-00030: wct4xxp does not come up in rc3
Reporter:Dirk Nehring (dnehring)Labels:
Date Opened:2008-08-28 16:17:53Date Closed:2008-09-15 14:14:19
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:wct4xxp
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Dahdi-Linux 2.0.0-rc3, Asterisk 1.6.0-rc3 (tagged svn versions)

Hardware (with Hardware EC)
pci:0000:03:08.0     wct4xxp+     d161:0220 Wildcard TE220 (4th Gen)

Setup: both E1 port connected via crossover cable. This setup works with Asterisk 1.6.0beta9/zaptel 1.4.11, but not with dahdi 2.0.0-rc3/Asterisk 1.6.0-rc3. Problem:

sip*CLI> pri show spans
PRI span 1/0: Provisioned, Down, Active
PRI span 2/0: Provisioned, Down, Active

[Aug 28 16:22:54] NOTICE[9834] chan_dahdi.c: PRI got event: HDLC Abort (6) on Pr
imary D-channel of span 2

With zaptel:
sip*CLI> pri show spans
PRI span 1/0: Provisioned, Up, Active
PRI span 2/0: Provisioned, Up, Active




****** ADDITIONAL INFORMATION ******

/etc/dahdi/system.conf:
span=1,1,0,ccs,hdb3
bchan=1-15,17-31
dchan=16

span=2,2,0,ccs,hdb3
bchan=32-46,48-62
dchan=47

loadzone=de
defaultzone=de

/etc/asterisk/chan_dahdi.conf:

[...]
; Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4
group=1
context=pbx-in
switchtype = euroisdn
signalling = pri_cpe
channel => 1-15,17-31

; Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" HDB3/CCS/CRC4
group=2
context=pbx-transfer
switchtype = euroisdn
signalling = pri_net
channel => 32-46,48-62


Old configuration:

/etc/zaptel.conf

span=1,1,0,ccs,hdb3,crc4
bchan=1-15,17-31
dchan=16

span=2,2,0,ccs,hdb3,crc4
bchan=32-46,48-62
dchan=47

loadzone=de
defaultzone=de

/etc/asterisk/zapata.conf:
; Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4 ClockSource
group=1
context=pbx-in
switchtype = euroisdn
signalling = pri_cpe
channel => 1-15,17-31
context = default
group = 63

; Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" HDB3/CCS/CRC4
group=2
context=pbx-in
switchtype = euroisdn
signalling = pri_net
channel => 32-46,48-62
context = default
group = 63


Here the initialation log:

Aug 28 15:48:09 sip kernel: dahdi: Telephony Interface Registered on major 196
Aug 28 15:48:09 sip kernel: dahdi: Version: 2.0.0-rc3
Aug 28 15:48:09 sip kernel: Found TE2XXP at base address dffffc00, remapped to f8a1cc00
Aug 28 15:48:09 sip kernel: TE2XXP version c01a016a, burst ON
Aug 28 15:48:09 sip kernel: Octasic optimized!
Aug 28 15:48:09 sip kernel: FALC version: 00000005, Board ID: 00
Aug 28 15:48:09 sip kernel: Reg 0: 0x055fc400
Aug 28 15:48:09 sip kernel: Reg 1: 0x055fc000
Aug 28 15:48:09 sip kernel: Reg 2: 0xffffffff
Aug 28 15:48:09 sip kernel: Reg 3: 0x00000000
Aug 28 15:48:09 sip kernel: Reg 4: 0x00000101
Aug 28 15:48:09 sip kernel: Reg 5: 0x00000000
Aug 28 15:48:09 sip kernel: Reg 6: 0xc01a016a
Aug 28 15:48:09 sip kernel: Reg 7: 0x00001f00
Aug 28 15:48:09 sip kernel: Reg 8: 0x010200ff
Aug 28 15:48:09 sip kernel: Reg 9: 0x00fd0001
Aug 28 15:48:09 sip kernel: Reg 10: 0x0000004a
Aug 28 15:48:09 sip kernel: TE2XXP: Launching card: 0
Aug 28 15:48:09 sip kernel: TE2XXP: Setting up global serial parameters
Aug 28 15:48:09 sip kernel: dahdi: Registered Span 1 ('TE2/0/1') with 31 channels
Aug 28 15:48:09 sip kernel: dahdi: Span ('TE2/0/1') is new master
Aug 28 15:48:09 sip kernel: dahdi: Registered Span 2 ('TE2/0/2') with 31 channels
Aug 28 15:48:09 sip kernel: Found a Wildcard: Wildcard TE220 (4th Gen)
Aug 28 15:48:09 sip kernel: dahdi_transcode: Loaded.
Aug 28 15:48:12 sip kernel: About to enter spanconfig!
Aug 28 15:48:12 sip kernel: Done with spanconfig!
Aug 28 15:48:12 sip kernel: About to enter spanconfig!
Aug 28 15:48:12 sip kernel: Done with spanconfig!
Aug 28 15:48:12 sip kernel: dahdi: Registered tone zone 29 (Germany)
Aug 28 15:48:12 sip kernel: About to enter startup!
Aug 28 15:48:12 sip kernel: TE2XXP: Span 1 configured for CCS/HDB3/CRC4
Aug 28 15:48:12 sip kernel: wct2xxp: Setting yellow alarm on span 1
Aug 28 15:48:12 sip kernel: timing source auto card 0!
Aug 28 15:48:12 sip kernel: VPM400: Not Present
Aug 28 15:48:13 sip kernel: VPM450: echo cancellation for 64 channels
Aug 28 15:48:18 sip kernel: VPM450: hardware DTMF disabled.
Aug 28 15:48:18 sip kernel: VPM450: Present and operational servicing 2 span(s)
Aug 28 15:48:18 sip kernel: Completed startup!
Aug 28 15:48:18 sip kernel: About to enter startup!
Aug 28 15:48:18 sip kernel: TE2XXP: Span 2 configured for CCS/HDB3/CRC4
Aug 28 15:48:18 sip kernel: wct2xxp: Setting yellow alarm on span 2
Aug 28 15:48:18 sip kernel: Completed startup!
Aug 28 15:48:18 sip kernel: timing source auto card 0!
Aug 28 15:51:53 sip kernel: timing source auto card 0!
Aug 28 15:51:53 sip kernel: timing source auto card 0!
Aug 28 15:51:58 sip kernel: wct2xxp: Clearing yellow alarm on span 2
Aug 28 15:51:58 sip kernel: wct2xxp: Clearing yellow alarm on span 1
Comments:By: Leif Madsen (lmadsen) 2008-09-04 14:49:39

Can you reverse patch your version of DAHDI to see if this helps?

svn diff -c 4685 drivers/dahdi/wct4xxp/base.c > mypatch.diff
patch -R -p0 < mypatch.diff

Matt Fredrickson has been tracking down an issue in wct4xx for the last week, so this may or may not help.
By: Digium Subversion (svnbot) 2008-09-04 16:12:21

Repository: dahdi
Revision: 4861

U   linux/trunk/drivers/dahdi/wct4xxp/base.c

------------------------------------------------------------------------
r4861 | sruffell | 2008-09-04 16:12:20 -0500 (Thu, 04 Sep 2008) | 5 lines

Fixes an issue where the dual-span cards are not properly configured which can
cause data loss.

Fix provided by opticron and possibly related to issue ASTERISK-1330393.

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=4861
By: Dirk Nehring (dnehring) 2008-09-05 05:39:25

I just tried the patch (based on rc3). The pri status does not change, still only works with zaptel (currently 1.4.12).
By: Shaun Ruffell (sruffell) 2008-09-05 09:47:49

Would you try testing with the trunk of dahdi-linux?
By: Dirk Nehring (dnehring) 2008-09-07 13:55:23

Mmh, currently I have no spare card for doing intensive testing, it is now a productive system. But my problem is easy to reproduce: setting card to E1 mode and plug in a crossover cable.
By: Shaun Ruffell (sruffell) 2008-09-15 14:14:16

I believe this is fixed in revision 4861.  If you still have problems with it, please reopen this issue.