We are experiencing a sporadic issue across several systems using 1.2.x releases of Asterisk where there are lots of child processes spawned off the main Asterisk process that appear to be just sitting around doing nothing. They don't accumulate any CPU time, so don't know if they are deadlocked on something. Eventually, the systems will hang when a number of these processes accumulate. Anyone else experienced this or is there any specific known issue that may cause this? Thanks, Mike Clark