[asterisk-r2] Res: Zap alarm Problem

[Arturo Ochoa]

AFAIK, unicall or openr2, are library's that let asterisk understand
mfc-r2 signaling.... The kernel driver (zaptel or dahdi) is the one in
charge of all the communication between the card and the operating
system. So, every time the  card detects loose signal... the driver is
the one that notifies the kernel about it.....This is my
understanding, please correct me, if I'm wrong...

I recently had exactly same problem with Telmex in Mexico. We replace
E1 cable, troubleshoot any IRQ problems, We grounded the Server, and
the problem still happen time to time.... So, it should be some bad
quality modem, or perhaps bad wiring, still don't know...

Regards,

Ing Arturo Ochoa





On Mon, Jul 20, 2009 at 9:46 AM, Marcus Vinicius<marc_mcs10 at yahoo.com.br> wrote:
> Hi,
>
> The Telefonica has already made physical tests but not found anything on
> line. This system was running with the library unicall smoothly.
> OpenR2 could be treating the "Yellow Alarm" in a different way of unicall?
> The call does not hang up with unicall.
>
> Some settings can be changed to try to fix that?
>
> thanks.
>
>
>
>
> Marcus
>
>
>
> ________________________________
> De: Rafael Prado Rocchi <prado at practis.com.br>
> Para: asterisk-r2 at lists.digium.com
> Enviadas: Quinta-feira, 25 de Junho de 2009 17:14:31
> Assunto: Re: [asterisk-r2] Zap alarm Problem
>
> Marcus,
>
>
>
> We have several clients using Telefonica E1 links in Brazil, in most of them
> the links are bad quality.
>
> Sadly, this is a very common situation for telefonica clients.
>
>
>
> When it happens, we call telefonica support and ask a for a line quality
> test. Ask them to send a technician to you. In 100% of the cases, they solve
> this kind of problem by changing your modem, cables and/or balums.
>
>
>
> Prado
>
>
>
>
>
>
>
>
>
> From: asterisk-r2-bounces at lists.digium.com
> [mailto:asterisk-r2-bounces at lists.digium.com] On Behalf Of Marcus Vinicius
> Sent: quinta-feira, 25 de junho de 2009 13:46
> To: asterisk-r2 at lists.digium.com
> Subject: [asterisk-r2] Zap alarm Problem
>
>
>
> Good morning,
>
> I have a Digium card Te110P and a E1 Brazil (telco Telefonica).
> I have alarms at different times of day and the calls Hang up .
>
> The following are the logs and the Asterisk configurations.
>
> Who knows what may be happening?
>
>
> Thank you.
>
>
> Logs
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 2:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 2.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 3:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 3.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 4:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 4.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 5:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 5.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 6:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 6.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 7:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 7.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 10:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 10.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 11:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Detected alarm on channel 17:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 17.
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Detected alarm on channel 18:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 18.
> Jun 25 11:55:39 WARNING[6485] chan_zap.c: Detected alarm on channel 19:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[5419] chan_zap.c: Detected alarm on channel 9:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[28580] chan_zap.c: Detected alarm on channel 1:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[28612] chan_zap.c: Detected alarm on channel 8:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[1005] chan_zap.c: Detected alarm on channel 20:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[3388] chan_zap.c: Detected alarm on channel 21:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 11.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 12:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 12.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 13:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 13.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 14:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 14.
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Detected alarm on channel 15:
> Yellow Alarm
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 15.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 2
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 2.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 3
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 3.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 4
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 4.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 5
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 5.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 6
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 6.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 7
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 7.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 9
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 9.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 10
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 10.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 11
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 11.
> Jun 25 11:55:39 NOTICE[4637] chan_zap.c: Alarm cleared on channel 17
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 17.
> Jun 25 11:55:39 NOTICE[4637] chan_zap.c: Alarm cleared on channel 18
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 18.
> Jun 25 11:55:39 NOTICE[4637] chan_zap.c: Alarm cleared on channel 20
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 20.
> Jun 25 11:55:39 NOTICE[4637] chan_zap.c: Alarm cleared on channel 21
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 21.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 12
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 12.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 13
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 13.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 14
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 14.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 15
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 15.
> Jun 25 11:55:39 NOTICE[4637] chan_zap.c: Alarm cleared on channel 19
> Jun 25 11:55:39 WARNING[4637] chan_zap.c: Zap alarm on chan 19.
> Jun 25 11:55:39 NOTICE[4636] chan_zap.c: Alarm cleared on channel 1
> Jun 25 11:55:39 WARNING[4636] chan_zap.c: Zap alarm on chan 1.
> Jun 25 11:55:40 NOTICE[4636] chan_zap.c: Alarm cleared on channel 8
> Jun 25 11:55:40 WARNING[4636] chan_zap.c: Zap alarm on chan 8.
>
>
> Version: Asterisk SVN-moy-mfcr2-1.2-r178065
> Zaptel Version: 1.2.27
>
>
> /etc/zaptel.conf
> span=1,1,0,cas,hdb3
> cas=1-15,17-31:1101
>
> loadzone=br
> defaultzone=br
>
> /etc/asterisk/zapata.conf
> [trunkgroups]
>
> [channels]
> context=default
> rxwink=300
> busydetect=yes
> busycount=3
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> restrictcid=no
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=no
> cancallforward=no
> callreturn=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> callgroup=2
> pickupgroup=2
> faxdetect=both
> immediate=no
> musiconhold=default
> faxdetect=both
> echocancel=yes
> relaxdtmf=yes
> context=default
>
> ; Configuracao de E1 R2
> signalling=mfcr2
> mfcr2_variant=br
> mfcr2_get_ani_first=no
> mfcr2_max_ani=10
> mfcr2_max_dnis=4
> mfcr2_category=national_subscriber
> mfcr2_logdir=span1
> mfcr2_logging=all
> mfcr2_allow_collect_calls=yes
> mfcr2_double_answer=no
>
> ; 20 Canais MFC
> context=default
> group=0
> callgroup=0
> pickupgroup=0
> channel => 1-15
> channel => 17-21
>
>
> cat /proc/interrupts
>            CPU0
>   0:  177065570          XT-PIC  timer
>   1:         10          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   5:  176981347          XT-PIC  wctdm
>   9:          0          XT-PIC  acpi
>  10:   41354041          XT-PIC  eth1
>  11:  177061623          XT-PIC  wctdm, eth0
>  12:  176977065          XT-PIC  wcte11xp
>  14:    4672339          XT-PIC  libata
>  15:         34          XT-PIC  ide1
> NMI:          0
> LOC:          0
> ERR:          0
> MIS:          0
>
>
>
>
> __________________________________________________
> Fale com seus amigos de graça com o novo Yahoo! Messenger
> http://br.messenger.yahoo.com/
>
> __________ Informação do ESET NOD32 Antivirus, versão da vacina 4188
> (20090625) __________
>
> A mensagem foi verificada pelo ESET NOD32 Antivirus.
>
> http://www.eset.com
>
> __________ Informação do ESET NOD32 Antivirus, versão da vacina 4189
> (20090625) __________
>
> A mensagem foi verificada pelo ESET NOD32 Antivirus.
>
> http://www.eset.com
>
> ________________________________
> Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 -
> Celebridades - Música - Esportes
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>