Summary:	ASTERISK-00435: TE410p requiring a complete power down on the server.
Reporter:	zoa (zoa)	Labels:
Date Opened:	2003-10-27 10:29:55.000-0600	Date Closed:	2011-06-07 14:00:36
Priority:	Blocker	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	My asterisk server in a colo suddenly no longer seemed to be able to call. the span status was green, and everything seemed to be working fine, but i always got a could not create zap channel. pri (intensive) debug span 1 did not do anything, i got no error messages or warning or debug messages, nothing that would indicate that debugging was on. (Except for the message that debugging was on) Reloading the modules and rebooting the server did not resolve the issue, after a 2 hour drive to the colo and a complete power down the problem was resolved. I remember hearing a similar problem, is there a solution or workaround for this ? I am running : Asterisk CVS-10/14/03-00:10:29
Comments:	By: Mark Spencer (markster) 2003-11-06 18:59:10.000-0600 I've never heard of a problem which required a complete power cycle.  Are you sure reloading the module wouldn't fix it? By: gavin (gavin) 2003-11-10 06:11:33.000-0600 I also have had this problem once with the TE410P.  Most of the time, reloading the module works, but after repeated loading and unloading the module the card can "lock up" to the point removal of power is necessary. By: Brian West (bkw918) 2003-12-06 12:08:41.000-0600 Could this be hardware related? By: zoa (zoa) 2003-12-06 18:57:17.000-0600 i'm sure reloading the module didnt fix it, reboot didnt work either, only power down did the trick. Only saw this behaviour once. By: Brian West (bkw918) 2003-12-10 17:48:26.000-0600 Maybe a fluke?  Have you seen it happen since then or only once? By: zoa (zoa) 2003-12-11 07:05:58.000-0600 it happened only once. By: Brian West (bkw918) 2003-12-14 11:44:06.000-0600 I'm going to say this was a one time issue.  It hasn't happened since then but if it does please find me on IRC and we will reopen this bug.