thr3ads.net - asterisk users - [Asterisk-Users] Sangoma A104

If this information is useful, please help other people find it:
Share via:

Kumak

2005-Feb-17 08:07 UTC

[Asterisk-Users] Sangoma A104 - D-Channel problem

Hello,
I have following problem with Sangoma A104 card:

CLI> pri show span 1
Primary D-channel: 16
Status: Provisioned, Down, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T313 Timer: 4000
N200 Counter: 3

NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6) on
Primary D-channel of span 1
NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6) on
Primary D-channel of span 1
NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6) on
Primary D-channel of span 1
NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6) on
Primary D-channel of span 1

Any idea how to fix it?

My configs:

zaptel.conf:

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

zapata.conf

[channels]
switchtype=euroisdn
pridialplan=unknown
overlapdial=no
usecallerid=yes
hidecallerid=yes
callwaiting=no
callwaitingcallerid=no
threewaycalling=no
transfer=no
cancallforward=no
callreturn=no
jitterbuffers=4
echocancel=yes
echocancelwhenbridged=no
echotraining=yes
relaxdtmf=yes
rxgain=0.5
txgain=0.9
immediate=no
amaflags=billing
adsi=no
busydetect=no
callprogress=no
context = zapline1
switchtype = euroisdn
group=1
signalling = pri_cpe
channel => 1-15
channel => 17-31

cat /proc/zaptel/1 :

Span 1: WPE1/0 "wanpipe1 card 0" HDB3//CRC4

           1 WPE1/0/1 Clear (In use)
           2 WPE1/0/2 Clear (In use)
           3 WPE1/0/3 Clear (In use)
           4 WPE1/0/4 Clear (In use)
           5 WPE1/0/5 Clear (In use)
           6 WPE1/0/6 Clear (In use)
           7 WPE1/0/7 Clear (In use)
           8 WPE1/0/8 Clear (In use)
           9 WPE1/0/9 Clear (In use)
          10 WPE1/0/10 Clear (In use)
          11 WPE1/0/11 Clear (In use)
          12 WPE1/0/12 Clear (In use)
          13 WPE1/0/13 Clear (In use)
          14 WPE1/0/14 Clear (In use)
          15 WPE1/0/15 Clear (In use)
          16 WPE1/0/16 HDLCFCS (In use)
          17 WPE1/0/17 Clear (In use)
          18 WPE1/0/18 Clear (In use)
          19 WPE1/0/19 Clear (In use)
          20 WPE1/0/20 Clear (In use)
          21 WPE1/0/21 Clear (In use)
          22 WPE1/0/22 Clear (In use)
          23 WPE1/0/23 Clear (In use)
          24 WPE1/0/24 Clear (In use)
          25 WPE1/0/25 Clear (In use)
          26 WPE1/0/26 Clear (In use)
          27 WPE1/0/27 Clear (In use)
          28 WPE1/0/28 Clear (In use)
          29 WPE1/0/29 Clear (In use)
          30 WPE1/0/30 Clear (In use)
          31 WPE1/0/31 Clear (In use)


Information from dmesg:

Processing WAN device wanpipe1...
wanpipe1: Locating: A104 card, CPU A, PciSlot=8, PciBus=0
wanpipe1: Found: A104 card, CPU A, PciSlot=8, PciBus=0, Port=0
PCI: Found IRQ 10 for device 00:08.0
wanpipe1: AFT PCI memory at 0xEE000000
wanpipe1: IRQ 10 allocated to the AFT PCI card
wanpipe1: Initializing for SMP
wanpipe1: Starting AFT Quad Hardware Init.
wanpipe1: Enabling front end link monitor
wanpipe1: Global Chip Configuration: used=1
wanpipe1: Global Front End Configuraton!
wanpipe1: T1/E1/J1 Global configuration!
wanpipe1: AFT Data Mux Bit Map: 0x76543210
wanpipe1: Setting E1 configuration (Port 1)!
wanpipe1: All channels enabled
wanpipe1: Front end successful
wanpipe1: AFT Security: UnChannelised
wanpipe1: Configuring Device   :wanpipe1  FrmVr=8
wanpipe1:    Global MTU   = 1500
wanpipe1:    Global MRU   = 1500
wanpipe1:    Data Mux Map = 0x76543210
wanpipe1: Configuring Interface: w1g1
wanpipe1:w1g1: Running in TDM Voice mode.
wanpipe1: AFT Fifo Level Map: 0x02082082
wanpipe1: Registering interface to Zaptel span # 1!
wanpipe1:    MRU           :248
wanpipe1:    MTU           :248
wanpipe1:    HDLC Eng      :Off (Transparent)
wanpipe1:    Data Mux Ctrl :On
wanpipe1:w1g1: Active channels = 0xFFFFFFFE
wanpipe1:w1g1: Setting first time slot to 1
wanpipe1:w1g1: Config for Transparent mode: Idle=0 Len=248
wanpipe1:w1g1: Allocating 65 dma skb len=256 Chaining=Off

Michael Bielicki

2005-Feb-17 19:38 UTC

head link

[Asterisk-Users] Sangoma A104 - D-Channel problem

upgrade to the following wanpipe and also upgrade the firmware o the
crd (it's included in the wanpipe softwaare)
ftp://ftp.sangoma.com/linux/custom/2.3.2/wanpipe-beta5g-2.3.2.tgz


On Thu, 17 Feb 2005 16:07:54 +0100, Kumak <kumak@exe.pl>
wrote:> 
> Hello,
> I have following problem with Sangoma A104 card:
> 
> CLI> pri show span 1
> Primary D-channel: 16
> Status: Provisioned, Down, Active
> Switchtype: EuroISDN
> Type: CPE
> Window Length: 0/7
> Sentrej: 0
> SolicitFbit: 0
> Retrans: 0
> Busy: 0
> Overlap Dial: 0
> T200 Timer: 1000
> T203 Timer: 10000
> T305 Timer: 30000
> T308 Timer: 4000
> T313 Timer: 4000
> N200 Counter: 3
> 
> NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
> NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
> NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
> NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
> 
> Any idea how to fix it?
> 
> My configs:
> 
> zaptel.conf:
> 
> span=1,1,1,ccs,hdb3,crc4
> bchan=1-15,17-31
> dchan=16
> 
> zapata.conf
> 
> [channels]
> switchtype=euroisdn
> pridialplan=unknown
> overlapdial=no
> usecallerid=yes
> hidecallerid=yes
> callwaiting=no
> callwaitingcallerid=no
> threewaycalling=no
> transfer=no
> cancallforward=no
> callreturn=no
> jitterbuffers=4
> echocancel=yes
> echocancelwhenbridged=no
> echotraining=yes
> relaxdtmf=yes
> rxgain=0.5
> txgain=0.9
> immediate=no
> amaflags=billing
> adsi=no
> busydetect=no
> callprogress=no
> context = zapline1
> switchtype = euroisdn
> group=1
> signalling = pri_cpe
> channel => 1-15
> channel => 17-31
> 
> cat /proc/zaptel/1 :
> 
> Span 1: WPE1/0 "wanpipe1 card 0" HDB3//CRC4
> 
>            1 WPE1/0/1 Clear (In use)
>            2 WPE1/0/2 Clear (In use)
>            3 WPE1/0/3 Clear (In use)
>            4 WPE1/0/4 Clear (In use)
>            5 WPE1/0/5 Clear (In use)
>            6 WPE1/0/6 Clear (In use)
>            7 WPE1/0/7 Clear (In use)
>            8 WPE1/0/8 Clear (In use)
>            9 WPE1/0/9 Clear (In use)
>           10 WPE1/0/10 Clear (In use)
>           11 WPE1/0/11 Clear (In use)
>           12 WPE1/0/12 Clear (In use)
>           13 WPE1/0/13 Clear (In use)
>           14 WPE1/0/14 Clear (In use)
>           15 WPE1/0/15 Clear (In use)
>           16 WPE1/0/16 HDLCFCS (In use)
>           17 WPE1/0/17 Clear (In use)
>           18 WPE1/0/18 Clear (In use)
>           19 WPE1/0/19 Clear (In use)
>           20 WPE1/0/20 Clear (In use)
>           21 WPE1/0/21 Clear (In use)
>           22 WPE1/0/22 Clear (In use)
>           23 WPE1/0/23 Clear (In use)
>           24 WPE1/0/24 Clear (In use)
>           25 WPE1/0/25 Clear (In use)
>           26 WPE1/0/26 Clear (In use)
>           27 WPE1/0/27 Clear (In use)
>           28 WPE1/0/28 Clear (In use)
>           29 WPE1/0/29 Clear (In use)
>           30 WPE1/0/30 Clear (In use)
>           31 WPE1/0/31 Clear (In use)
> 
> Information from dmesg:
> 
> Processing WAN device wanpipe1...
> wanpipe1: Locating: A104 card, CPU A, PciSlot=8, PciBus=0
> wanpipe1: Found: A104 card, CPU A, PciSlot=8, PciBus=0, Port=0
> PCI: Found IRQ 10 for device 00:08.0
> wanpipe1: AFT PCI memory at 0xEE000000
> wanpipe1: IRQ 10 allocated to the AFT PCI card
> wanpipe1: Initializing for SMP
> wanpipe1: Starting AFT Quad Hardware Init.
> wanpipe1: Enabling front end link monitor
> wanpipe1: Global Chip Configuration: used=1
> wanpipe1: Global Front End Configuraton!
> wanpipe1: T1/E1/J1 Global configuration!
> wanpipe1: AFT Data Mux Bit Map: 0x76543210
> wanpipe1: Setting E1 configuration (Port 1)!
> wanpipe1: All channels enabled
> wanpipe1: Front end successful
> wanpipe1: AFT Security: UnChannelised
> wanpipe1: Configuring Device   :wanpipe1  FrmVr=8
> wanpipe1:    Global MTU   = 1500
> wanpipe1:    Global MRU   = 1500
> wanpipe1:    Data Mux Map = 0x76543210
> wanpipe1: Configuring Interface: w1g1
> wanpipe1:w1g1: Running in TDM Voice mode.
> wanpipe1: AFT Fifo Level Map: 0x02082082
> wanpipe1: Registering interface to Zaptel span # 1!
> wanpipe1:    MRU           :248
> wanpipe1:    MTU           :248
> wanpipe1:    HDLC Eng      :Off (Transparent)
> wanpipe1:    Data Mux Ctrl :On
> wanpipe1:w1g1: Active channels = 0xFFFFFFFE
> wanpipe1:w1g1: Setting first time slot to 1
> wanpipe1:w1g1: Config for Transparent mode: Idle=0 Len=248
> wanpipe1:w1g1: Allocating 65 dma skb len=256 Chaining=Off
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 

-- 
Michal Bielicki
http://www.asterisk.com.pl/

Daniel Bichara

2005-Feb-18 14:57 UTC

head link

[Asterisk-Users] Sangoma A104 - D-Channel problem

Hi,

Did you tried to set your DMA or SATA as described at message "Sangoma 
A102 cards testing FIXED"?

Daniel

Kumak wrote:
>Hello,
>I have following problem with Sangoma A104 card:
>
>CLI> pri show span 1
>Primary D-channel: 16
>Status: Provisioned, Down, Active
>Switchtype: EuroISDN
>Type: CPE
>Window Length: 0/7
>Sentrej: 0
>SolicitFbit: 0
>Retrans: 0
>Busy: 0
>Overlap Dial: 0
>T200 Timer: 1000
>T203 Timer: 10000
>T305 Timer: 30000
>T308 Timer: 4000
>T313 Timer: 4000
>N200 Counter: 3
>
>NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
>NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
>NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
>NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Abort (6)
on Primary D-channel of span 1
>
>Any idea how to fix it?
>
>My configs:
>
>zaptel.conf:
>
>span=1,1,1,ccs,hdb3,crc4
>bchan=1-15,17-31
>dchan=16
>
>zapata.conf
>
>[channels]
>switchtype=euroisdn
>pridialplan=unknown
>overlapdial=no
>usecallerid=yes
>hidecallerid=yes
>callwaiting=no
>callwaitingcallerid=no
>threewaycalling=no
>transfer=no
>cancallforward=no
>callreturn=no
>jitterbuffers=4
>echocancel=yes
>echocancelwhenbridged=no
>echotraining=yes
>relaxdtmf=yes
>rxgain=0.5
>txgain=0.9
>immediate=no
>amaflags=billing
>adsi=no
>busydetect=no
>callprogress=no
>context = zapline1
>switchtype = euroisdn
>group=1
>signalling = pri_cpe
>channel => 1-15
>channel => 17-31
>
>cat /proc/zaptel/1 :
>
>Span 1: WPE1/0 "wanpipe1 card 0" HDB3//CRC4
>
>           1 WPE1/0/1 Clear (In use)
>           2 WPE1/0/2 Clear (In use)
>           3 WPE1/0/3 Clear (In use)
>           4 WPE1/0/4 Clear (In use)
>           5 WPE1/0/5 Clear (In use)
>           6 WPE1/0/6 Clear (In use)
>           7 WPE1/0/7 Clear (In use)
>           8 WPE1/0/8 Clear (In use)
>           9 WPE1/0/9 Clear (In use)
>          10 WPE1/0/10 Clear (In use)
>          11 WPE1/0/11 Clear (In use)
>          12 WPE1/0/12 Clear (In use)
>          13 WPE1/0/13 Clear (In use)
>          14 WPE1/0/14 Clear (In use)
>          15 WPE1/0/15 Clear (In use)
>          16 WPE1/0/16 HDLCFCS (In use)
>          17 WPE1/0/17 Clear (In use)
>          18 WPE1/0/18 Clear (In use)
>          19 WPE1/0/19 Clear (In use)
>          20 WPE1/0/20 Clear (In use)
>          21 WPE1/0/21 Clear (In use)
>          22 WPE1/0/22 Clear (In use)
>          23 WPE1/0/23 Clear (In use)
>          24 WPE1/0/24 Clear (In use)
>          25 WPE1/0/25 Clear (In use)
>          26 WPE1/0/26 Clear (In use)
>          27 WPE1/0/27 Clear (In use)
>          28 WPE1/0/28 Clear (In use)
>          29 WPE1/0/29 Clear (In use)
>          30 WPE1/0/30 Clear (In use)
>          31 WPE1/0/31 Clear (In use)
>
>
>Information from dmesg:
>
>Processing WAN device wanpipe1...
>wanpipe1: Locating: A104 card, CPU A, PciSlot=8, PciBus=0
>wanpipe1: Found: A104 card, CPU A, PciSlot=8, PciBus=0, Port=0
>PCI: Found IRQ 10 for device 00:08.0
>wanpipe1: AFT PCI memory at 0xEE000000
>wanpipe1: IRQ 10 allocated to the AFT PCI card
>wanpipe1: Initializing for SMP
>wanpipe1: Starting AFT Quad Hardware Init.
>wanpipe1: Enabling front end link monitor
>wanpipe1: Global Chip Configuration: used=1
>wanpipe1: Global Front End Configuraton!
>wanpipe1: T1/E1/J1 Global configuration!
>wanpipe1: AFT Data Mux Bit Map: 0x76543210
>wanpipe1: Setting E1 configuration (Port 1)!
>wanpipe1: All channels enabled
>wanpipe1: Front end successful
>wanpipe1: AFT Security: UnChannelised
>wanpipe1: Configuring Device   :wanpipe1  FrmVr=8
>wanpipe1:    Global MTU   = 1500
>wanpipe1:    Global MRU   = 1500
>wanpipe1:    Data Mux Map = 0x76543210
>wanpipe1: Configuring Interface: w1g1
>wanpipe1:w1g1: Running in TDM Voice mode.
>wanpipe1: AFT Fifo Level Map: 0x02082082
>wanpipe1: Registering interface to Zaptel span # 1!
>wanpipe1:    MRU           :248
>wanpipe1:    MTU           :248
>wanpipe1:    HDLC Eng      :Off (Transparent)
>wanpipe1:    Data Mux Ctrl :On
>wanpipe1:w1g1: Active channels = 0xFFFFFFFE
>wanpipe1:w1g1: Setting first time slot to 1
>wanpipe1:w1g1: Config for Transparent mode: Idle=0 Len=248
>wanpipe1:w1g1: Allocating 65 dma skb len=256 Chaining=Off
>
>
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users@lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>  
>

Seemingly Similar Threads

Search for more reasonably related threads

asterisk users - Feb 2005 - Sangoma A104 - D-Channel problem

[Asterisk-Users] Sangoma A104 - D-Channel problem

[Asterisk-Users] Sangoma A104 - D-Channel problem

[Asterisk-Users] Sangoma A104 - D-Channel problem

Seemingly Similar Threads