Sangoma B600 in new System 60 dead on arrival?

Hi,

We recently purchased a FreePBX Phone System 60 with a Sangoma B600DE card. The appliance came with the card installed (and the mounting brackets, which were bent). The ports on the card do not show up in the DADHDI module. The system is up-to-date and Sangoma settings seem to be correct in the DAHDI module – use wanpipe in DAHDI/Digium mode and T1 mode.

When I run fwconsole restart, there is an error in the output:

[[email protected] ~]# fwconsole restart
Running FreePBX shutdown...

Checking Asterisk Status...
Run Pre-Asterisk Shutdown Hooks
Restapps daemon stopped
Stopping UCP Server
Stopped UCP Server
XMPP Server was not running
Stopping Zulu Server
Stopped Zulu Server

Shutting down Asterisk Gracefully...
Press C to Cancel
Press N to shut down NOW
Stopping Asterisk...
 120/120 [============================] 100%
Asterisk Stopped Successfuly

Running Post-Asterisk Stop Scripts
Stopping Wanrouter for Sangoma Cards
Wanrouter Stopped
Stopping DAHDi for Digium Cards
DAHDi Stopped
Running VQPlus Hooks
Stopping Queue Callback Daemon
Queue Callback Daemon Stopped
Running FreePBX startup...
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Setting Permissions...
 34733/34733 [============================] 100%
Finished setting permissions

Checking Asterisk Status...
Run Pre-Asterisk Hooks
Starting Wanrouter for Sangoma Cards
Wanrouter Failed: The command "/usr/sbin/wanrouter start" failed.
Exit Code: 1(General error)

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-600 configured on slot:4 bus:8 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-2016-03-17.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...
Current boot level is 3

Wanrouter boot scripts configuration...

Removing existing wanrouter boot scripts...OK
Verifying Dahdi boot scripts...
Verifying Dahdi boot scripts...Enabled (level:13)
Verifying Dahdi shutdown scripts...Enabled (level:87)
Enabling wanrouter boot scripts ...(level:12)
Enabling wanrouter shutdown scripts ...(level:86)
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 ... 
Loading DAHDI hardware modules:
  wct4xxp:  [  OK  ]
  wcte43x:  [  OK  ]
  wcte12xp:  [  OK  ]
  wcte13xp:  [  OK  ]
  wct1xxp:  [  OK  ]
  wcte11xp:  [  OK  ]
  r1t1:  [  OK  ]
  rxt1:  [  OK  ]
  wctdm24xxp:  [  OK  ]
  wcaxx:  [  OK  ]
  wcfxo:  [  OK  ]
  wctdm:  [  OK  ]
  rcbfx:  [  OK  ]
  wcb4xxp:  [  OK  ]
  wctc4xxp:  [  OK  ]
  xpp_usb:  [  OK  ]

Running dahdi_cfg:  [  OK  ]

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


0 channels to configure.




Error Output:
================


	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: unknown interface: No such device
DAHDI Tools Version - 2.11.0

DAHDi: Already started
Running Sysadmin Hooks
Restarting fail2ban
fail2ban Restarted

Starting Asterisk...
 100/100 [============================] 100%
Asterisk Started on  3195

Running Post-Asterisk Scripts
Running Restapps Hooks
Starting Restapps daemon
Restapps daemon done
Starting UCP Server
Started UCP Server
Running VQPlus Hooks
Starting Queue Callback Daemon
Queue Callback Daemon Started
Running XMPP Hooks
Starting XMPP Server
XMPP Server Started

Looking at /var/log/wanrouter:

Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
 * Reading section [devices]...
 * Shutting down WAN device wanpipe1 ...
Done
ok
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 8
 * 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

and /var/log/messages:

Mar 17 11:57:06 pbx kernel: WANPIPE(tm) Hardware Support Module  7.0.16.0 (c) 1994-2013 Sangoma Technologies Inc
Mar 17 11:57:06 pbx kernel: usbcore: registered new interface driver sdlausb
Mar 17 11:57:06 pbx kernel: dahdi: Version: 2.11.0
Mar 17 11:57:06 pbx kernel: dahdi: Telephony Interface Registered on major 196
Mar 17 11:57:06 pbx kernel: WANPIPE(tm) Interface Support Module 7.0.16.0 (c) 1994-2013 Sangoma Technologies Inc
Mar 17 11:57:07 pbx kernel: WANPIPE(tm) Multi-Protocol WAN Driver Module 7.0.16.0 (c) 1994-2013 Sangoma Technologies Inc
Mar 17 11:57:07 pbx kernel: wanpipe: Probing for WANPIPE hardware.
Mar 17 11:57:07 pbx kernel: wanpipe: AFT-B600-SH PCI FXO/FXS card found (HDLC rev.5), cpu(s) 1, bus #8, slot #4, irq #18
Mar 17 11:57:07 pbx kernel: wanpipe: Allocating maximum 1 devices: wanpipe1 - wanpipe1.
Mar 17 11:57:07 pbx kernel: WANPIPE: TDM Codecs Initialized
Mar 17 11:57:07 pbx kernel: WANPIPE(tm) Socket API Module 7.0.16.0 (c) 1994-2013 Sangoma Technologies Inc
Mar 17 11:57:07 pbx kernel: NET: Registered protocol family 25
Mar 17 11:57:07 pbx kernel: WANPIPE(tm) WANEC Layer 7.0.16.0 (c) 1995-2006 Sangoma Technologies Inc.
Mar 17 11:57:07 pbx kernel: wanec_create_dev: Registering Wanpipe ECDEV Device!
Mar 17 11:57:07 pbx kernel: wanpipe1: Starting WAN Setup
Mar 17 11:57:07 pbx kernel: 
Mar 17 11:57:07 pbx kernel: Processing WAN device wanpipe1...
Mar 17 11:57:07 pbx kernel: wanpipe1: Locating: A200/A400/B600/B700/B800/B610 card, CPU A, PciBus=8, PciSlot=4
Mar 17 11:57:07 pbx kernel: wanpipe1: Found: A200/A400/B600/B700/B800/B610 card, CPU A, PciBus=8, PciSlot=4, Port=0
Mar 17 11:57:07 pbx kernel: wanpipe1: AFT PCI memory at 0xD0600000
Mar 17 11:57:07 pbx kernel: wanpipe1: IRQ 18 allocated to the AFT PCI card
Mar 17 11:57:07 pbx kernel: wanpipe1: Starting AFT B600 Hardware Init.
Mar 17 11:57:07 pbx kernel: wanpipe1: Enabling front end link monitor
Mar 17 11:57:07 pbx kernel: wanpipe1: Global Chip Configuration: used=1 used_type=1
Mar 17 11:57:07 pbx kernel: wanpipe1: Configuring for internal oscillator
Mar 17 11:57:07 pbx kernel: wanpipe1: Global Front End Configuration!
Mar 17 11:57:07 pbx kernel: wanpipe1: Configuring FXS/FXO Front End ...
Mar 17 11:57:07 pbx kernel: wanpipe1: Module 1: Installed -- Auto FXO (FCC mode)!
Mar 17 11:57:08 pbx kernel: wanpipe1: Module 2: Installed -- Auto FXO (FCC mode)!
Mar 17 11:57:08 pbx kernel: wanpipe1: Module 3: Installed -- Auto FXO (FCC mode)!
Mar 17 11:57:08 pbx kernel: wanpipe1: Module 4: Installed -- Auto FXO (FCC mode)!
Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Failed to powerup within 1000 ms (0V : 72V)!
Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Did you remember to plug in the power cable?
Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Unable to do INITIAL ProSLIC powerup!
Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Retry configuration...
Mar 17 11:57:10 pbx kernel: wanpipe1: Module 5: Failed to powerup within 1000 ms (0V : 72V)!
Mar 17 11:57:10 pbx kernel: wanpipe1: Module 5: Did you remember to plug in the power cable?
Mar 17 11:57:10 pbx kernel: wanpipe1: Module 5: Unable to do INITIAL ProSLIC powerup!
Mar 17 11:57:10 pbx kernel: wanpipe1: Module 5: FXS failed!
Mar 17 11:57:10 pbx kernel: wanpipe1: 1 FXO/FXS module(s) are failed to initialize!
Mar 17 11:57:10 pbx kernel: wanpipe1: Failed Front End configuration!
Mar 17 11:57:10 pbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)
Mar 17 11:57:10 pbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)
Mar 17 11:57:10 pbx kernel: wanpipe1: TASKQ Not Running
Mar 17 11:57:10 pbx kernel: wanpipe1: Global Chip Shutdown Usage=1, Used_type_cnt=1
Mar 17 11:57:10 pbx kernel: wanpipe1: Master shutting down
Mar 17 11:57:11 pbx kernel: dahdi_transcode: Loaded.
Mar 17 11:57:11 pbx kernel: INFO-xpp: revision Unknown MAX_XPDS=64 (8*8)
Mar 17 11:57:11 pbx kernel: INFO-xpp: FEATURE: with PROTOCOL_DEBUG
Mar 17 11:57:11 pbx kernel: INFO-xpp: FEATURE: with sync_tick() from DAHDI
Mar 17 11:57:11 pbx kernel: INFO-xpp_usb: revision Unknown

The port lights on the card turn on, but I opened the appliance top cover to take a look. Everything seemed ok:

Does anybody have any further thoughts or suggestions? This appears to be a hardware issue with the new appliance, but I cannot find the proper support channel on the Sangoma website to get this issue resolved. Thanks in advance for your time.

That stuff looks important.

Did you double check and make sure that all of the power cables (including any weird little extra cables) are all plugged in.

In Germany, we used to tell people to unplug and re-plug their computers. It’s amazing how many times the response was “that did it.” I’d suggest unplugging and re-plugging everything, just to make sure something hasn’t popped loose.

I agree that the bit you quoted looks important. I did double-check all of the connections and, in fact, most of them are hot-glued. Nothing seems loose to me.

agreed - this kinda spells it out …

Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Failed to powerup within 1000 ms (0V : 72V)!
Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Did you remember to plug in the power cable?
Mar 17 11:57:09 pbx kernel: wanpipe1: Module 5: Unable to do INITIAL ProSLIC powerup!

I like the forums as much as anybody but shouldnt you be speaking with someone in support for Sangoma ? that’s where i would start …

As I stated in the post I was having trouble finding a phone number to call – I agree with you though. I’ve finally found a phone number but still have not been able to reach anybody…

http://ussupport.sangoma.com

We have recently discovered an issue with the B600 series with our System 60’s.

Please open a support ticket at https://ussupport.sangoma.com for further assistance.

Thanks, I will look into creating a support ticket.

Having the same issue with a 102e…actually the second card. I’ve been working with support for several weeks and they haven’t had anything that was helpful–they RMA’d the first card and second one is identical result–not detected.

Has anyone had success resolving this? Or…does anyone have a good recommendation for an alternative to Sangoma/Digium for dedicated FreePBX servers??

what are your wanpipe and dahdi versions?

For the modules? I see 14.0.1.3 for the Dahdi, but don’t see wanpipe anywhere–its constantly failing to detect.

Now they have determined that both PCI slots in the brand new motherboard must be bad…sounds like a stretch.

No Sangoma voice compatible cards found/configured

Generating configuration files for FreePBX
modprobe: ERROR: could not insert ‘wanpipe’: No such device

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

No Sangoma ISDN T1/E1 cards detected
-bash-4.2#
-bash-4.2# lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 0e)
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e)
00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 (rev 0e)
00:1d.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB EHCI (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
01:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
02:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
-bash-4.2# yum update -y
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
No packages marked for update
-bash-4.2#