[Asterisk-Users] Zaptel/PRI problem

reseaux reseauxit at yahoo.it
Wed Mar 31 03:37:00 MST 2004


Dear Tais
	I have found the same problem with the same version of Asterisk (cvs 1_0) im 
still waiting for a possible progress in it.
Im using Asterisk under Mandrake 9.2 with entreprise kernel (2.4) with one and  
two CPU (two Server) both CPU are Xeon with 1 TE410P per Server.
I hope in some new event...
Bye
Dimitri

On Tuesday 30 March 2004 10:14, Tais M. Hansen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi.
>
> I'm getting the following error at random intervals on my TE410P with
> Asterisk CVS-03/30/04-11:49:01-CEST.
>
> I have two spans active, one connected to my Telco, the other to a Siemens
> PABX. Both spans display this behavior at random intervals.
>
> All calls are dropped when this happens. Spans are not necessarily in use
> when this happens.
>
>
> Mar 30 12:01:41 WARNING[81926]: chan_zap.c:6017 zt_pri_error: PRI: Read on
> 72 failed: Unknown error 500
> Mar 30 12:01:41 NOTICE[81926]: chan_zap.c:6733 pri_dchannel: PRI got event:
> 4 on span 2
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 32: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 32
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 33: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 33
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 34: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 34
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 35: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 35
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 36: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 36
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 37: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 37
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 38: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 38
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 39: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 39
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 40: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 40
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 41: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 41
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 42: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 42
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 43: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 43
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 44: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 44
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 45: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 45
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 46: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 46
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 48: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 48
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 49: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 49
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 50: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 50
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 51: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 51
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 52: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 52
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 53: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 53
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 54: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 54
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 55: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 55
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 56: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 56
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 57: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 57
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 58: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 58
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 59: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 59
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 60: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 60
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 61: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 61
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected
> alarm on channel 62: Yellow Alarm
> Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to
> disable echo cancellation on channel 62
> Mar 30 12:01:41 WARNING[81926]: chan_zap.c:6017 zt_pri_error: PRI: Read on
> 72 failed: Unknown error 500
> Mar 30 12:01:41 NOTICE[81926]: chan_zap.c:6733 pri_dchannel: PRI got event:
> 5 on span 2
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 32
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 33
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 34
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 35
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 36
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 37
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 38
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 39
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 40
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 41
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 42
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 43
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 44
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 45
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 46
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 48
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 49
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 50
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 51
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 52
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 53
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 54
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 55
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 56
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 57
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 58
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 59
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 60
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 61
> Mar 30 12:01:41 NOTICE[98311]: chan_zap.c:4933 handle_init_event: Alarm
> cleared on channel 62
>
> - --
> Regards,
> Tais M. Hansen
> ComX Networks
> Tel: +45-70257474
> Fax: +45-70257374
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAaUiA2TEAILET3McRAs5EAJwLQhuJyYZWaYubS3ddk/c2vpPFLACfUifQ
> P80Zirl2e/8I4ekJD5OIigU=
> =N/ae
> -----END PGP SIGNATURE-----
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users




More information about the asterisk-users mailing list