Here's the messages log. There's a line that says ERROR: Unsupported DS E1 CHIP (00:00)<br><br>Feb 14 10:09:19 server14 kernel: [6011515.237242] dahdi: Telephony Interface Registered on major 196<br>Feb 14 10:09:19 server14 kernel: [6011515.237246] dahdi: Version: 2.4.0<br>
Feb 14 10:09:19 server14 kernel: [6011515.244707] WANPIPE(tm) Hardware Support Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>Feb 14 10:09:19 server14 kernel: [6011515.245010] usbcore: registered new interface driver sdlausb<br>
Feb 14 10:09:19 server14 kernel: [6011515.251320] WANPIPE(tm) Interface Support Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>Feb 14 10:09:19 server14 kernel: [6011515.262373] WANPIPE(tm) Multi-Protocol WAN Driver Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>
Feb 14 10:09:19 server14 kernel: [6011515.262376] wanpipe: Probing for WANPIPE hardware.<br>Feb 14 10:09:19 server14 kernel: [6011515.264214] wanpipe: AFT-A104-SH PCIe T1/E1 card found (HDLC (DS) rev.37), cpu(s) 1, line(s) 4, bus #4, slot #4, irq #16<br>
Feb 14 10:09:19 server14 kernel: [6011515.264228] wanpipe: Allocating maximum 4 devices: wanpipe1 - wanpipe4.<br>Feb 14 10:09:19 server14 kernel: [6011515.264775] WANPIPE: TDM Codecs Initialized<br>Feb 14 10:09:19 server14 kernel: [6011515.271478] WANPIPE(tm) Socket API Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>
Feb 14 10:09:19 server14 kernel: [6011515.271481] NET: Registered protocol family 25<br>Feb 14 10:09:19 server14 kernel: [6011515.283341] WANPIPE(tm) WANEC Layer 3.5.18.0 (c) 1995-2006 Sangoma Technologies Inc.<br>Feb 14 10:09:19 server14 kernel: [6011515.283344] wanec_create_dev: Registering Wanpipe ECDEV Device!<br>
Feb 14 10:10:32 server14 kernel: [6011588.876265] wanec_remove_dev: Unregistering Wanpipe ECDEV Device!<br>Feb 14 10:10:32 server14 kernel: [6011588.876346] WANEC Layer: Unloaded<br>Feb 14 10:10:32 server14 kernel: [6011588.879218] af_wanpipe: Unregistering Wanpipe API Socket Module<br>
Feb 14 10:10:32 server14 kernel: [6011588.904829] NET: Unregistered protocol family 25<br>Feb 14 10:10:32 server14 kernel: [6011588.907606] WANPIPE: TDM Codecs unloaded.<br>Feb 14 10:10:32 server14 kernel: [6011588.907609]<br>
Feb 14 10:10:32 server14 kernel: [6011588.907610] wanpipe: WANPIPE Modules Unloaded.<br>Feb 14 10:10:32 server14 kernel: [6011588.912729] usbcore: deregistering interface driver sdlausb<br>Feb 14 10:10:32 server14 kernel: [6011588.912756] Logger TASKQ Not Running<br>
Feb 14 10:10:32 server14 kernel: [6011588.914895] dahdi: Telephony Interface Unloaded<br>Feb 14 10:11:47 server14 kernel: [6011663.492120] dahdi: Telephony Interface Registered on major 196<br>Feb 14 10:11:47 server14 kernel: [6011663.492123] dahdi: Version: 2.4.0<br>
Feb 14 10:11:47 server14 kernel: [6011663.500161] WANPIPE(tm) Hardware Support Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>Feb 14 10:11:47 server14 kernel: [6011663.500557] usbcore: registered new interface driver sdlausb<br>
Feb 14 10:11:47 server14 kernel: [6011663.505314] WANPIPE(tm) Interface Support Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>Feb 14 10:11:47 server14 kernel: [6011663.513738] WANPIPE(tm) Multi-Protocol WAN Driver Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>
Feb 14 10:11:47 server14 kernel: [6011663.513741] wanpipe: Probing for WANPIPE hardware.<br>Feb 14 10:11:47 server14 kernel: [6011663.514985] wanpipe: AFT-A104-SH PCIe T1/E1 card found (HDLC (DS) rev.37), cpu(s) 1, line(s) 4, bus #4, slot #4, irq #16<br>
Feb 14 10:11:47 server14 kernel: [6011663.514996] wanpipe: Allocating maximum 4 devices: wanpipe1 - wanpipe4.<br>Feb 14 10:11:47 server14 kernel: [6011663.515447] WANPIPE: TDM Codecs Initialized<br>Feb 14 10:11:47 server14 kernel: [6011663.522007] WANPIPE(tm) Socket API Module 3.5.18.0 (c) 1994-2010 Sangoma Technologies Inc<br>
Feb 14 10:11:47 server14 kernel: [6011663.522011] NET: Registered protocol family 25<br>Feb 14 10:11:47 server14 kernel: [6011663.534362] WANPIPE(tm) WANEC Layer 3.5.18.0 (c) 1995-2006 Sangoma Technologies Inc.<br>Feb 14 10:11:47 server14 kernel: [6011663.534366] wanec_create_dev: Registering Wanpipe ECDEV Device!<br>
Feb 14 10:11:47 server14 kernel: [6011663.543452] wanpipe1: Starting WAN Setup<br>Feb 14 10:11:47 server14 kernel: [6011663.543455]<br>Feb 14 10:11:47 server14 kernel: [6011663.543457] Processing WAN device wanpipe1...<br>
Feb 14 10:11:47 server14 kernel: [6011663.543461] wanpipe1: Locating: A101/1D/A102/2D/4/4D/8 card, CPU A, PciBus=4, PciSlot=4<br>Feb 14 10:11:47 server14 kernel: [6011663.543467] wanpipe1: Found: A101/1D/A102/2D/4/4D/8 card, CPU A, PciBus=4, PciSlot=4, Port=0<br>
Feb 14 10:11:47 server14 kernel: [6011663.543718] wanpipe1: AFT PCI memory at 0xFAFE0000<br>Feb 14 10:11:47 server14 kernel: [6011663.543721] wanpipe1: IRQ 16 allocated to the AFT PCI card<br>Feb 14 10:11:47 server14 kernel: [6011663.543733] wanpipe1: Starting AFT 2/4/8 Hardware Init.<br>
Feb 14 10:11:47 server14 kernel: [6011663.543741] wanpipe1: Enabling front end link monitor<br>Feb 14 10:11:47 server14 kernel: [6011663.543745] wanpipe1: Global Chip Configuration: used=1 used_type=1<br>Feb 14 10:11:47 server14 kernel: [6011663.547108] wanpipe1: ERROR: Unsupported DS E1 CHIP (00:00)<br>
Feb 14 10:11:47 server14 kernel: [6011663.547111] a104_global_chip_config(): 778: Error: global_config() ptr is NULL<br>Feb 14 10:11:47 server14 kernel: [6011663.547115] wanpipe1: E1 Front End unconfigation!<br>Feb 14 10:11:47 server14 kernel: [6011663.547130] wanpipe1: Enable transmit AIS alarm<br>
Feb 14 10:11:47 server14 kernel: [6011663.547168] wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)<br>Feb 14 10:11:47 server14 kernel: [6011663.547180] wanpipe1: E1 Front End unconfigation!<br>Feb 14 10:11:47 server14 kernel: [6011663.547195] wanpipe1: Enable transmit AIS alarm<br>
Feb 14 10:11:47 server14 kernel: [6011663.547234] wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down)<br>Feb 14 10:11:47 server14 kernel: [6011663.547269] wanpipe1: TASKQ Not Running<br>Feb 14 10:11:47 server14 kernel: [6011663.547271] wanpipe1: Global Chip Shutdown Usage=1, Used_type_cnt=1<br>
Feb 14 10:11:47 server14 kernel: [6011663.547274] wanpipe1: Global E1 Front End unconfigation!<br>Feb 14 10:11:47 server14 kernel: [6011663.549347] wanpipe1: Master shutting down<br><br><div class="gmail_quote">On Sat, Feb 12, 2011 at 11:33 AM, Moises Silva <span dir="ltr"><<a href="mailto:moises.silva@gmail.com">moises.silva@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">As the error suggest, try checking /var/log/messages for possible hints on what went wrong.<div>
<br></div><div>Make sure you configured the device with wancfg_dahdi script first.</div><div><br><div><font color="#888888">Moises Silva<br>Senior Software Engineer<br>
Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada<br>t. 1 905 474 1990 x128 | e. <a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a><br>
<br><br></font><div class="gmail_quote"><div><div></div><div class="h5">On Fri, Feb 11, 2011 at 1:47 AM, Roi Stork <span dir="ltr"><<a href="mailto:roi.stork@gmail.com" target="_blank">roi.stork@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">
Trying to install wanpipe 3.5.18.<br><br>No errors during compile. But when I reach the point where wanpipe and dahdi_cfg is started, I encountered an error.<br><br><div style="margin-left: 40px;"><font size="1">Starting WAN Router...<br>
Loading WAN drivers: wanpipe done.<br>Starting up device: wanpipe1<br><br><br> wanconfig: WAN device wanpipe1 driver load failed !!<br> : ioctl(wanpipe1,ROUTER_SETUP) failed:<br> : 22 - Invalid argument<br>
<br><br> Wanpipe driver did not load properly<br> Please check /var/log/wanrouter and<br> /var/log/messages for errors<br><br>Configuring interfaces: w1g1 w1g1: ERROR while getting interface flags: No<br>
such device<br><br>done.<br>/etc/wanpipe/scripts/start: 7: Syntax error: Bad for loop variable<br><br>DAHDI_SPANCONFIG failed on span 1: No such device<br>or address (6)<br></font></div><font size="1"><br></font>Dont know why I still keep getting a 'No such device' error even if the device was detected (Sangoma a104de, setup asked to configure/skip the 4 ports) before the error happened.<br>
<br></div></div><div class="im">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></div></blockquote></div><br></div></div>
<br>--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br>