retrieve_conf grabs all the settings in the MySQL DB for everything you have in the FreePBX GUI. It re-writes the asterisk config files.
core reload takes all the dialplan in asterisk and reloads it into the running config.
If you do a core reload and nothing breaks I can see why you think its a FreePBX issue but if you do a retreive_conf without changing a thing in the GUI it takes and writes out the same configs that you currently have and do a core reload it breaks.
You have confirmed that nothing changes in the /etc/asterisk directory when you diff before and after retrieve_conf without making a change in the GUI yet a core reload now breaks it. If nothing is truly changing in the configs its clear Asterisk must be breaking because the conf file has a new time stamp or something weird.
A simple test would be to just touch those files so the time and date stamps get updated and do a core reload and see what happens. My guess is it will break. Take that data back to Digium and hopefully they can get it fixed up.
first, i did a core reload and there were no dropped connections
next, i made a copy of /etc/asterisk and ran a diff to verify
next, i touch /etc/asterisk/*
run diff again, no change in files
now, i run core reload ā¦and i drop connectionsā¦so, i guess that completely rules out freepbx
although, i still suspect that andrew is the cigarette smoking man !!!
anyway, i am off to asterisk community, if I have some time over the weekend, i will try to touch files one by one to see if it is a specific file
Until itās exposed how could we tell you how to do it. You are asking for us to tell you how to do something that doesnāt exist in FreePBX at this time to do.
could you please take a look at the comment made by george, i can try to reproduce what he is asking, but it will take time. if you have any input, that would be greatly appreciated.
