[Asterisk-Users] Errors after re-plugging T1

[Markus Mayer]

Hi,

After temporarily pulling the T1 cable out of our Asterisk box, we ended
up getting a strange error messages even after the cable was plugged
back in.

[...]
Dec 10 09:01:11 WARNING[1192437440]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: Read on 63 failed: Unknown error 500
Dec 10 09:01:21 WARNING[1192437440]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: Read on 63 failed: Unknown error 500
Dec 10 09:03:42 WARNING[1192437440]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: Read on 63 failed: Unknown error 500
Dec 10 09:03:52 WARNING[1192437440]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: Read on 63 failed: Unknown error 500
[...]

So I stopped asterisk, unloaded the kernel modules and restarted
everything, but still:

Dec 10 09:06:16 WARNING[1184048960]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: !! No channel map, no channel, and no ds1?  What am
I supposed to identify?
Dec 10 09:06:16 WARNING[1184048960]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: !! Unable to add IE 'Channel Identification'
Dec 10 09:06:20 WARNING[1184048960]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: Read on 62 failed: Unknown error 500
Dec 10 09:06:20 NOTICE[1200825920]: File chan_zap.c, Line 4634
(handle_init_event): Alarm cleared on channel 1
Dec 10 09:06:20 NOTICE[1200825920]: File chan_zap.c, Line 4634
(handle_init_event): Alarm cleared on channel 2
Dec 10 09:06:20 NOTICE[1200825920]: File chan_zap.c, Line 4634
(handle_init_event): Alarm cleared on channel 3
Dec 10 09:06:20 NOTICE[1200825920]: File chan_zap.c, Line 4634
(handle_init_event): Alarm cleared on channel 4
[...]
Dec 10 09:18:07 WARNING[1184048960]: File chan_zap.c, Line 5683
(zt_pri_error): PRI: Read on 62 failed: Unknown error 500
Dec 10 09:18:07 NOTICE[1200825920]: File chan_zap.c, Line 4634
(handle_init_event): Alarm cleared on channel 1
Dec 10 09:18:07 NOTICE[1200825920]: File chan_zap.c, Line 4634
(handle_init_event): Alarm cleared on channel 2

I tried this several times, to no avail. Only rebooting the box helped.
The question now is: is there a way to avoid rebooting in a situation
like this and still get everything to work again? Rebooting can be a
huge pain.

Thanks.

Regards,
Markus