[asterisk-r2] Res: Res: Zap alarm Problem
Marcus Vinicius
marc_mcs10 at yahoo.com.br
Thu Jul 23 09:05:09 CDT 2009
Hi Moises,
I commented the line of alarm and recompile the asterisk but rather to call off. See the logs:
***
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 17: Yellow Alarm
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 17.
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 19: Yellow Alarm
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 19.
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 20: Yellow Alarm
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 20.
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 21: Yellow Alarm
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 21.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 1: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 1.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 2: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 2.
Jul 23 10:53:58 WARNING[11759]: chan_zap.c:4268 zt_handle_event: Detected alarm on channel 3: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 4: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 4.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 5: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 5.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 6: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 6.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 8: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 8.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 9: Yellow Alarm
Jul 23 10:53:58 WARNING[11775]: chan_zap.c:4268 zt_handle_event: Detected alarm on channel 7: Yellow Alarm
-- Stopped music on hold on Zap/7-1
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/7-1' in macro 'nx-queue'
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/7-1' in macro 'aa-suporte-multiempresa'
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/7-1'
-- Executing Hangup("Local/249 at from-inside-cd94,2", "") in new stack
Jul 23 10:53:58 WARNING[11050]: chan_zap.c:4268 zt_handle_event: Detected alarm on channel 11: Yellow Alarm
Jul 23 10:53:58 WARNING[11649]: chan_zap.c:4268 zt_handle_event: Detected alarm on channel 18: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 9.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 10: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 10.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 12: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 12.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 13: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 13.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 14: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 14.
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1383 zt_r2_on_hardware_alarm: Detected alarm on channel 15: Yellow Alarm
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 15.
-- Stopped music on hold on Zap/18-1
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/18-1' in macro 'nx-queue'
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/18-1' in macro 'aa-suporte-multiempresa'
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/18-1'
-- Hungup 'Zap/18-1'
== Spawn extension (from-inside-redir, h, 1) exited non-zero on 'Local/249 at from-inside-cd94,2'
-- Hungup 'Zap/7-1'
Jul 23 10:53:58 NOTICE[21644]: chan_zap.c:1457 zt_r2_on_call_end: MFC/R2 call end on chan 18
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/3-1' in macro 'nx-queue'
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/3-1' in macro 'aa-suporte-multiempresa'
== Spawn extension (macro-nx-queue, s, 13) exited non-zero on 'Zap/3-1'
== Spawn extension (macro-nx-userexten-base, s, 135) exited non-zero on 'Zap/11-1' in macro 'nx-userexten-base'
-- Hungup 'Zap/3-1'
Jul 23 10:53:58 NOTICE[21644]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 17
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 17.
Jul 23 10:53:58 NOTICE[21644]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 18
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 18.
Jul 23 10:53:58 NOTICE[21644]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 19
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 19.
Jul 23 10:53:58 NOTICE[21644]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 20
== Spawn extension (macro-nx-userexten-base, s, 135) exited non-zero on 'Zap/11-1' in macro 'nx-stdexten'
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 20.
Jul 23 10:53:58 NOTICE[21644]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 21
Jul 23 10:53:58 WARNING[21644]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 21.
== Spawn extension (macro-nx-userexten-base, s, 135) exited non-zero on 'Zap/11-1' in macro 'aa-suporte-multiempresa'
== Spawn extension (macro-nx-userexten-base, s, 135) exited non-zero on 'Zap/11-1'
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 8
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 8.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 15
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 15.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 1
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 1.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 2
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 2.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 3
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 3.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 4
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 4.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 5
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 5.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 6
-- Hungup 'Zap/11-1'
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 6.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 7
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 7.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 9
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 9.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 10
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 10.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 12
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 12.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 13
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 13.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 14
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 14.
Jul 23 10:53:58 NOTICE[21643]: chan_zap.c:1389 zt_r2_on_hardware_alarm: Alarm cleared on channel 11
Jul 23 10:53:58 WARNING[21643]: chan_zap.c:1393 zt_r2_on_hardware_alarm: Zap alarm on chan 11.
***
changes were:
# diff -u chan_zap.c.old chan_zap.c
--- chan_zap.c.old 2009-07-21 11:44:36.000000000 -0300
+++ chan_zap.c 2009-07-21 11:45:39.000000000 -0300
@@ -5007,7 +5007,7 @@
return NULL;
}
- if (p->radio && p->inalarm) return NULL;
+ /* if (p->radio && p->inalarm) return NULL; */
p->subs[index].f.frametype = AST_FRAME_NULL;
p->subs[index].f.datalen = 0;
Version:
Asterisk SVN-moy-mfcr2-1.2-r178065M
OpenR2 version: 1.1.0, revision: exported
Any other place in chan_zap.c is this treatment?
thank you very much.
--
Marcus
________________________________
De: Moises Silva <moises.silva at gmail.com>
Para: asterisk-r2 at lists.digium.com
Enviadas: Segunda-feira, 20 de Julho de 2009 13:14:39
Assunto: Re: [asterisk-r2] Res: Zap alarm Problem
> Having said that, the difference is between chan_zap and chan_unicall.
>
> chan_unicall ignores alarms, you can find Steve comments in chan_unicall.c, search for UC_EVENT_ALARM, and you will find something like this:
>
> /* TODO: No alarm handling is bad! */
>
> On the other hand, chan_zap/chan_dahdi both check the alarm status each time zt_read()/dahdi_read() is called and return NULL if the line is in alarm, and the Asterisk core most > likely drops the call when sees NULL as return value from those routines.
>
> In order to be certified most likely any PBX should drop the call on alarms. In your case, if you don't care about that you can easily comment the following lines in chan_zap.c:
>
> Search for zt_read in line 4990 in chan_zap.c and read some lines below, you will see a line saying:
>
> if (p->radio && p->inalarm) return NULL;
>
> Just comment out that line, or remove the p->inalarm condition.
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
More information about the asterisk-r2
mailing list