I mean powered down and cold restarted. As if its got a config its come from somewere,
[/quote]
This has never been the case for any version of asterisk in the past.
Everything always went from the reloading of the services. I’ll give it a try, but “rebooting” is not an option in a production environment. No asterisk function has ever required a reboot in the past (except for module load order in old zaptel?)
are you 100% sure that your extensions.conf file is
A: Spelt correct ie extensions.conf with no control chars in the nameing
B: the file is in a unix format and not been edited by notpad or the like just using vi
also try dos2unix to make 100 sure the file is in unix format