Reading through the reference this was closed on wednesday. It appears that it is in the 1.8.4.rc2 version but not in the current 1.8.3.2.
You can do one of 3 things.
1. Wait until the stable 1.8.4 is release (RSN Real Soon Now) then use update-source once the digiumsource.conf file is updated. Hopefully the problem will be fixed in the final release.
Did I mention that update-source is EXPERIMENTAL?
2. Apply the interim patch yourself to your running version of asterisk
3. Edit the /etc/pbx/digiumsource.conf and replace the version of asterisk which is 1.8.3.2 with 1.8.4-rc2 and then use update-source
Did I mention that update-source is EXPERIMENTAL?
We generally DO NOT put release candidate versions of asterisk out. Nor do we routinely patch existing running versions of asterisk unless it is a critical security patch that could expose your system to harm.
This is the beauty of PIAF is you can do what you want with your system. You can stay put do nothing, patch it yourself, or upgrade it yourself.
Of course we always recommend you have a bare metal backup and you have tested the restoration out completely prior to making any changes to a system you depend on.
Please note that with Freepbx backup and restore there is a severe bug that prevents the correct restoration of some fields so at least on my fpbx 2.8 systems I do not rely on it. Mondo seems to be working now and I just did a backup and restore with it all seems to be fine.
As for the EXPERIMENTAL moniker.... we classify this program as experimental because we cannot predict how users have modified their systems and this sometimes can alter the use of this program. We test it extensively and we use it daily with good results. That being said we don't recommend the routine use of it EVER.
thanks for the report and I hope this has helped put things in perspective. BTW I have not noticed this behavior in my 1.8.3.2 system that was installed yesterday however I will try to duplicate it.
Best regards
Tom