This would imply that the define "CONFIG_PRODUCT_WANPIPE_TDM_VOICE" is not set 
when wanpipe is build.

This is definitely a Philip question...

Lonnie


On Nov 15, 2009, at 3:35 PM, Tom Mazzotta wrote:

> Lonnie,
> 
> These tips helped me make a lot of progress. On the remote system with the 
> TDM card, "dahdi show status" is recognizing the card. However, my local 
> system with the Sangoma board is still a problem. My concern is the message 
> "wanpipe1: Error: TDM VOICE prot not compiled" reported by dmesg (see below). 
> Is it possible that there is some required component of wanpipe that was left 
> out of the 0.7 build I am testing?
> 
> pbx ~ # dmesg | grep wanpipe
> wanpipe1: Running post initialization...
> wanpipe1: Remora config done!
> wanpipe1: AFT Data Mux Bit Map: 0x01234567
> wanpipe1: Front End Interface Ready 0x00000000
> wanpipe1: Register EC interface wanec1 (usage 1, max ec chans 32)!
> wanpipe1: Configuring Device   :wanpipe1  FrmVr=11
> wanpipe1:    Global MTU           = 1500
> wanpipe1:    Global MRU           = 1500
> wanpipe1:    Data Mux Map         = 0x01234567
> wanpipe1:    Rx CRC Bytes         = 0
> wanpipe1:    Global TDM Int       = Disabled
> wanpipe1:    Global TDM Ring      = Disabled
> wanpipe1:    TDMV HW DTMF/FAX     = Enabled/Disabled(0)
> wanpipe1:    TDMV Span            = 1 : Enabled
> wanpipe1:    RTP TAP              = Disabled
> wanpipe1: Error: TDM VOICE prot not compiled
> wanpipe1:        during installation process!
> wanpipe1: Shutting Down!
> wanpipe1: TASKQ Not Running
> wanpipe1: Unconfiguring FXS/FXO Front End...
> wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)
> wanpipe1: Unregister interface from wanec1 (usage 1)!
> wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)
> wanpipe1: Global Chip Shutdown Usage=1
> wanpipe1: Unconfiguring FXS/FXO Front End...
> wanpipe1: Master shutting down
> af_wanpipe: Unregistering Wanpipe API Socket Module
> wanpipe: WANPIPE Modules Unloaded.
> pbx ~ #
> 
> -----Original Message-----
> From: Lonnie Abelbeck [mailto:[email protected]] 
> Sent: Sunday, November 15, 2009 2:51 PM
> To: AstLinux Users Mailing List
> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade?
> 
> Tom,
> 
> DAHDI files should be located as /mnt/kd/dahdi/*.conf 
> 
> A reboot is required for DAHDI to see them.  Also, after such files are 
> created, they may be edited via the Edit tab.
> 
> While this is painful, clearly DAHDI is the future, and the transition from 
> ZAPTEL needs to occur.
> 
> Lonnie


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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