CHANUNAVAIL despite wanrouter loading, cannot get FXS or FXO working on Sangoma A200/Remora

[sipman]

CHANUNAVAIL despite wanrouter loading, cannot get FXS or FXO working.
Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card.
FreePBX 2.4.0.0 (Kernel 2.6.18-92.1.22.el5 (SMP) - CentOS release 5.2 (Final)).

// Re-compiled zaptel:
cd /usr/src/zaptel
make menuconfig (left xpp unchecked only) x to save
make clean
./configure
make
make install
make config

//Added the wanpipe dependancy;

cd /var
wget ftp://myftpserver//pbx_load//byacc-1.9-29.2.2.i386.rpm
rpm -i byacc-1.9-29.2.2.i386.rpm

//Then;
//Installed Sangoma Wanpipe-3.2.7.1.tgz wanpipe drivers (the recent ones don’t
//work) onto FreePBX 2.4.0.0 (Kernel 2.6.18-92.1.22.el5 (SMP) - CentOS release
//5.2 (Final))

wget ftp://myftpserver//pbx_load//wanpipe-3.2.7.1.tgz
tar xvf wanpipe-3.2.7.1.tgz
cd wanpipe-3.2.7.1
chmod 744 Setup
./Setup install --silent --protocol=TDM
setup-sangoma
(ALAW ztcfg etc.)

//The channels for both FXS and FXO are assigned and available.(zapata-auto.conf):

;Sangoma A200 [slot:4 bus:2 span:1]
context=from-internal
group=1
signalling = fxo_ks
channel => 1

context=from-internal
group=1
signalling = fxo_ks
channel => 2

context=from-zaptel
group=0
signalling = fxs_ks
channel => 3

context=from-zaptel
group=0
signalling = fxs_ks
channel => 4

// Results of a /usr/src/zaptel/ztscan tool:

active=yes
alarms=OK
description=wrtdm Board 1
name=WRTDM/0
manufacturer=
devicetype=
location=
basechan=1
totchans=24
irq=0
type=analog
port=1,FXS
port=2,FXS
port=3,FXO
port=4,FXO
port=5,none
port=6,none

// results of wanrouter hwprobe:

Wanpipe Hardware Probe Info

1 . AFT-A200-SH : SLOT=4 : BUS=2 : IRQ=11 : CPU=A : PORT=PRI : HWEC=32 : V=11

Card Cnt: S508=0 S514X=0 S518=0 A101-2=0 A104=0 A300=0 A200=1 A108=0 A056=0

// results cat /var/log/messages

Jun 25 14:42:47 pbx kernel: WANPIPE™ Socket API Module Stable 3.2.7.1.0 © 1994-2008 Sangoma Technologies Inc
Jun 25 14:42:47 pbx kernel: NET: Registered protocol family 25
Jun 25 14:42:47 pbx kernel: WANPIPE™ L.I.P Network Layer Stable 3.2.7.1.0 © 1995-2004 Sangoma Technologies Inc.
Jun 25 14:42:47 pbx kernel: WanpipeLIP: Protocols: No Protocol Compiled
Jun 25 14:42:47 pbx kernel:
Jun 25 14:42:47 pbx kernel: WANPIPE™ WANEC Layer Stable 3.2.7.1.0 © 1995-2006 Sangoma Technologies Inc.
Jun 25 14:42:47 pbx kernel: wanec_create_dev: Registering Wanpipe ECDEV Device!
Jun 25 14:42:47 pbx kernel: wanpipe1: Starting WAN Setup
Jun 25 14:42:47 pbx kernel:
Jun 25 14:42:47 pbx kernel: Processing WAN device wanpipe1…
Jun 25 14:42:47 pbx kernel: wanpipe1: Locating: A200/400 card, CPU A, PciSlot=4, PciBus=2
Jun 25 14:42:47 pbx kernel: wanpipe1: Front-End interface functions are not defined!
Jun 25 14:42:47 pbx kernel: wanpipe1: Found: A200/400 card, CPU A, PciSlot=4, PciBus=2, Port=0
Jun 25 14:42:47 pbx kernel: wanpipe1: AFT PCI memory at 0xFE8F0000
Jun 25 14:42:47 pbx kernel: wanpipe1: IRQ 169 allocated to the AFT PCI card
Jun 25 14:42:47 pbx kernel: wanpipe1: Starting AFT Analog Hardware Init.
Jun 25 14:42:47 pbx kernel: wanpipe1: Enabling front end link monitor
Jun 25 14:42:47 pbx kernel: wanpipe1: Global Chip Configuration: used=1
Jun 25 14:42:47 pbx kernel: wanpipe1: Global Front End Configuraton!
Jun 25 14:42:47 pbx kernel: wanpipe1: Configuring FXS/FXO Front End …
Jun 25 14:42:47 pbx kernel: wanpipe1: Module 0: Installed – Auto FXS!
Jun 25 14:42:47 pbx kernel: wanpipe1: Module 1: Installed – Auto FXS!
Jun 25 14:42:47 pbx kernel: wanpipe1: Module 2: Installed – Auto FXO (FCC mode)!
Jun 25 14:42:47 pbx kernel: wanpipe1: Module 3: Installed – Auto FXO (FCC mode)!
Jun 25 14:42:47 pbx kernel: wanpipe1: Running post initialization…
Jun 25 14:42:47 pbx kernel: wanpipe1: Remora config done!
Jun 25 14:42:47 pbx kernel: wanpipe1: AFT Data Mux Bit Map: 0x01234567
Jun 25 14:42:47 pbx kernel: wanpipe1: Front End Interface Ready 0x00000000
Jun 25 14:42:47 pbx kernel: wanpipe1: Register EC interface wanec1 (usage 1, max ec chans 32)!
Jun 25 14:42:47 pbx kernel: wanpipe1: Configuring Device :wanpipe1 FrmVr=11
Jun 25 14:42:47 pbx kernel: wanpipe1: Global MTU = 1500
Jun 25 14:42:47 pbx kernel: wanpipe1: Global MRU = 1500
Jun 25 14:42:47 pbx kernel: wanpipe1: Data Mux Map = 0x01234567
Jun 25 14:42:47 pbx kernel: wanpipe1: Rx CRC Bytes = 0
Jun 25 14:42:47 pbx kernel: wanpipe1: Global TDM Int = Disabled
Jun 25 14:42:47 pbx kernel: wanpipe1: Global TDM Ring= Disabled
Jun 25 14:42:47 pbx kernel: wanpipe1: Global TDM HW DTMF = Disabled
Jun 25 14:42:47 pbx kernel: wanpipe1: IRQ Throttle Period=1 Timeout=10
Jun 25 14:42:47 pbx kernel: wanpipe1: TDMV Span = 1 : Enabled
Jun 25 14:42:47 pbx kernel: wanpipe1: RTP TAP = Disabled
Jun 25 14:42:47 pbx kernel: wanpipe1: Configuring Interface: w1g1
Jun 25 14:42:47 pbx kernel: wanpipe1:w1g1: Running in TDM Voice Zaptel Mode.
Jun 25 14:42:47 pbx kernel: wanpipe1: Registering TDMV FXS iface to module 1!
Jun 25 14:42:47 pbx kernel: wanpipe1: MRU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: MTU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: HDLC Eng :Off (Transparent)
Jun 25 14:42:48 pbx kernel: wanpipe1: Data Mux Ctrl :On
Jun 25 14:42:48 pbx kernel: wanpipe1: Active Ch Map :0x00000001
Jun 25 14:42:48 pbx kernel: wanpipe1: First TSlot :0
Jun 25 14:42:48 pbx kernel: wanpipe1: DMA/Len/Chain/EC :4/1024/Off/On
Jun 25 14:42:48 pbx kernel:
Jun 25 14:42:48 pbx kernel: wanpipe1: Configuring Interface: w1g1
Jun 25 14:42:48 pbx kernel: wanpipe1:w1g1: Running in TDM Voice Zaptel Mode.
Jun 25 14:42:48 pbx kernel: wanpipe1: Registering TDMV FXS iface to module 2!
Jun 25 14:42:48 pbx pcscd: pcscdaemon.c:507:main() pcsc-lite 1.4.4 daemon ready.
Jun 25 14:42:48 pbx kernel: wanpipe1: MRU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: MTU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: HDLC Eng :Off (Transparent)
Jun 25 14:42:48 pbx kernel: wanpipe1: Data Mux Ctrl :On
Jun 25 14:42:48 pbx kernel: wanpipe1: Active Ch Map :0x00000002
Jun 25 14:42:48 pbx kernel: wanpipe1: First TSlot :1
Jun 25 14:42:48 pbx kernel: wanpipe1: DMA/Len/Chain/EC :4/1024/Off/On
Jun 25 14:42:48 pbx kernel:
Jun 25 14:42:48 pbx kernel: wanpipe1: Configuring Interface: w1g1
Jun 25 14:42:48 pbx kernel: wanpipe1:w1g1: Running in TDM Voice Zaptel Mode.
Jun 25 14:42:48 pbx kernel: wanpipe1: Registering TDMV FXO iface to module 3!
Jun 25 14:42:48 pbx kernel: wanpipe1: MRU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: MTU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: HDLC Eng :Off (Transparent)
Jun 25 14:42:48 pbx kernel: wanpipe1: Data Mux Ctrl :On
Jun 25 14:42:48 pbx kernel: wanpipe1: Active Ch Map :0x00000004
Jun 25 14:42:48 pbx kernel: wanpipe1: First TSlot :2
Jun 25 14:42:48 pbx kernel: wanpipe1: DMA/Len/Chain/EC :4/1024/Off/On
Jun 25 14:42:48 pbx kernel:
Jun 25 14:42:48 pbx kernel: wanpipe1: Configuring Interface: w1g1
Jun 25 14:42:48 pbx kernel: wanpipe1:w1g1: Running in TDM Voice Zaptel Mode.
Jun 25 14:42:48 pbx kernel: wanpipe1: Configuring TDMV Master dev w1g1
Jun 25 14:42:48 pbx kernel: wanpipe1: Registering TDMV FXO iface to module 4!
Jun 25 14:42:48 pbx kernel: wanpipe1: MRU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: MTU :8
Jun 25 14:42:48 pbx kernel: wanpipe1: HDLC Eng :Off (Transparent)
Jun 25 14:42:48 pbx kernel: wanpipe1: Data Mux Ctrl :On
Jun 25 14:42:48 pbx kernel: wanpipe1: Active Ch Map :0x00000008
Jun 25 14:42:48 pbx kernel: wanpipe1: First TSlot :3
Jun 25 14:42:48 pbx kernel: wanpipe1: DMA/Len/Chain/EC :4/1024/Off/On
Jun 25 14:42:48 pbx kernel:
Jun 25 14:42:48 pbx kernel: wanpipe1: ALAW override parameter detected. Device will be operating in ALAW
Jun 25 14:42:48 pbx kernel: wanpipe1: Battery Threshhold 3 (3)
Jun 25 14:42:48 pbx kernel: wanpipe1: Battery Debounce 16 (16)
Jun 25 14:42:48 pbx kernel: wanpipe1: Wanpipe device is registered to Zaptel span # 1!
Jun 25 14:42:48 pbx kernel: wanpipe1: AFT communications enabled!
Jun 25 14:42:48 pbx kernel: wanpipe1: AFT Per Port TDM Intr (swring)
Jun 25 14:42:48 pbx kernel: wanpipe1: Clear Echo Canceller chip reset.
Jun 25 14:42:48 pbx kernel: wanec1: Opening HW Echo Canceller (NoiseRed=Off)
Jun 25 14:42:48 pbx kernel: Registered tone zone 0 (United States / North America)
…

// Setup trunk to ZAP/3 (g0 --group0) (thats where my telco line is plugged in).
// Setup outbound route pointing to ZAP/3 with dialplan 9|.
// Setup two IAX extensions xxa and xxb mapping to channel 1 and 2 (group=1)
// respectively.
// Setup two SIPgeneric extensions xxc and xxd on basic ALAW 711/723.

// “YES” the molex power connector is connected to the Sangoma Card.
// Plugged two standard analog phones into channel 1 & 2.

// I get battery static but no pbx tone on the analog phones.
// I can call between SIP extentions but cannot call between IAX extensions.

// I cannot dialout, I get;

“== Everyone is busy/congested at this time (1:0/0/1) – Executing [s@macro-dial:8] Set(“SIP/10 b7813228”, “DIALSTATUS=CHANUNAVAIL”) in new stack”

A pointer in the right direction would really be appreciated.

Thanks in advance

[sipman]

WOW, no response in 48hrs!.

O.K. I forgot to mention the asterisk version if no-one gathered from FreePBX 2.4.x that I am running here is;
Asterisk 1.4.18.1, Copyright © 1999 - 2008 Digium, Inc. and others.

Further to the above and after some more reading up on the matter,
I was beginning to suspect irq or port clashes so I checked the folowing;

root@pbx:~ $ cat /proc/interrupts
CPU0 CPU1
0: 38130346 106034 IO-APIC-edge timer
1: 3 0 IO-APIC-edge i8042
8: 2 1 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
12: 0 4 IO-APIC-edge i8042
50: 28199 0 PCI-MSI eth1
169: 12391 38202204 IO-APIC-level uhci_hcd:usb3, wanpipe1, eth0
201: 0 1 IO-APIC-level uhci_hcd:usb4, uhci_hcd:usb6
209: 1 1 IO-APIC-level ehci_hcd:usb1
217: 0 0 IO-APIC-level ehci_hcd:usb2, uhci_hcd:usb5
225: 162166 3127 IO-APIC-level uhci_hcd:usb7, libata, libata
NMI: 0 0
LOC: 37610720 37610728
ERR: 0
MIS: 0

//and

root@pbx:~ $: lspci -vb

02:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card
Subsystem: NEC Corporation Unknown device 1100
Flags: bus master, medium devsel, latency 255, IRQ 11
Memory at fe8f0000 (32-bit, non-prefetchable)

04:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
Memory at fe5c0000 (32-bit, non-prefetchable)
Memory at fe5e0000 (32-bit, non-prefetchable)
I/O ports at dcc0
Expansion ROM at fe600000 [disabled]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device

// it would appear that the usb, eth0 and wanpipe1 share both the physical and assigned irq.
//a little concerning is that Trixbox distro (2.6.10 to 2.6.2)and wanpipe drivers load fine on
//the same hardware and WORK!, the only reason I would like to change is every time they “Fonality”
//do a upgrade there is a 98% probability that it will break your box!!- well that is what I experienced in my case.
//and after the XXXth time of fixing the installation I decided it was time to change to something possibly more stable (amongst many reasons, FreepBX have a complete Os distro).
//hence FreePBX, now there is just fustration and no solution!
//if no-one can help me here it would appear FreePBX distro of asterisk does not have strategic partnerships with the likes of Sangoma or not very many people have used sangoma with FreePBX as it is a Digium Forte!.
//ANY response here would be appreciated.

[fskrotzki]

Yes you will have IRQ issues specially when the card is sharing with the NIC but that might not be the root cause here.

Let me ask a Simple question:

This is a Sangnoma card and they have excellent support, it’s part of what you pay for when you buy there card. Why not call them and get that part of the issue all straightened out first?

Next As a official statement FreePBX is a software bundle and layer that sits on top of a working copy of asterisk, and we assume that everything under it is working fine. So we really don’t have any reason to support hardware cards as asterisk has to work with the m first for us to see it (i.e. if asterisk see’s it fine then we’ll see it fine). Now saying that does not mean we will not or don’t but please try and remember these things.

1. We are a layer above the issue and assume you have it working.
2. This forum is Free Support by users who want to or can help other users NOT a manditory technical support help line. If that is what is needed please see paid support on the site where you WILL get exactly what you are seeking.
3. I’d help but I have not used Sangnoma hardware (Digium, IAX and SIP trunks) so don’t know the details of how to verify that things are actually working.
4. In the Northern part of the US, Grade Schools just let out this week and if most communities are anything like mine 50% of them are now on vacation. I saw cars, trailers, campers, and RV’s waiting at my kids school for it to end so they could grab the kids and drive/fly away on vacation.

So questions you need to ask yourself.
If the Sangnoma drivers can see it, can asterisk? Have you checked and verified that asterisk can see it because if it can’t FreePBX surely will not.

Assuming you can see the card have you created a trunk in FreePBX? because if there is no trunk defined in FreePBX then it will not touch it.

Based on the infor you provided you are using a early version of FreePBX 2.4 WHY? either use the latest version of FreePBX and/or since this is a new box please start with the latest 2.5.1.x as they are working on releasing 2.6 shortly and you’ll already be two generations behind, which if this was a old in production box would be one thing but since it’s a new build don’t start behind the eight ball.

[sipman]

Thanks all the same but it is not what I am looking for.