[asterisk-users] Problem with Sangoma A104 and euroisdn pri - SOLVED

[Jaap Winius]

Quoting James Lamanna <jlamanna at 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: 10000
T305 Timer: 30000
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