[asterisk-users] module load chan_dahdi.so gives several WARNING-messages

[jonas kellens]

I have 2 questions about the following output on the Asterisk CLI :

asterisk*CLI> reload chan_dahdi.so
The 'reload' command is deprecated and will be removed in a future
release. Please use 'module reload' instead.
[Apr 22 15:02:33] NOTICE[3634]: loader.c:580 ast_module_reload: The
module 'chan_dahdi.so' was not properly initialized.  Before reloading
the module, you must run "module load chan_dahdi.so" and fix whatever is
preventing the module from being initialized.
asterisk*CLI> module load chan_dahdi.so
[Apr 22 15:02:43] WARNING[3634]: pbx.c:2982 ast_register_application:
Already have an application 'DAHDISendKeypadFacility'
[Apr 22 15:02:43] WARNING[3634]: pbx.c:2982 ast_register_application:
Already have an application 'ZapSendKeypadFacility'
  == Parsing '/etc/asterisk/chan_dahdi.conf': Found
[Apr 22 15:02:43] WARNING[3634]: chan_dahdi.c:4090 handle_alarms:
Detected alarm on channel 1: Red Alarm
    -- Registered channel 1, FXS Kewlstart signalling
[Apr 22 15:02:43] WARNING[3634]: chan_dahdi.c:4090 handle_alarms:
Detected alarm on channel 2: Red Alarm
    -- Registered channel 2, FXS Kewlstart signalling
[Apr 22 15:02:43] WARNING[3634]: chan_dahdi.c:4090 handle_alarms:
Detected alarm on channel 3: Red Alarm
    -- Registered channel 3, FXS Kewlstart signalling
    -- Automatically generated pseudo channel
  == Parsing '/etc/asterisk/users.conf': Found
  == Registered channel type 'DAHDI' (DAHDI Telephony Driver w/PRI)
  == Manager registered action DAHDITransfer
  == Manager registered action ZapTransfer
  == Manager registered action DAHDIHangup
  == Manager registered action ZapHangup
  == Manager registered action DAHDIDialOffHook
  == Manager registered action ZapDialOffHook
  == Manager registered action DAHDIDNDon
  == Manager registered action ZapDNDon
  == Manager registered action DAHDIDNDoff
  == Manager registered action ZapDNDoff
  == Manager registered action DAHDIShowChannels
  == Manager registered action ZapShowChannels
  == Manager registered action DAHDIRestart
  == Manager registered action ZapRestart
 Loaded chan_dahdi.so => (DAHDI Telephony w/PRI)


1. The Zaptel module is installed but is not loaded when the
Asterisk-server starts up. With chkconfig I changed the startup so that
in every runlevel the Zaptel-module is not loaded !
Why do I still get messages about Zaptel in the CLI ?

2. What could be the reason for the red alarms ???

Here are my config files :

/etc/dahdi/system.conf :

fxsks=1-3
loadzone= be
defaultzone= be

/etc/asterisk/chan_dahdi.conf :

[root at asterisk asterisk]# cat chan_dahdi.conf
[trunkgroups]

[channels]

language=be
busydetect=yes
busycount=6
callerid=asreceived
threewaycaling=yes
transfer=yes

;internationalprefix: 00
;nationalprefix:0 

;bovenstaande opties gelden voor alle gedefinïeerde kanalen hieronder

context=tel2268191 ; E.U.
signalling=fxs_ks
channel => 1

context=tel2362334 ; KMO
signalling=fxs_ks
channel => 2

context=telunknown
signalling=fxs_ks
channel => 3


[root at asterisk asterisk]# /usr/sbin/dahdi_cfg -vvvvv
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: FXS Kewlstart (Default) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Slaves: 03)

3 channels to configure.

[root at asterisk asterisk]# /usr/sbin/dahdi_hardware 
pci:0000:04:05.0     wctdm24xxp+  d161:8005 Wildcard TDM410P

[root at asterisk asterisk]# /usr/sbin/dahdi_tool 
shows me an 'OK' under Alarm for my Wildcard TDM410

Jonas Kellens.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090422/8b30d224/attachment.htm