Displaying 20 results from an estimated 26 matches for "e159".
Did you mean:
159
2005 Aug 01
2
TDM400P REV I issues - ProSLIC vs TDM400P
The REV I card shows up in the PCI table as:
02:05.0 Network controller: Tiger Jet Network Inc. Intel 537 (or
02:05.0 Class 0280: e159:0001)
Subsystem: Unknown device b119:0001
But the REV E/F shows up as:
02:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface (or
02:0d.0 Class 0780: e159:0001)
Subsystem: Unknown device b100:0003
One is class 0780, one is class 0280. I don'...
2006 Mar 06
2
Problem getting two x200p cards working on 1.2.4
...XO/1 "Generic Clone Board 2"
signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 1
context=from-pstn
group=0
channel => 1
; Span 2: ZTDUMMY/1 "ZTDUMMY/1 1"
This is the corresponding 'lspci -vv -n' for my two cards:
02:01.0 Class 0780: e159:0001
Subsystem: 8086:0003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 32000ns max)...
2005 Jul 31
1
Questions on Asterisk and CallerID
...{EXTEN})
exten => _NXXXXXXX,1,Answer
exten => _NXXXXXXX,2,Dial(Zap/g1/${EXTEN})
I can to see following in /var/log/messages when I make outgoing call.
Jul 20 00:50:26 boldsoft kernel: Zapata Telephony Interface Registered
on major 196
Jul 20 00:50:26 boldsoft kernel: ZapTel device: vendor=e159 device=1
subvendor=8085
Jul 20 00:50:26 boldsoft kernel: wcfxo0: <Wildcard X101P> port
0xe800-0xe8ff mem 0xfaffe000-0xfaffefff irq 18 at device 9.0 on
pci2
Jul 20 00:50:26 boldsoft kernel: ZapTel Attach for wcfxo0: deviceID :
0xe159
Jul 20 00:50:26 boldsoft kernel: wcfxo: DAA mode is 'FCC...
2005 Aug 02
0
Few questions about Asterisk
...{EXTEN})
exten => _NXXXXXXX,1,Answer
exten => _NXXXXXXX,2,Dial(Zap/g1/${EXTEN})
I can to see following in /var/log/messages when I make outgoing call.
Jul 20 00:50:26 boldsoft kernel: Zapata Telephony Interface Registered
on major 196
Jul 20 00:50:26 boldsoft kernel: ZapTel device: vendor=e159 device=1
subvendor=8085
Jul 20 00:50:26 boldsoft kernel: wcfxo0: <Wildcard X101P> port
0xe800-0xe8ff mem 0xfaffe000-0xfaffefff irq 18 at device 9.0 on
pci2
Jul 20 00:50:26 boldsoft kernel: ZapTel Attach for wcfxo0: deviceID :
0xe159
Jul 20 00:50:26 boldsoft kernel: wcfxo: DAA mode is 'FCC...
2006 May 26
1
my kernel not detect my TDM400P card
Hi all
I want to install a TDM400P card. I use fedora core 4 and the version of my kernel is 2.6.11-1.1369_FC4smp. When i type lspci, i have this message:
02:01.0 Network controller: Unknown device e159:0001
how can i fix this problem?
Thanks for your help!
Serge MESSA OVONO
---------------------------------
Yahoo! Mail r?invente le mail ! D?couvrez le nouveau Yahoo! Mail et son interface r?volutionnaire.
-------------- next part --------------
An HTML...
2011 Jun 01
1
Dahdi_genconfig - "Empty configuration -- no spans"
...n -- no spans
# dahdi_cfg -vvv
DAHDI Tools Version - 2.4.1
DAHDI Version: 2.4.1.2
Echo Canceller(s):
Configuration
======================
Channel map:
0 channels to configure.
# dahdi_hardware
driver should be 'wctdm' but is actually 'netjet'
pci:0000:01:09.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F
Where am I going wrong? Why is dahdi_genconf not seeing the card, when
dahdi_hardware does see it? I've tried "modprobe netjet", but makes no
difference.
Thanks for any suggestions,
Sebastian
2009 Nov 03
1
dahdi channel not showing up
Hi,
I have a X101P card and am running Asterisk SVN-trunk-r226890. The
X101P card seems to be identified properly:
debian:/usr/src/dahdi-tools# dahdi_hardware
pci:0000:01:01.0 wcfxo+ e159:0001 Wildcard X101P
debian:/usr/src/dahdi-tools# dahdi_cfg -vv
DAHDI Tools Version - SVN-trunk-r7409
DAHDI Version: SVN-trunk-r7445
Echo Canceller(s): MG2
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)
1 channels to conf...
2010 Sep 01
2
Freepbx + Asterisk problem - NEED HELP
...Blocked State
pseudo default
default In Service
-----------
INFO:
related lspci result:
07:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface
related dahdi_hardware result:
pci:0000:07:00.0 wctdm+ e159:0001 Wildcard TDM400P REV I
One more thing:
root at asterisk:~# lsmod|grep dahdi
dahdi_echocan_mg2 5729 4
dahdi_transcode 6836 1 wctc4xxp
dahdi_voicebus 41854 2 wctdm24xxp,wcte12xp
dahdi 210885 12
dahdi_echocan_mg2,xpp,dahdi_transcode,wcb4xxp,wctdm,wcfxo,...
2014 May 12
1
Terrible dahdi_test results
...ium Wildcard TE110P T1/E1
[ 39.223031] wcopenpci: Module loaded
[ 39.714308] dahdi_echocan_oslec: Registered echo canceler 'OSLEC'
[ 39.716015] TE110P: Span configured for CCS/HDB3/CRC4
[ 39.751770] wcte1xxp: Setting yellow alarm
# dahdi_hardware
pci:0000:06:00.0 wcte11xp+ e159:0001 Digium Wildcard TE110P T1/E1 Board
# dahdi_scan
[1]
active=yes
alarms=RED
description=Digium Wildcard TE110P T1/E1 Card 0
name=WCT1/0
manufacturer=Digium
devicetype=Digium Wildcard TE110P T1/E1
location=PCI Bus 06 Slot 01
basechan=1
totchans=31
irq=0
type=digital-E1
syncsrc=0
lbo=0 db (CSU)/...
2009 May 20
1
Channels configuration with DAHDI
...pan 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: HRtimer) 1" (MASTER)
Span 2: WCTDM/4 "Wildcard TDM400P REV E/F Board 5"
1 WCTDM/4/0 FXSKS RED
2 WCTDM/4/1 FXOKS
3 WCTDM/4/2
4 WCTDM/4/3
# dahdi_hardware
pci:0000:00:0a.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F
# dahdi_cfg -vvvvvvv
DAHDI Tools Version - 2.1.0.2
DAHDI Version: 2.1.0.4
Echo Canceller(s):
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Slaves: 02)
2 channels to configu...
2009 Aug 04
1
dahdi_scan doesn't recognize an OpenVox A400E
...hdi_hardware? detect it
but ?dahdi_scan? not and I cannot use it.
>lsppci:
*0a:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface*
11:00.0 ISDN controller: Digium, Inc. Wildcard B410 quad-BRI card (rev 01)
> dahdi_hardware:
pci:0000:0a:00.0 wctdm- e159:0001 Wildcard TDM400P REV E/F
pci:0000:11:00.0 wcb4xxp+ d161:b410 Digium Wildcard B410P
As you can see, it seems that wctdm driver is not loaded (minus sign beside
wctdm) but if I restart dahdi, it loads it correctly:
Loading DAHDI hardware modules:
wctdm:...
2009 Mar 10
3
configuring channels for dahdi
...can for channel 1 to mg2
setting echocan for channel 4 to mg2
sudo cat /proc/dahdi/*
Span 1: wctdm/4 'wildcard tdm400p rev I board 5' (master)
1 wctdm/4/0 fxoks (ec: mg2)
2 wctdm/4/1
3 wctdm/4/2
4 wctdm/4/3/ fxsks (ec:mg2)
dahdi_hardware -v
pci:0000:00:06.0 wctdm+ e159:0001 wildcard tdm400p rev I
ls -l /usr/lib/asterisk/modules/chan_dahdiso
-rwx-xr-x 1 root root /usr/lib/asterisk/modules/chan_dahdi.so
signalling must be specified before any channels are error[4641]
core show channels location State Application(Data)
0 active channels
0 act...
2003 Dec 15
6
more questions
> 3. Supposed I have 2 fxo cards (right now I have one already) and 3
> fxs, and one of the fxo will have two phone (running pararell), is
> there any way for * to:
> a. It always dial the first fxo, if the fxo is busy or is being used
> (have other people conversation), will * be able to switch it to
> other fxo? Here's the approximiate the conditions of the phone.
2011 Apr 02
1
Problem getting TDM400P clone card to go off-hook and dial
...MMY/1 (source: HRtimer) 1"
------------------------------------------
chan_dahdi.conf
...............
...
[channels]
#include /etc/asterisk/dahdi-channels.conf
...
---------------------------------------------
root at Trixie:/etc/asterisk# dahdi_hardware
pci:0000:02:01.0 wctdm+ e159:0001 Wildcard TDM400P REV I
---------------------------------------
root at Trixie:~# lsdahdi
### Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
1 FXO FXSKS (In use) (SWEC: MG2)
2 FXO FXSKS (In use) (SWEC: MG2)
3 FXS FXOKS (In us...
2005 Oct 03
0
TDM400P recognised as "Network controller: Unknowndevice"
...el installed. As I
wanted to explore more, I bought a TDM400P development kit (TDM11B) from
an authorised Asterisk reseller in Germany. After I updated my Asterisk
(make update) and installed zaptel last week (27 Sep 2005), here is what
I got:
# lspci -v
01:05.0 Network controller: Unknown device e159:0001
Subsystem: Unknown device b119:0001
Flags: bus master, medium devsel, latency 100, IRQ 209
I/O ports at 2400 [size=256]
Memory at efffe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
# dmesg
Module 0: Installed --...
2014 Jan 31
0
e911 Signalling
...to do with the hookstate
of the dahdi channel.
If anyone has a similar situation and want to provide some guidance, I'd
sure appreciate it.
Thanks!
Adam
Here's my config:
DAHDI version 2.8.0.1
[root at e911 dahdi]# dahdi_hardware
pci:0000:02:01.0 wct1xxp+ e159:0001 Digium Wildcard T100P T1/PRI
or E100P E1/PRA Board
e911*CLI> core show version
Asterisk 11.7.0 built by root @ e911 on a x86_64 running Linux on
2014-01-28 15:50:19 UTC
/etc/dahdi/system.conf
span=1,1,0,esf,b8zs
e&m=1-2
/etc/asterisk/chan_dahdi.conf
[channels]
group=...
2009 Mar 15
1
No hardware timing source found in /proc/dahdi
...rdware it is now recommended you
edit /etc/dahdi/modules in order to load support for only
the DAHDI hardware installed in this system. By default
support for all DAHDI hardware is loaded at DAHDI start.
I think that the DAHDI hardware you have on your system is:
pci:0000:03:08.0 wctdm- e159:0001 Wildcard TDM400P REV E/F
so it is seeing the card
/etc/dahdi/system.conf:
loadzone = us
defaultzone=us
fxoks=1,2
fxsks=3,4
echocanceller=mg2,1-4
channels=1-4
/etc/dahdi/init.conf:
MODULES="$MODULES wctdm"
/etc/dahdi/modules
# Digium TDM400P: up to 4 analog ports
wctdm
# /etc/i...
2005 Oct 03
2
TDM400P recognised as "Network controller: Unknown device"
...el installed. As I wanted to explore more, I bought a TDM400P development kit (TDM11B) from an authorised Asterisk reseller in Germany. After I updated my Asterisk (make update) and installed zaptel last week (27 Sep 2005), here is what I got:
# lspci -v
01:05.0 Network controller: Unknown device e159:0001
Subsystem: Unknown device b119:0001
Flags: bus master, medium devsel, latency 100, IRQ 209
I/O ports at 2400 [size=256]
Memory at efffe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
# dmesg
Module 0: Installed --...
2005 Mar 05
1
X100P Clone, Which one?
Hi All,
Googling X100P Clone I found several information about these cards and seems that some winmodem has the same chip used from the original X100P.
Here below a list winmodem which should work as X100P clone:
1057 Motorola
5608 SM56 PCI Fax Voice Modem
E159 Tiger Jet Network Inc
0001 Tiger 300/320 PCI interface
I bought one "Trust 56k V92 PCI Internal Modem MD-1100" which has the 1057 Motorola Chip, and I installed it on my linux box.
in my /proc/pci list it is recognized like 1057:3052 (Motorola) (rev 4)., IRQ 11, I/O at 0x6c00 [0x6cff]...
2020 Mar 27
0
AX-1600P FXO port configuration
...228088 19
xpp,r1t1,rxt1,wctdm24xxp,rcbfx,wcaxx,wcfxo,wctdm,dahdi_transcode,dahdi_echocan_oslec,oct612x,dahdi_voicebus,wcb4xxp,wct1xxp,wct4xxp,wcte43x,wcte11xp,wcte12xp,wcte13xp
crc_ccitt 12707 2 wctdm24xxp,dahdi
"dahdi_hardware" command:
pci:0000:06:01.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F
"dahdi_scan" command:
[1]
active=yes
alarms=OK
description=Wildcard TDM400P REV E/F Board 5
name=WCTDM/4
manufacturer=Digium
devicetype=Wildcard TDM400P REV E/F
location=PCI Bus 06 Slot 02
basechan=1
totchans=4
irq=0
type=analog
port=1,FXO
port=2,none
port=3...