"Every time we run the update and installation script for APTUS it causes destructive modification of /etc/asterisk/extensions_custom.conf. This file is being modified in rather strange ways and the result is that custom dialplan contexts and their contents are reordered, lines become suffixed with " = " and other blocks are completely deleted.
Example:
[extens-and-ringgroups]
include => ext-group =
include => ext-findmefollow =
include => ext-local =
Original:
[extens-and-ringgroups]
include => ext-group
include => ext-findmefollow
include => ext-local
The script you are using employs some sort of parser which reads the entire file and then completely overwrites it. While some dialplan modifications are required to work, still, what is the merit of writing a full (and incorrect) parser when awk or sed would have sufficed to remove APTUS sections and a simple "echo >>" to append new sections?"
"Every time we run the update and installation script for APTUS it causes destructive modification of /etc/asterisk/extensions_custom.conf. This file is being modified in rather strange ways and the result is that custom dialplan contexts and their contents are reordered, lines become suffixed with " = " and other blocks are completely deleted.
Example:
[extens-and-ringgroups] include => ext-group = include => ext-findmefollow = include => ext-local =
Original:
[extens-and-ringgroups] include => ext-group include => ext-findmefollow include => ext-local
The script you are using employs some sort of parser which reads the entire file and then completely overwrites it. While some dialplan modifications are required to work, still, what is the merit of writing a full (and incorrect) parser when awk or sed would have sufficed to remove APTUS sections and a simple "echo >>" to append new sections?"
Written by client.