[asterisk-bugs] [Asterisk 0014627]: Asterisk says: "No DAHDI Transcoders found.", but dahdi_transcode module reports 1 transcoder
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Mar 9 11:02:14 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14627
======================================================================
Reported By: xblurone
Assigned To: sruffell
======================================================================
Project: Asterisk
Issue ID: 14627
Category: Codecs/General
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 180380
Request Review:
======================================================================
Date Submitted: 2009-03-09 01:02 CDT
Last Modified: 2009-03-09 11:02 CDT
======================================================================
Summary: Asterisk says: "No DAHDI Transcoders found.", but
dahdi_transcode module reports 1 transcoder
Description:
Hi,
I have compiled various versions of Dahdi Linux and asterisk (1.4 and
1.6), and even Digium support has compiled the latest Dahdi-SVN &
Asterisk-1.4-svn, to no avail. Dmesg shows happily the drivers loaded and
the transcoder also ready, however asterisk does not seem to agree.
By the way, asterisk does NOT report that /dev/dahdi/transcoder cannot be
opened, so there is no error there.
I can only conclude this is a bug... Anything else I can help to
fast-track the resolve of this issue?
======================================================================
----------------------------------------------------------------------
(0101391) xblurone (reporter) - 2009-03-09 11:02
http://bugs.digium.com/view.php?id=14627#c101391
----------------------------------------------------------------------
Oops, guess I got to the limit of the window... Here is the rest of the
dmesg output...
wanpipe8: Enable Zaptel HW DCHAN interface
wanpipe8: Wanpipe device is registered to Zaptel span # 8!
wanpipe6: E1 connected!
wanpipe6: AFT communications enabled!
wanpipe6: AFT Per Port TDM Intr
wanpipe7: E1 disconnected!
wanpipe4: Enable E1 Interrupts
wanpipe5: Enable E1 Interrupts
ADDRCONF(NETDEV_UP): w3g1: link is not ready
wanpipe8: E1 connected!
wanpipe8: AFT communications enabled!
wanpipe8: AFT Per Port TDM Intr
wanpipe6: Enable E1 Interrupts
ADDRCONF(NETDEV_UP): w7g1: link is not ready
ADDRCONF(NETDEV_CHANGE): w8g1: link becomes ready
wanpipe8: Enable E1 Interrupts
wanpipe1: Enable E1 CCS signalling mode!
wanpipe2: Enable E1 CCS signalling mode!
wanpipe3: Enable E1 CCS signalling mode!
wanpipe4: Enable E1 CCS signalling mode!
wanpipe5: Enable E1 CCS signalling mode!
wanpipe6: Enable E1 CCS signalling mode!
wanpipe7: Enable E1 CCS signalling mode!
wanpipe8: Enable E1 CCS signalling mode!
dahdi_echocan_mg2: Registered echo canceler 'MG2'
wctc4xxp: tc400b0: Attached to device at 0000:09:02.0.
wctc4xxp: tc400b0: (G.729a) Transcoder support LOADED (firm ver = 6.12)
wctc4xxp: tc400b0: Installed a Wildcard TC: Wildcard TC400P+TC400M
dahdi_transcode: Registered codec translator 'DTE Encoder' with 120
transcoders (srcs=0000000c, dsts=00000100)
dahdi_transcode: Registered codec translator 'DTE Decoder' with 120
transcoders (srcs=00000100, dsts=0000000c)
I have indeed talked to Digium on several occasions, but all they do is
reinstall the Dahdi driver, which is a bit redundant... I am hoping this
way I get faster results, which will also benefit all other TC400B users.
Issue History
Date Modified Username Field Change
======================================================================
2009-03-09 11:02 xblurone Note Added: 0101391
======================================================================
More information about the asterisk-bugs
mailing list