Asterisk AMI is required by Communications Manager. You shouldn't be disabling it or you would not be able to manage your system. You should into original issue where Asterisk wouldn't start. Have you had this problem before? How did you restored your system? And did you do anything other than that?

There is no information about this error message. It was removed in v1.8. v1.6.2 is EOL since 2012. You could try restarting your system in case something was locked or hung. But you should really consider updating your system to the latest version.

I agree, but I need to get AMI working so I can import the customers from this last 1.6 server to the new thirdlane…I have rebooted it several times and got the same results, will try the timeout settings to see if it fixes it

Is 1.6 still based on flat files in /etc/asterisk? Or is there SQL integration? Couldn't you use data from those files and/or the SQL DB to reconstruct a file that will import into the newer version of TL? I have never used the AMI so I'm not certain what attributes are backed up.

thanks to Alex got in to our server, he tried to run manager with in the CLI and it would not work, then put in the old original manager.conf, it worked. then replace it with the one we had issues with and BAM it is working perfectly. Now we can migrate the customers over the next couple of weeks. thanks again. He tried something we so simple but it worked, Alex you rock!

A winning combination of field tested VoIP telephony and modern Unified Communications with voice, video, messaging, screen and file sharing, and integration with Salesforce, Zendesk and other applications assures that our customers have the most advanced communications tools available today.