[Asterisk-Users] Sangoma A104 errors

Tue Oct 25 14:42:10 MST 2005

When compiling the wanpipe drivers, you are faced with only one option that
has 1 through 4 as a choice.  I choose 3.  This does the config for me. 

You really have to watch when you compile these drivers since at the end YOU
are confirming the compile was good.  You must look over the last 10 or so
lines before confirming.  Then I believe the tools are complied.

I was using beta 12.  Updated zaptel and it blew up.  Recompiled zaptel, and
asterisk, still bad.  Went to a backup, then downloaded the latest wanpipe
(15) drivers and this would not compile with zaptel.

So 15 & prior zaptel - is a no no
12 and new zaptel is a nono
12 and old ok
15 and new zaptel is ok

Also I follow this procedure
Compile zaptel first,  Then wanpipe, then you must do zaptel again.

If you did all of this.  You must configure wigi interfaces.  Only thing
necessary for pri is # of chans and the d chan number (24)

Here is my config:

PRI: wigi file -----------------------------------------
# Wanrouter interface configuration file
# name:	w1g1
# date:	Thu Aug 11 22:30:10 EDT 2005
#
DEVICE=w1g1
IPADDR=
NETMASK=255.255.255.255
POINTOPOINT=
ONBOOT=yes

Wanpipe 1 conf file-----------------------------------
#================================================
# WANPIPE1 Configuration File
#================================================
#
# Date: Fri Aug 12 11:07:45 EDT 2005
#
# Note: This file was generated automatically
#       by /usr/sbin/wancfg program.
#
#       If you want to edit this file, it is
#       recommended that you use wancfg program
#       to do so.
#================================================
# Sangoma Technologies Inc.
#================================================

[devices]
wanpipe1 = WAN_AFT, Comment

[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment

[wanpipe1]
CARD_TYPE 	= AFT
S514CPU 	= A
CommPort 	= PRI
AUTO_PCISLOT 	= NO
PCISLOT 	= 3
PCIBUS  	= 2
FE_MEDIA	= T1
FE_LCODE	= B8ZS
FE_FRAME	= ESF
FE_LINE		= 1
TE_CLOCK 	= NORMAL
TE_REF_CLOCK 	= 0
ACTIVE_CH	= ALL
TE_HIGHIMPEDANCE	= NO
LBO 		= 0DB
FE_TXTRISTATE	= NO
MTU 		= 1500
UDPPORT 	= 9000
TTL		= 255
IGNORE_FRONT_END = NO
TDMV_SPAN	= 1
TDMV_DCHAN	= 24

[w1g1]
ACTIVE_CH	= ALL
TDMV_ECHO_OFF	= NO

Zapata.conf--------------------------------

; Span 1:
;==========================PRI==============================================
===
; PRI
signalling = pri_net
group=0
context=from-pstn

;-----------------------------------------
; PRI
; T1
channel=>1-23 

Zaptel.conf ----------------------------------

##############################################################
#T1
span=1,0,0,esf,b8zs
#span=1,0,0,d4,ami

#use with PRI
bchan=1-23
dchan=24

---------------------
Hope this helps
:)
Paul

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Sharon
Sent: Tuesday, October 25, 2005 5:03 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Sangoma A104 errors

>besides shouldn't it be type 2 national.  Not sure if that's an option, but
> when I compile, I use the option 3 and the pri only needs the channels and
> the d chan specified.  So I never noticed if it said type 2.

didn't get wht u meant here? wht type r u talking abt?

> Are you using the newest drivers from Sangoma?  There was an update due to
> the revision in asterisk/zaptel and the patch point was modified by
Sangoma.
>
> If you used CVS to obtain the latest Zaptel / or used the latest A104
> drivers without the latest CVS, the patch point is wrong and Sangoma
> compiled wrong.
yes i used the newest drivers from Sangoma. and i'm running cvs
head(downloaded around start of august)

On 10/25/05, Paul <paul at siliconvp.com> wrote:
> Are you using the newest drivers from Sangoma?  There was an update due to
> the revision in asterisk/zaptel and the patch point was modified by
Sangoma.
>
> If you used CVS to obtain the latest Zaptel / or used the latest A104
> drivers without the latest CVS, the patch point is wrong and Sangoma
> compiled wrong.
>
> Besides shouldn't it be type 2 national.  Not sure if that's an option,
but
> when I compile, I use the option 3 and the pri only needs the channels and
> the d chan specified.  So I never noticed if it said type 2.
>
> :)
> Paul
>
>
>
>
> -----Original Message-----
> From: Sharon [mailto:asteriskgirl at gmail.com]
> Sent: Tuesday, October 25, 2005 10:37 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [Asterisk-Users] Sangoma A104 errors
>
> I am using a A104 Sangoma card. We are runningasterisk cvs head on our
> production box.After wanpipe configuration I am receiving the below
> mentioned error.
> pri show span looks good as below.
>
> pri show span 1
> Primary D-channel: 24
> Status: Provisioned, In Alarm, Down, Active
> Switchtype: National ISDN
> 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
>
> error on the server:
>
> Write to 33 failed: Bad address
> Short write: 0/5 (Bad address)
>
>
> Any help appreciated.
> Thank you,
>
>
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users at 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
>
_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
Asterisk-Users at 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