> While investigating XCF-3554 <http://track.sipfoundry.org/browse/XCF-3554> :"Change domain name does not update voicemail.xml hence user fails to deposit voicemail", I found that the problem was not only applicable to voicemail, but also to any services that has dependence on domain name.
> Currently, when domain name is changed, only a few services' configurations, such as ivr service, proxy, registrar, etc. are replicated, but all other services that have dependence on domain name are not notified about the changes. > Given domain name change is a critical change for the whole system, I think we should > 1) push ALL service/locations profiles upon domain changes rather than trying to indentify and replicate only for SOME services > 2) as device( phone and gateway) profiles also contain domain information, we should re-generate the device profiles as well, otherwise, the phone profiles will be left with invalid domain info, unless user regenerate them. After a second thought on this, we probably should NOT force re-generating device profiles in this case. As there are many cases, such as dialplan changes, pickup code changes, etc. yet we do NOT force to regenerate device profiles, but leave it to the user, why should we treat this case differently? We'd better to keep it in a consistent way, not to force regeneration of device profiles upon domain changes. cheers, Huijun
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
