See copies of the requested files below. The critical one is wanpipe1.conf, 
because without building this one on another system (running a full 
implementation of perl to support the Sangoma configuration generator) it would 
have been very difficult to figure out what parameters are necessary to operate 
the A200 card.

You will find some documentation on this file in the Sangoma wiki here:
http://wiki.sangoma.com/Wanpipe-Asterisk-Configuration-File#aft_20x_for_zaptel

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

# wanpipe1.conf
#
[devices]
wanpipe1 = WAN_AFT_ANALOG, Comment

[interfaces]
wag1 = wanpipe1, , TDM_VOICE, Comment

[wanpipe1]
CARD_TYPE       = AFT
S514CPU         = A
CommPort        = PRI
AUTO_PCISLOT    = NO
PCISLOT         = 14
PCIBUS          = 0
FE_MEDIA        = FXO/FXS
TDMV_LAW        = MULAW
TDMV_OPERMODE   = FCC
RM_BATTTHRESH   = 3
RM_BATTDEBOUNCE = 16
FE_NETWORK_SYNC = NO
MTU             = 1500
UDPPORT         = 9000
TTL             = 255
IGNORE_FRONT_END = NO
TDMV_SPAN       = 1
TDMV_HW_DTMF    = YES   # Req's HWEC
RM_FXOTXGAIN    = 10

[wag1]
ACTIVE_CH       = ALL
##TDMV_ECHO_OFF = NO    # Legacy parameter; overwritten by TDMV_HWEC
TDMV_HWEC       = YES   # Enable HWEC module

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

# system.conf
#
loadzone=us
defaultzone=us

#Sangoma A200 [slot:14 bus:0 span:1] <wanpipe1>
fxsks=1 # fxo port
fxsks=2 # fxo port
fxoks=3 # fxs port
fxoks=4 # fxs port

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

; chan_dahdi.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=3.0
txgain=3.0
group=1
callgroup=1
pickupgroup=1

;Sangoma A200 [slot:14 bus:0 span:1]  <wanpipe1>
context=inbound-personal
immediate=no
signalling = fxs_ks
channel => 1 ; fxo port

context=inbound-biz
immediate=no
signalling = fxs_ks
channel => 2 ; fxo port

context=inbound-doorbell
callerid="FRONT" <DOORBELL>
immediate=yes
signalling = fxo_ks
channel => 3 ; fxs port

context=inbound-doorbell
callerid="SIDE" <DOORBELL>
immediate=yes
signalling = fxo_ks
channel => 4 ; fxs port

-----Original Message-----
From: Darrick Hartman [mailto:[email protected]] 
Sent: Saturday, December 12, 2009 8:18 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Wanpipe users READ THIS

Tom

Could you paste the contents of those config files?  Probably could create some 
of those manually on Astlinux with the right example files. 

Darrick
Sent from my BlackBerry(r) wireless device from U.S. Cellular

-----Original Message-----
From: Tom Mazzotta <[email protected]>
Date: Sat, 12 Dec 2009 18:40:14 
To: AstLinux Users Mailing List<[email protected]>
Subject: Re: [Astlinux-users] Wanpipe users READ THIS

I am running an A200 card (2x FXO, 2x FXS, EC) with astlinux 0.7. To configure 
the card I needed to copy wanpipe1.conf from another system because 
wancfg_dahdi won't run due to a dependency on perl. I also needed to create by 
hand system.conf and chan_dahdi.conf due to the same problem.

The only utilities I use are "wanrouter", "wanpipemon", and "wanconfig", but I 
do not believe these files are located in the directories you specified.

I'm not sure how I would know if the other files are necessary short of 
removing them from my system. 

-----Original Message-----
From: Darrick Hartman (lists) [mailto:[email protected]] 
Sent: Saturday, December 12, 2009 5:42 PM
To: AstLinux Users Mailing List; AstLinux Developers Mailing List
Subject: [Astlinux-users] Wanpipe users READ THIS

We need some input from Sangoma (wanpipe) users.

Namely, we need some input on what steps you use to generate 
configuration files and more importantly, which files in 
/stat/etc/wanpipe (which may also reside in /mnt/kd/wanpipe) are 
required.  There are several files that are present in that directory 
which may not be required.

If we don't get feedback, we may drop support for Wanpipe in Astlinux. 
None of the developers use these products and they take enough time and 
space in the build to bring this into question.  If we can get some 
clarification on these issues, I'm sure we can find a good way to move 
forward.

We would really like to get this cleared up before we release 0.7.

Thanks,

Darrick
-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].


------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].


------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to