There is no external power on the new card. There was on the old.
Most of the configuration files are the once that comes with âmake samplesâ I only made changes to extensions.conf, sip.conf, voicemail.comf and chan_dahdi.conf. And then use the generated files from dahdi_genconfig
/etc/dagdi/modules
Autogenerated by /sbin/dahdi_genconf (Dahdi::Config::Gen::Modules) on Thu Mar 10 22:08:14 2016
If you edit this file and execute /sbin/dahdi_genconf again,
your manual changes will be LOST.
wctdm24xxp
~
/etc/dahdi/system.conf
Autogenerated by /sbin/dahdi_genconf on Thu Mar 10 23:39:31 2016
If you edit this file and execute /sbin/dahdi_genconf again,
your manual changes will be LOST.
Dahdi Configuration File
This file is parsed by the Dahdi Configurator, dahdi_cfg
Span 1: WCTDM/0 âWildcard TDM410Pâ (MASTER)
fxsks=1
echocanceller=mg2,1
fxoks=2
echocanceller=mg2,2
fxoks=3
echocanceller=mg2,3
fxoks=4
echocanceller=mg2,4
Global data
loadzone = us
defaultzone = us
/etc/dahdi/assigned-spans.conf
Autogenerated by /sbin/dahdi_span_assignments on Thu Mar 10 22:13:13 PST 2016
Map devices + local spans to span + base channel number
Device: [] @PCI_Bus_04_Slot_01 /sys/devices/pci0000:00/0000:00:1c.0/0000:03:00.0/0000:04:00.0/pci:0000:04:00.0
/sys/devices/pci0000:00/0000:00:1c.0/0000:03:00.0/0000:04:00.0/pci:0000:04:00.0 1:1:1
/etc/asterisk/sip.conf
register => ⌠// This is working fine, even whan dahdi is offhook.
[vitel-inbound]
type=friend
dtmfmode=auto
host=inbound22.vitelity.net
context=inbound-vitel
defaultuser=***
secret=***
allow=all
insecure=port,invite
canreinvite=no
[vitel-outbound]
type=friend
callerid=***
dtmfmode=auto
host=outbound.vitelity.net
defaultuser=***
fromuser=***
trustrpid=yes
sendrpid=yes
secret=***
allow=all
/etc/asterisk/modules
[modules]
autoload=yes
;
; Any modules that need to be loaded before the Asterisk core has been
; initialized (just after the logger has been initialized) can be loaded
; using âpreloadâ. This will frequently be needed if you wish to map all
; module configuration files into Realtime storage, since the Realtime
; driver will need to be loaded before the modules using those configuration
; files are initialized.
;
; An example of loading ODBC support would be:
;preload => res_odbc.so
;preload => res_config_odbc.so
;
; Uncomment the following if you wish to use the Speech Recognition API
;preload => res_speech.so
;
; If you want Asterisk to fail if a module does not load, then use
; the ârequireâ keyword. Asterisk will exit with a status code of 2
; if a required module does not load.
;
; require = chan_sip.so
; If you want you can combine with preload
; preload-require = res_odbc.so
;
; If you want, load the GTK console right away.
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
;
load => res_musiconhold.so
;
; Load one of: chan_oss, alsa, or console (portaudio).
; By default, load chan_oss only (automatically).
;
noload => chan_alsa.so
;noload => chan_oss.so
noload => chan_console.so
;
noload => res_phoneprov.so
noload => res_ari_events.so
noload => cdr_pgsql.so
noload => cel_pgsql.so
noload => res_config_pgsql.so
noload => res_config_ldap.so
noload => cdr_adaptive_odbc.so
noload => cdr_odbc.so
noload => cel_odbc.so
noload => func_odbc.so
noload => res_config_odbc.so
noload => res_odbc.so
What other configuration or log files would you be looking for?