Re: [asterisk-users] Problem with Sangoma A104 and euroisdn pri
Can you post outputs for the following commands;
#asterisk -rx 'pri show spans'
#asterisk -rx 'zap show channels'
#wanpipemon -i w1g1 -c Ta
Sam
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jaap Winius
Sent: Thursday, April 01, 2010 4:15 PM
To: Asterisk
Subject: [asterisk-users] Problem with Sangoma A104 and euroisdn pri
Hi all,
My problem boils down to these errors:
... Unable to create channel of type 'ZAP' (cause 34 -
Circuit/channel congestion)
== Everyone is busy/congested at this time
This is triggered by lines in extentions.conf such as:
exten = _X.,1,Dial(ZAP/g1/${EXTEN},,W)
The system is CentOS v5.2 with Asterisk 1.4.23
(druid-asterisk-1.4.23.1-2), a Sangoma A104 4-port card, Wanpipe
v3.4.4 and Zaptel v1.4.12.1. The system is attached to a single
EuroISDN PRI and is located in the Netherlands.
Besides the above error, I also noticed this:
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: 1
T305 Timer: 3
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3
The status needs to be Provisioned, Up, Active.
Following Sangoma's instructions for debugging an Asterisk PRI span, I
can confirm that there are only outgoing frames and that the D-channel
messages in Asterisk are the same as what the Wanpipe drivers are
seeing. So, assuming that my local telco (KPN Telecom) has activated
the D-channel, what else could possibly be causing this problem?
Thanks,
Jaap
PS -- Below are my current configuration files and debugging output:
==begin zaptel.conf
loadzone=us
defaultzone=us
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
hardhdlc=16
==end zaptel.conf ==
==begin wanpipe1.conf ==
[devices]
wanpipe1 = WAN_AFT_TE1, Comment
[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment
[wanpipe1]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 13
FE_MEDIA= E1
FE_LCODE= HDB3
FE_FRAME= NCRC4
FE_LINE= 1
TE_CLOCK = NORMAL
TE_REF_CLOCK= 0
TE_SIG_MODE = CCS
TE_HIGHIMPEDANCE= NO
LBO = 120OH
FE_TXTRISTATE= NO
MTU = 1500
UDPPORT = 9000
TTL= 255
IGNORE_FRONT_END = NO
TDMV_SPAN= 1
TDMV_DCHAN= 16
TDMV_HW_DTMF= NO
TDMV_HW_FAX_DETECT = NO
[w1g1]
ACTIVE_CH= ALL
TDMV_HWEC= NO
==end wanpipe1.conf
==begin zapata.conf
[trunkgroups]
[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
switchtype=euroisdn
context=default
group=1
signalling=pri_cpe
channel =1-15,17-31
==end zapata.conf ==
Here's some debugging output:
=== begin debug info ==
# ztcfg -vv
Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
==
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Hardware assisted D-channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18)
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: Clear channel (Default) (Slaves: 24)
Channel 25: Clear channel (Default) (Slaves: 25)
Channel 26: Clear channel (Default) (Slaves: 26)
Channel 27: Clear channel (Default) (Slaves: 27)
Channel 28: Clear channel (Default) (Slaves: 28)
Channel
Re: [asterisk-users] Problem with Sangoma A104 and euroisdn pri
Quoting RESEARCH resea...@businesstz.com: Can you post outputs for the following commands; #asterisk -rx 'pri show spans' #asterisk -rx 'zap show channels' #wanpipemon -i w1g1 -c Ta Sure thing! Here they are in succession: == # asterisk -rx 'pri show spans' PRI span 1/0: Provisioned, Down, Active # asterisk -rx 'zap show channels' Chan Extension Context Language MOH Interpret pseudodefaultdefault 1defaultdefault 2defaultdefault 3defaultdefault 4defaultdefault 5defaultdefault 6defaultdefault 7defaultdefault 8defaultdefault 9defaultdefault 10defaultdefault 11defaultdefault 12defaultdefault 13defaultdefault 14defaultdefault 15defaultdefault 17defaultdefault 18defaultdefault 19defaultdefault 20defaultdefault 21defaultdefault 22defaultdefault 23defaultdefault 24defaultdefault 25defaultdefault 26defaultdefault 27defaultdefault 28defaultdefault 29defaultdefault 30defaultdefault 31defaultdefault # wanpipemon -i w1g1 -c Ta * w1g1: E1 Alarms (Framer) * ALOS:OFF| LOS:OFF RED:OFF| AIS:OFF OOF:OFF| RAI:OFF * w1g1: E1 Alarms (LIU) * Short Circuit:OFF Open Circuit:OFF Loss of Signal:OFF * w1g1: E1 Performance Monitoring Counters * Line Code Violation: 324 Far End Block Errors: 0 CRC4 Errors: 0 FAS Errors: 0 Rx Level: -2.5db # == Cheers, Jaap -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Problem with Sangoma A104 and euroisdn pri
what about cat /proc/zaptel/* HTH, Ioan. On Fri, Apr 2, 2010 at 2:46 PM, Jaap Winius jwin...@umrk.to wrote: # asterisk -rx 'pri show spans' PRI span 1/0: Provisioned, Down, Active -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Problem with Sangoma A104 and euroisdn pri
On Thu, Apr 1, 2010 at 6:15 AM, Jaap Winius jwin...@umrk.to wrote: [snip] Besides the above error, I also noticed this: 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: 1 T305 Timer: 3 T308 Timer: 4000 T309 Timer: -1 T313 Timer: 4000 N200 Counter: 3 The status needs to be Provisioned, Up, Active. Following Sangoma's instructions for debugging an Asterisk PRI span, I can confirm that there are only outgoing frames and that the D-channel messages in Asterisk are the same as what the Wanpipe drivers are seeing. So, assuming that my local telco (KPN Telecom) has activated the D-channel, what else could possibly be causing this problem? I would call KPN Telecom and ask them for help as well. They will have much more sophisticated tools for debugging PRIs and also will be able to check on their end if they see the D-Channel as up. -- James -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Problem with Sangoma A104 and euroisdn pri - SOLVED
Quoting James Lamanna jlama...@gmail.com: I would call KPN Telecom and ask them for help as well. They will have much more sophisticated tools for debugging PRIs and also will be able to check on their end if they see the D-Channel as up. After studying the configuration more closely, the first thing I changed was... === begin wanpipe1.conf === [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort= PRI AUTO_PCISLOT= NO PCISLOT = 4 PCIBUS = 13 FE_MEDIA= E1 FE_LCODE= HDB3 FE_FRAME= NCRC4 FE_LINE = 1 TE_CLOCK= NORMAL TE_REF_CLOCK= 0 TE_HIGHIMPEDANCE = NO TE_RX_SLEVEL= 120 LBO = 120OH TE_SIG_MODE = CCS FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 16 TDMV_HW_DTMF= NO [w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = YES === end wanpipe1.conf = This was my last result after running /usr/sbin/wancfg, although I'm not sure the changes made any difference. Probably minor. The second step was to modify /etc/zaptel.conf to reflect the wanpipe1.conf configuration: === begin /etc/zaptel.conf loadzone=nl defaultzone=nl span=1,1,0,ccs,hdb3 bchan=1-15,17-31 hardhdlc=16 === end /etc/zaptel.conf == The span line used to be span=1,0,0,ccs,hdb3. The second field specifies the timing source, which in my case needs to be the provider (KPN), so I changed it to a 1. I also took the opportunity to changes the loadzone and defaultzone to nl. However, I noticed later that the old configuration works as well, so these changes were evidently not too important. In the end, the real problem turned out to be on the other end of the line. After opening a trouble ticket with KPN Telecom, at one point the pri just started to work: = CLI pri show span 1 Primary D-channel: 16 Status: Provisioned, Up, 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: 1 T305 Timer: 3 T308 Timer: 4000 T309 Timer: -1 T313 Timer: 4000 N200 Counter: 3 = Also, this is what now appears at the CLI shortly after starting Asterisk: = -- B-channel 0/1 successfully restarted on span 1 -- B-channel 0/2 successfully restarted on span 1 -- B-channel 0/3 successfully restarted on span 1 -- B-channel 0/4 successfully restarted on span 1 -- B-channel 0/5 successfully restarted on span 1 -- B-channel 0/6 successfully restarted on span 1 -- B-channel 0/7 successfully restarted on span 1 -- B-channel 0/8 successfully restarted on span 1 -- B-channel 0/9 successfully restarted on span 1 -- B-channel 0/10 successfully restarted on span 1 -- B-channel 0/11 successfully restarted on span 1 -- B-channel 0/12 successfully restarted on span 1 -- B-channel 0/13 successfully restarted on span 1 -- B-channel 0/14 successfully restarted on span 1 -- B-channel 0/15 successfully restarted on span 1 -- B-channel 0/17 successfully restarted on span 1 -- B-channel 0/18 successfully restarted on span 1 -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/20 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 -- B-channel 0/22 successfully restarted on span 1 -- B-channel 0/23 successfully restarted on span 1 -- B-channel 0/24 successfully restarted on span 1 -- B-channel 0/25 successfully restarted on span 1 -- B-channel 0/26 successfully restarted on span 1 -- B-channel 0/27 successfully restarted on span 1 -- B-channel 0/28 successfully restarted on span 1 -- B-channel 0/29 successfully restarted on span 1 -- B-channel 0/30 successfully restarted on span 1 -- B-channel 0/31 successfully restarted on span 1 = I guess that's good. When I asked KPN what they had done, they said they hadn't discovered any problems. However, I was also told that the line was reset as a normal part of their troubleshooting procedure, so I guess that made the difference. Problem solved. Thanks! Jaap -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Problem with Sangoma A104 and euroisdn pri
Hi all,
My problem boils down to these errors:
... Unable to create channel of type 'ZAP' (cause 34 -
Circuit/channel congestion)
== Everyone is busy/congested at this time
This is triggered by lines in extentions.conf such as:
exten = _X.,1,Dial(ZAP/g1/${EXTEN},,W)
The system is CentOS v5.2 with Asterisk 1.4.23
(druid-asterisk-1.4.23.1-2), a Sangoma A104 4-port card, Wanpipe
v3.4.4 and Zaptel v1.4.12.1. The system is attached to a single
EuroISDN PRI and is located in the Netherlands.
Besides the above error, I also noticed this:
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: 1
T305 Timer: 3
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3
The status needs to be Provisioned, Up, Active.
Following Sangoma's instructions for debugging an Asterisk PRI span, I
can confirm that there are only outgoing frames and that the D-channel
messages in Asterisk are the same as what the Wanpipe drivers are
seeing. So, assuming that my local telco (KPN Telecom) has activated
the D-channel, what else could possibly be causing this problem?
Thanks,
Jaap
PS -- Below are my current configuration files and debugging output:
==begin zaptel.conf
loadzone=us
defaultzone=us
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
hardhdlc=16
==end zaptel.conf ==
==begin wanpipe1.conf ==
[devices]
wanpipe1 = WAN_AFT_TE1, Comment
[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment
[wanpipe1]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 13
FE_MEDIA= E1
FE_LCODE= HDB3
FE_FRAME= NCRC4
FE_LINE= 1
TE_CLOCK = NORMAL
TE_REF_CLOCK= 0
TE_SIG_MODE = CCS
TE_HIGHIMPEDANCE= NO
LBO = 120OH
FE_TXTRISTATE= NO
MTU = 1500
UDPPORT = 9000
TTL= 255
IGNORE_FRONT_END = NO
TDMV_SPAN= 1
TDMV_DCHAN= 16
TDMV_HW_DTMF= NO
TDMV_HW_FAX_DETECT = NO
[w1g1]
ACTIVE_CH= ALL
TDMV_HWEC= NO
==end wanpipe1.conf
==begin zapata.conf
[trunkgroups]
[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
switchtype=euroisdn
context=default
group=1
signalling=pri_cpe
channel =1-15,17-31
==end zapata.conf ==
Here's some debugging output:
=== begin debug info ==
# ztcfg -vv
Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
==
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Hardware assisted D-channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18)
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: Clear channel (Default) (Slaves: 24)
Channel 25: Clear channel (Default) (Slaves: 25)
Channel 26: Clear channel (Default) (Slaves: 26)
Channel 27: Clear channel (Default) (Slaves: 27)
Channel 28: Clear channel (Default) (Slaves: 28)
Channel 29: Clear channel (Default) (Slaves: 29)
Channel 30: Clear channel (Default) (Slaves: 30)
Channel 31: Clear channel (Default) (Slaves: 31)
31 channels to configure.
# wanrouter status
Devices currently active:
wanpipe1
Wanpipe Config:
Device name | Protocol Map | Adapter | IRQ | Slot/IO | If's | CLK |
Baud rate |
wanpipe1| N/A | A101/1D/A102/2D/4/4D/8| 169 | 4 | 1
| N/A |
