## El Log del kernel me muestra esto cuando carga el modulo.
_____________________________________________________________
Apr 11 01:10:04 asterisk1 kernel: ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2 loaded
Apr 11 01:10:04 asterisk1 kernel: HiSax: Linux Driver for passive ISDN cards
Apr 11 01:10:04 asterisk1 kernel: HiSax: Version 3.5 (module)
Apr 11 01:10:04 asterisk1 kernel: HiSax: Layer1 Revision 2.46.2.5
Apr 11 01:10:04 asterisk1 kernel: HiSax: Layer2 Revision 2.30.2.4
Apr 11 01:10:04 asterisk1 kernel: HiSax: TeiMgr Revision 2.20.2.3
Apr 11 01:10:04 asterisk1 kernel: HiSax: Layer3 Revision 2.22.2.3
Apr 11 01:10:04 asterisk1 kernel: HiSax: LinkLayer Revision 2.59.2.4
Apr 11 01:10:04 asterisk1 kernel: HiSax module removed
Apr 11 01:10:04 asterisk1 kernel: ISDN-subsystem unloaded
Apr 11 01:10:04 asterisk1 kernel: Zapata Telephony Interface Registered on major 196
Apr 11 01:10:04 asterisk1 kernel: Zaptel Version: Echo Canceller: KB1
Apr 11 01:10:04 asterisk1 kernel: Registered Tormenta2 PCI
Apr 11 01:10:04 asterisk1 kernel: ACPI: PCI interrupt 0000:03:09.0[A] -> GSI 21 (level, low) -> IRQ 209
Apr 11 01:10:04 asterisk1 kernel: Controller version: 24
Apr 11 01:10:04 asterisk1 kernel: FALC version: 00000000
Apr 11 01:10:04 asterisk1 kernel: TE110P: Setting up global serial parameters for E1 FALC V1.2
Apr 11 01:10:04 asterisk1 kernel: TE110P: Successfully initialized serial bus for card
Apr 11 01:10:04 asterisk1 kernel: Found a Wildcard: Digium Wildcard TE110P T1/E1
Apr 11 01:10:04 asterisk1 kernel: Registered tone zone 2 (France)
Apr 11 01:10:04 asterisk1 kernel: TE110P: Span configured for CCS/HDB3/CRC4
Apr 11 01:10:04 asterisk1 kernel: Calling startup (flags is 4099)
Apr 11 01:10:04 asterisk1 kernel: wcte1xxp: Setting yellow alarm
Apr 11 01:10:04 asterisk1 kernel: TE110P: Span configured for CCS/HDB3/CRC4
Apr 11 01:10:04 asterisk1 kernel: Calling startup (flags is 4099)
Apr 11 01:10:04 asterisk1 kernel: Registered tone zone 2 (France)
Apr 11 01:10:04 asterisk1 kernel: TE110P: Span configured for CCS/HDB3/CRC4
Apr 11 01:10:04 asterisk1 kernel: Calling startup (flags is 4099)
Apr 11 01:10:04 asterisk1 kernel: Registered tone zone 2 (France)
Apr 11 01:10:04 asterisk1 kernel: TE110P: Span configured for CCS/HDB3/CRC4
Apr 11 01:10:04 asterisk1 kernel: Calling startup (flags is 4099)
Apr 11 01:10:04 asterisk1 kernel: Registered tone zone 2 (France)
Apr 11 01:10:04 asterisk1 kernel: TE110P: Span configured for CCS/HDB3/CRC4
Apr 11 01:10:04 asterisk1 kernel: Calling startup (flags is 4099)
Apr 11 01:10:04 asterisk1 kernel: Registered tone zone 2 (France)
______________________________________________
#### El Log de /var/log/asterisk/full dice lo siguiente con respecto a ZAP
_____________________________________________________________________
[chan_features.so]Apr 11 11:09:09 VERBOSE[3119] logger.c: [chan_features.so] => (Feature Proxy Channel)
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Registered channel type 'Feature' (Feature Proxy Channel Driver)
Apr 11 11:09:09 VERBOSE[3119] logger.c: [chan_zap.so]Apr 11 11:09:09 VERBOSE[3119] logger.c: [chan_zap.so] => (Zapata Telephony w/PRI)
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Parsing '/etc/asterisk/zapata.conf': Apr 11 11:09:09 VERBOSE[3119] logger.c: == Parsing '/etc/asterisk/zapata.conf': Fo
und
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Parsing '/etc/asterisk/zapata-auto.conf': Apr 11 11:09:09 VERBOSE[3119] logger.c: == Parsing '/etc/asterisk/zapata-auto
.conf': Found
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Parsing '/etc/asterisk/zapata_additional.conf': Apr 11 11:09:09 VERBOSE[3119] logger.c: == Parsing '/etc/asterisk/zapat
a_additional.conf': Found
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 1, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 1, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 2, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 2, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 3, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 3, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 4, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 4, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 5, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 5, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 6, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 6, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 7, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 7, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 8, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 8, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 9, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 9, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 10, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 10, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 11, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 11, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 12, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 12, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 13, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 13, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 14, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 14, PRI Signalling signalling
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Failed to read gains: Invalid argument
Apr 11 11:09:09 DEBUG[3119] chan_zap.c: Updated conferencing on 15, with 0 conference users
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Registered channel 15, PRI Signalling signalling
Apr 11 11:09:09 VERBOSE[3119] logger.c: -- Automatically generated pseudo channel
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Starting D-Channel on span 1
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Registered channel type 'Zap' (Zapata Telephony Driver w/PRI)
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Manager registered action ZapTransfer
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Manager registered action ZapHangup
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Manager registered action ZapDialOffhook
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Manager registered action ZapDNDon
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Manager registered action ZapDNDoff
Apr 11 11:09:09 VERBOSE[3119] logger.c: == Manager registered action ZapShowChannels
________________________________________________________________________
2006/4/11, Black Hand <[EMAIL PROTECTED]>:
On Tuesday 11 April 2006 11:18, Carlos Leon wrote:
> Desde hace un par de dias estoy intentando configurar esta tarjeta para
> utilizarlo con un E1/2 en Telmex, he configurado el zaptel.conf de la
> siguiente manera
>
> span=1,1,0,ccs,hdb3,crc4
> bchan=1-15
> dchan=16
>
> cargo los modulos aplico el ztcfg -vv y la tarjeta prende el led rojo
> intermitentemente. Se uqe para que funciones correctamente tiene que estar
> en verde. Alguna ayuda para ver como soluciono esto.
uhm... q te dicen los logs del asterisk ?
/var/log/asterisk/*
--
Black Hand
Amiga Addicts
Powered by Linux, KDE 3.5 and lots of GNU Force
_______________________________________________
Linux-plug mailing list
[email protected]
http://www.linux.org.pe/cgi-bin/mailman/listinfo/linux-plug
_______________________________________________ Linux-plug mailing list [email protected] http://www.linux.org.pe/cgi-bin/mailman/listinfo/linux-plug
