rutileblue
09-01-08, 12:21 PM
I'm still trying to get my mind around what is possible with the Warp. (and, truth to tell, that's been kinda fun!) So please excuse/correct any ommisions or misunderstandings...
I'm trying to understand how you all are thinking units will get upgraded while keeping the unique settings needed for a particular site's configuration.
For example, If I use the Asterisk GUI to configure a WARP or have custom IVR voice messages, and then later use the warploader to upgrade the unit (say because a new version of Asterisk comes out), those configuration changes are lost (if the persistent image is replaced which most likely it ought to be to match the kernel and ramdisk). So that's a pain (and error prone) to re-enter all that information after each update... So how to solve that...
Maybe move those configuration changes into the make files etc in PADS so that the custom *.config files and/or recordings are part of the image? Possible. But then what about when a new version of PADS comes out? I have to re-apply my custom changes to the make files. That can be just as painful (and error prone as the make files get improved).
So I'm not sure how you all are thinking we users would/should apply changes to what you provide that meet the customer's unique needs, but still allow the customer to benefit from upgrades and improvements to PADS and/or Asterisk.
Thank you for any guidance!
I'm trying to understand how you all are thinking units will get upgraded while keeping the unique settings needed for a particular site's configuration.
For example, If I use the Asterisk GUI to configure a WARP or have custom IVR voice messages, and then later use the warploader to upgrade the unit (say because a new version of Asterisk comes out), those configuration changes are lost (if the persistent image is replaced which most likely it ought to be to match the kernel and ramdisk). So that's a pain (and error prone) to re-enter all that information after each update... So how to solve that...
Maybe move those configuration changes into the make files etc in PADS so that the custom *.config files and/or recordings are part of the image? Possible. But then what about when a new version of PADS comes out? I have to re-apply my custom changes to the make files. That can be just as painful (and error prone as the make files get improved).
So I'm not sure how you all are thinking we users would/should apply changes to what you provide that meet the customer's unique needs, but still allow the customer to benefit from upgrades and improvements to PADS and/or Asterisk.
Thank you for any guidance!