Thanks DaveSin,
I was afraid that was going to be the only option.
The 1444e9e4e7ce.cfg string seems to be a reference generated by the Obi database to reference the file uniquely. I will try to remove and add the device after backing up the config.
RonR, thanks for the quick response... I am not sure if the configURL was the reason that my Obitalk changes would not push the expert config to the device, but that parameter does not get reset to default value if you have disabled the Obitalk Provisioning at some point thereby clearing that field. (or maybe I deleted it manually in one of my tweaks). Thanks anyway, I will try to store it safe this time so as not to loose it.
Update - The trick worked. I have the updated ConfigURL populated and the expert configuration is also being pushed to the device now.