Solved - Brand New FPBX 60 with A200 - Unable to configure

FreePBX Hardware
1

I have a brand new FPBX 60 which was shipped with the A200 card installed, but I am unable to get it to show up in the DAHDI config in the GUI. Card is listed if I do lspci from the console.

I see some lines that might look relevant in the logs, but I am not sure what the deal is. This came directly from Sangoma with the card installed in the unit.

/var/log/messages:

w1g1: ERROR while getting interface flags: No such device

/var/log/wanrouter:

Apr 19 13:47:26 pbx kernel: wanpipe1: Configuring FXS/FXO Front End ...
Apr 19 13:47:26 pbx kernel: Error: wanpipe1: No FXO/FXS modules are found!
Apr 19 13:47:26 pbx kernel: wanpipe1: Failed Front End configuration!

FULL LOGS

When I do fwconsole restart, this is what I am seeing:

Running FreePBX startup...
Running Asterisk pre from Dahdiconfig module
Writing out default Sangoma conf
Starting Wanrouter for Sangoma Cards
Wanrouter Failed: The command "/usr/sbin/wanrouter start" failed.

Exit Code: 1(General error)

Working directory: /etc/wanpipe

Output:
================

Executing DAHDI config T1

########################################################################
#                          Sangoma Wanpipe                             #
#        Dahdi/Zaptel/SMG/TDMAPI/BOOT Configuration Script             #
#                             v2.51                                    #
#                     Sangoma Technologies Inc.                        #
#                        Copyright(c) 2016.                            #
########################################################################

-------------------------------------------------------
Configuring T1/E1 cards [A101/A102/A104/A108/A116/T116]
-------------------------------------------------------

No Sangoma ISDN T1/E1 cards detected

-------------------------------------------
Configuring ISDN BRI cards [A500/B500/B700]
-------------------------------------------

No Sangoma ISDN BRI cards detected

------------------------------------
Configuring GSM cards [W400]
------------------------------------

No Sangoma GSM cards detected

------------------------------------
Configuring analog cards [A200/A400/B600/B610/B700/B800]
------------------------------------
AFT-200 configured on slot:4 bus:7 span:1

Analog card configuration complete

------------------------------------
Configuring USB devices [U100]
------------------------------------

###################################################################
#                             SUMMARY                             #
###################################################################

  0 T1/E1 port(s) detected, 0 configured
  0 ISDN BRI port(s) detected, 0 configured
  1 analog card(s) detected, 1 configured
  0 GSM card(s) detected, 0 configured
  0 usb device(s) detected, 0 configured

Configurator will create the following files:
        1. Wanpipe config files in /etc/wanpipe
        2. Dahdi config file /etc/dahdi/system.conf


Your original configuration files will be saved to:
        1. /etc/dahdi/system.conf.bak

Your configuration has been saved in /etc/wanpipe/debug-2024-04-19.tgz.
When requesting support, email this file to [email protected]


###################################################################


Asterisk is not running...

Removing old configuration files...

Copying new Wanpipe configuration files...

Wanrouter start complete...
Removing old stop/start scripts....
Installing new Dahdi start script....
Removing old smg_ctrl boot.....OK
Removing old smg_ctrl_safe boot.....OK
Sangoma cards configuration complete, exiting...

Starting up device: wanpipe1
Configuring interfaces: w1g1
done.
Waiting for Dahdi /dev/dahdi ...
Starting dahdi (via systemctl):  [  OK  ]

DAHDI Version: 2.11.1
Echo Canceller(s):
Configuration
======================


0 channels to configure.




Error Output:
================
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.eth0.stable_secret"
sysctl: reading key "net.ipv6.conf.eth1.stable_secret"
sysctl: reading key "net.ipv6.conf.eth2.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"


        wanconfig: WAN device wanpipe1 driver load failed !!
                 : ioctl(wanpipe1,ROUTER_SETUP) failed:
                 :      22 - Invalid argument


        Wanpipe driver did not load properly
        Please check /var/log/wanrouter and
        /var/log/messages for errors

w1g1: ERROR while getting interface flags: No such device
DAHDI Tools Version - 2.11.1

DAHDi: Already started

OUTPUT OF /var/log/wanrouter :

Starting up device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
 * Parsing configuration file /etc/wanpipe/wanpipe1.conf ...
 * Reading section [devices]...
 * Reading section [wanpipe1]...
 * Reading section [interfaces]...
 * w1g1 to used by TDM_VOICE
 * Reading section [w1g1]...
 * Configuring device wanpipe1 (no description)
 * Setting CARD_TYPE to AFT
 * Setting S514CPU to A
 * Setting COMMPORT to PRI
 * Setting AUTO_PCISLOT to NO
 * Setting PCISLOT to 4
 * Setting PCIBUS to 7
 * Setting FE_MEDIA to FXO/FXS
 * Setting TDMV_LAW to MULAW
 * Setting TDMV_OPERMODE to FCC
 * Setting RM_BATTTHRESH to 3
 * Setting RM_BATTDEBOUNCE to 16
 * Setting FE_NETWORK_SYNC to NO
 * Setting MTU to 1500
 * Setting UDPPORT to 9000
 * Setting TTL to 255
 * Setting IGNORE_FRONT_END to NO
 * Setting TDMV_SPAN to 1
 * Setting TE_AIS_MAINTENANCE to NO
 * Setting TDMV_HW_DTMF to YES
 * Setting TDMV_HW_FAX_DETECT to NO
 * Setting HWEC_OPERATION_MODE to OCT_NORMAL
 * Setting HWEC_DTMF_REMOVAL to NO
 * Setting HWEC_NOISE_REDUCTION to NO
 * Setting HWEC_ACUSTIC_ECHO to NO
 * Setting HWEC_NLP_DISABLE to NO
 * Setting HWEC_TX_AUTO_GAIN to 0
 * Setting HWEC_RX_AUTO_GAIN to 0
 * Setting HWEC_TX_GAIN to 0
 * Setting HWEC_RX_GAIN to 0
 * Setting RM_FAKE_POLARITY to NO
 * Setting RM_FAKE_POLARITY_THRESHOLD to 16000
 * Setting RM_FAKE_POLARITY_CIDTIMER to 400
 * Setting RM_FAKE_POLARITY_CIDTIMEOUT to 4000
 * Setting RM_RING_DEBOUNCE to 0

RELEVANT OUTPUT OF /var/log/messages :

Apr 19 13:47:26 pbx kernel: dahdi: Version: 2.11.1
Apr 19 13:47:26 pbx kernel: dahdi: Telephony Interface Registered on major 196
Apr 19 13:47:26 pbx kernel: WANPIPE(tm) Hardware Support Module  7.0.32.0 (c) 1994-2016 Sangoma Technologies Inc
Apr 19 13:47:26 pbx kernel: usbcore: registered new interface driver sdlausb
Apr 19 13:47:26 pbx kernel: WANPIPE(tm) Interface Support Module 7.0.32.0 (c) 1994-2016 Sangoma Technologies Inc
Apr 19 13:47:26 pbx kernel: WANPIPE(tm) Multi-Protocol WAN Driver Module 7.0.32.0 (c) 1994-2016 Sangoma Technologies Inc
Apr 19 13:47:26 pbx kernel: wanpipe: Probing for WANPIPE hardware.
Apr 19 13:47:26 pbx kernel: wanpipe: AFT-A200-SH PCIe FXO/FXS card found (HDLC rev.13), cpu(s) 1, bus #7, slot #4, irq #16
Apr 19 13:47:26 pbx kernel: wanpipe: Allocating maximum 1 devices: wanpipe1 - wanpipe1.
Apr 19 13:47:26 pbx kernel: WANPIPE: TDM Codecs Initialized
Apr 19 13:47:26 pbx kernel: WANPIPE(tm) Socket API Module 7.0.32.0 (c) 1994-2016 Sangoma Technologies Inc
Apr 19 13:47:26 pbx kernel: NET: Registered protocol family 25
Apr 19 13:47:26 pbx kernel: WANPIPE(tm) WANEC Layer 7.0.32.0 (c) 1995-2006 Sangoma Technologies Inc.
Apr 19 13:47:26 pbx kernel: wanec_create_dev: Registering Wanpipe ECDEV Device!
Apr 19 13:47:26 pbx kernel: wanpipe1: Starting WAN Setup
Apr 19 13:47:26 pbx kernel:
Apr 19 13:47:26 pbx kernel: Processing WAN device wanpipe1...
Apr 19 13:47:26 pbx kernel: wanpipe1: Locating: A200/A400/B600/B700/B800/B610 card, CPU A, PciBus=7, PciSlot=4
Apr 19 13:47:26 pbx kernel: wanpipe1: Found: A200/A400/B600/B700/B800/B610 card, CPU A, PciBus=7, PciSlot=4, Port=0
Apr 19 13:47:26 pbx kernel: wanpipe1: AFT PCI memory at 0xD0600000
Apr 19 13:47:26 pbx kernel: wanpipe1: IRQ 16 allocated to the AFT PCI card
Apr 19 13:47:26 pbx kernel: wanpipe1: Starting AFT Analog Hardware Init.
Apr 19 13:47:26 pbx kernel: wanpipe1: Enabling front end link monitor
Apr 19 13:47:26 pbx kernel: wanpipe1: Global Chip Configuration: used=1 used_type=1
Apr 19 13:47:26 pbx kernel: wanpipe1: Global Front End Configuration!
Apr 19 13:47:26 pbx kernel: wanpipe1: Configuring FXS/FXO Front End ...
Apr 19 13:47:26 pbx kernel: Error: wanpipe1: No FXO/FXS modules are found!
Apr 19 13:47:26 pbx kernel: wanpipe1: Failed Front End configuration!
Apr 19 13:47:26 pbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)
Apr 19 13:47:26 pbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)
Apr 19 13:47:26 pbx kernel: wanpipe1: TASKQ Not Running
Apr 19 13:47:26 pbx kernel: wanpipe1: Global Chip Shutdown Usage=1, Used_type_cnt=1
Apr 19 13:47:26 pbx kernel: wanpipe1: Master shutting down
Apr 19 13:47:27 pbx systemd: Starting LSB: DAHDI kernel modules...
Apr 19 13:47:28 pbx dahdi: Loading DAHDI hardware modules:
Apr 19 13:47:28 pbx dahdi: wct4xxp:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wcte43x:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wcte12xp:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wcte13xp:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wct1xxp:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wcte11xp:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: r1t1:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: rxt1:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wctdm24xxp:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wcaxx:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wcfxo:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: wctdm:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: rcbfx:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: zaphfc:  modprobe: FATAL: Module zaphfc not found.
Apr 19 13:47:28 pbx dahdi: [FAILED]
Apr 19 13:47:28 pbx dahdi: wcb4xxp:  [  OK  ]
Apr 19 13:47:28 pbx kernel: dahdi_transcode: Loaded.
Apr 19 13:47:28 pbx dahdi: wctc4xxp:  [  OK  ]
Apr 19 13:47:28 pbx kernel: INFO-xpp: revision Unknown MAX_XPDS=64 (8*8)
Apr 19 13:47:28 pbx kernel: INFO-xpp: FEATURE: with PROTOCOL_DEBUG
Apr 19 13:47:28 pbx kernel: INFO-xpp: FEATURE: with sync_tick() from DAHDI
Apr 19 13:47:28 pbx kernel: INFO-xpp_usb: revision Unknown
Apr 19 13:47:28 pbx kernel: usbcore: registered new interface driver xpp_usb
Apr 19 13:47:28 pbx dahdi: xpp_usb:  [  OK  ]
Apr 19 13:47:28 pbx dahdi: Running dahdi_cfg:  [  OK  ]
Apr 19 13:47:28 pbx systemd: Started LSB: DAHDI kernel modules.
2

Maybe the modules came loose in transit.

3

That’s almost the answer, but it’s a step beyond that. Just for background, I generally only do SIP Trunks with systems I implement. This is the first of these that I have done where the client is sticking with their analog lines.

The system was shipped to me with the A200 card slotted into the appliance, screwed down, and appeared to be ready to go. After struggling with this for some time, I took a trip onsite to look into it further, and I found that neither slot on the A200 had a module plugged in at all! I wish there was some documentation available for this stuff, as I have been on the struggle bus trying to find anything about this Sangoma hardware. Fortunately I did not yet take out the trash from the install, because I found the FXO module in a small static bag inside a small cardboard envelope.

I pulled the card, installed the module into the card, plugged it all back in and booted, and I am now seeing the two FXO ports I expect in the GUI under the DAHDi config page. I should be all set now.

2 Likes
4

Glad this was solved. Reminds me that once I got burgers to go from a restaurant. Got home and neither my friend nor I could find the patties. We called the restaurant, and they told us to look in the secondary container. In there were the patties. They send them to-go separately so the bun doesn’t get soggy. Thoughtful, but a heads up would have been good!

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.