search for: wanpipe1

...echocancelwhenbridged=no echotraining=yes relaxdtmf=yes rxgain=0.5 txgain=0.9 immediate=no amaflags=billing adsi=no busydetect=no callprogress=no context = zapline1 switchtype = euroisdn group=1 signalling = pri_cpe channel => 1-15 channel => 17-31 cat /proc/zaptel/1 : Span 1: WPE1/0 "wanpipe1 card 0" HDB3//CRC4 1 WPE1/0/1 Clear (In use) 2 WPE1/0/2 Clear (In use) 3 WPE1/0/3 Clear (In use) 4 WPE1/0/4 Clear (In use) 5 WPE1/0/5 Clear (In use) 6 WPE1/0/6 Clear (In use) 7 WPE1/0/7 Clear (In use) 8 WP...

...n FC7 all went okay. using sangoma a104dx on both machine. I followed the write up on http://www.voip-info.org/wiki/index.php?page=Asterisk+ss7+setup I have the cross over cable between them. however, wanpipe shows connected but the signaling link does not align. i have my configs for host A ##wanpipe1.conf [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 4 PCIBUS = 15 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME =...

...rvice ? root at example:/etc/asterisk# /etc/init.d/dahdi stop Unloading DAHDI hardware modules: ERROR: Module wanpipe is in use ERROR: Module dahdi_echocan_mg2 is in use ERROR: Module dahdi is in use by dahdi_echocan_mg2,wanpipe error root at example:/etc/asterisk# wanrouter stop Shutting down wanpipe1 interface: w1g1 Shutting down device: wanpipe2 Shutting down device: wanpipe1 wanconfig: WAN device wanpipe1 did not shutdown : ioctl(wanpipe1,ROUTER_DOWN) failed: : 16 - Device or resource busy If you router was not running ignore this mes...

I am sure many of you have seen my post asking question that I cannot seem to resolve. While the responses i have been getting have been helpful i still cannot seem to get this working 100%. So I have waving the white flag here. I give up. I need someone to come to my office and help me get this working. If anyone is interested the office is in Lexington KY. If someone is interested we can

...ta2 to Sangoma A101. I followed the instructions, and installation was successful. zttool, ztcfg, all show card is installed properly. I copied the parameters from my old working zaptel.conf, zapata.conf and zapata-auto.conf. Verified on Sangoma website that these files are correct. Also configured wanpipe1.conf. But doing all this didn't start the PRI channels. It says 'no PRI configured on span 1' on Asterisk CLI on typing 'pri show span 1'. What am I missing here? -- Zeeshan A Zakaria -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list...

...else could possibly be causing this problem? Thanks, Jaap PS -- Below are my current configuration files and debugging output: ==begin zaptel.conf ==================== loadzone=us defaultzone=us span=1,0,0,ccs,hdb3 bchan=1-15,17-31 hardhdlc=16 ==end zaptel.conf ====================== ==begin wanpipe1.conf ================== [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 4 PCIBUS = 13 FE_MEDIA = E1 FE_LCODE...

Trying to install wanpipe 3.5.18. No errors during compile. But when I reach the point where wanpipe and dahdi_cfg is started, I encountered an error. Starting WAN Router... Loading WAN drivers: wanpipe done. Starting up device: wanpipe1 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 Configuring...

...99.996193, Difference: 99.996683 [root at sitges bin]# service wanrouter stop Shutting down asterisk: [ OK ] Stopping Asterisk... Shutting down wanpipe4 interface: w4g1 Shutting down wanpipe3 interface: w3g1 Shutting down wanpipe2 interface: w2g1 Shutting down wanpipe1 interface: w1g1 Shutting down device: wanpipe4 Shutting down device: wanpipe3 Shutting down device: wanpipe2 Shutting down device: wanpipe1 No devices running, Unloading Modules [root at sitges bin]# service wanrouter start Starting WAN Router... Loading WAN drivers: wanpipe done. Starting up dev...

...text=from-zaptel group=0 signalling = fxs_ks channel => 1-4 zaptel.conf: # Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- do not hand edit # Zaptel Channels Configurations (zaptel.conf) # loadzone=us defaultzone=us #Sangoma A200 [slot:6 bus:1 span:1] fxsks=1 fxsks=2 fxsks=3 fxsks=4 wanpipe1.conf: #================================================ # WANPIPE1 Configuration File #================================================ # # Date: Mon Jul 31 17:10:23 EDT 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to e...

...ch support in the local telco, my E1 should be: E1 PRI, CAS, HDB3, NCRC4, DSS1 However if I configure the card for CAS, it will never connect. My card is currently configured (and makes only outgoing calls) as: E1 PRI, CCS, HDB3,NCRC4 (i have no idea what dss1 is or where it goes) My /etc/wanpipe/wanpipe1.conf is: [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 1 PCIBUS = 4 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME...

...waycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes relaxdtmf=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no internationalprefix=00 nationalprefix=0 overlapdial=no ;Sangoma A101 port 1 [slot:5 bus:3 span:1] <wanpipe1> switchtype=euroisdn echocancel=yes signalling=pri_cpe channel =>1-15,17-31 /etc/dahdi/system.conf: # Span 1: WPE1/0 "wanpipe1 card 0" (MASTER) HDB3/CCS/CRC4 span=1,1,0,ccs,hdb3,crc4 # termtype: te bchan=1-15,17-31 echocanceller=mg2,1-15,17-31 hardhdlc=16 # Global data loadzone...

...meone can point me in the right direction as we're trying to get rid of swyx since we're tied down by limiting software and excessive licensing costs. Thanks! Geraint pri show spans shows all spans as up and active. zap show status shows all as ok wanrouter status shows all as connected wanpipe1 and 2: [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 1 PCIBUS = 16 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME...

...MG2 as specified in DAHDI's system.conf: #autogenerated by /usr/sbin/wancfg_dahdi do not hand edit #autogenrated on 2010-12-08 #Dahdi Channels Configurations #For detailed Dahdi options, view /etc/dahdi/system.conf.bak loadzone=us defaultzone=us #Sangoma A104 port 1 [slot:2 bus:2 span:1] <wanpipe1> span=1,1,0,esf,b8zs bchan=1-23 #dchan=24 echocanceller=mg2,1-23 hardhdlc=24 And, from chan_dahdi.conf: ;Sangoma A104 port 1 [slot:2 bus:2 span:1] <wanpipe1> switchtype=national context=ldrouted group=1 echocancel=yes signalling=pri_net channel =>1-23 Any thoughts, pointers, suggest...

...on the pattest on machine 2. Am I correct in assuming that this is not a good thing? Does anyone have any other recommendations on how to validate this setup? I am running all this on ubuntu lucid, kernel 2.6.32. Asterisk version 11.5.0 Dahdi 2.6.1 Wanpipe 7.0.3 Here's a few config snippets: wanpipe1.conf (the other wanpipe.conf files are similar) [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 4 PCIBUS = 5 FE_MEDIA = E1...

...lo All Any body used sangoma card A101. I have problem with this card. My system are: Linux Redhat 8.0. asterisk 1.07 and libpri, zaptel,... i connected E1 and MF/R2 signalling. i configure HDLC and TDM Voice. this is my configure as belows: #================================================ # WANPIPE1 Configuration File #================================================ # # Date: Sun May 15 03:11:45 GMT+7 2005 # # Note: This file was generated automatically # by /usr/sbin/wancfg program. # # If you want to edit this file, it is # recommended that you use wancfg program # t...

...ch support in the local telco, my E1 should be: E1 PRI, CAS, HDB3, NCRC4, DSS1 However if I configure the card for CAS, it will never connect. My card is currently configured (and makes only outgoing calls) as: E1 PRI, CCS, HDB3,NCRC4 (i have no idea what dss1 is or where it goes) My /etc/wanpipe/wanpipe1.conf is: [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 1 PCIBUS = 4 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME...

...on? Linux voip 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others. WANPIPE Release: 3.4.1 Wanpipe Config: Device name | Protocol Map | Adapter | IRQ | Slot/IO | If's | CLK | Baud rate | wanpipe1 | N/A | A101/1D/A102/2D/4/4D/8| 169 | 4 | 1 | N/A | 0 | Wanrouter Status: Device name | Protocol | Station | Status | wanpipe1 | AFT TE1 | N/A | Connected | Local sets are all Aastra 9143's. - dbc. -------------- next part ------------...

I have a problem with a Sangoma card. It worked until yesterday. Now I keep getting this error: Jul 29 17:45:17 pbxacura kernel: wanpipe1: Enable E1 CAS signalling mode! Jul 29 17:45:17 pbxacura kernel: wanpipe1:w1g1: Rx Error: No 'DeviceSelect' from target: pci fatal error! (0x000FA000) Jul 29 17:45:48 pbxacura last message repeated 30946 times It is using Wanpipe 3.5.6 and Zaptel 1.4.12.1 with Asterisk 1.4.30 and MFC/R2....

...have a system that is down since the morning (maybe power intruptions). All seems fine except for "wanrouter status" shows disconnected. Following are the alarms raised. Should I call telco (they have long wait times) or should I just keep searching online for troubleshooting tips. "*wanpipe1 | AFT TE1 | N/A | Disconnected |" <<<<<* This is what shows. root at pbx:~ $ wanpipemon -i w1g1 -c Ta ***** w1g1: T1 Rx Alarms (Framer) ***** *ALOS: OFF | LOS: ON* *RED: ON | AIS: OFF* *LOF: ON | RAI: OFF* * * ****** w1g1: T1 Rx Alarms (LIU...

Hi, I have a client who has a system with a Sangoma 1 port PRI card with echo canceling in it. For some reason, when the system comes up the PRI will stay up for about 4-5 hours, then drop. "zap show status" shows everything as ok, but we can't make or receive any calls until the system is rebooted. Just restarting asterisk does not fix the problem. I am going to call