On Fri, 2008-09-26 at 11:21 -0400, Raymond Dans wrote: > In 3.11.6, SipXConfig now generates the configuration files for the > various processes. For The Call Resolver, the velocity file read in > is called "callresolver-config.vm" and produces the file > "sipxcallresolver-config". > > Historically the Call Resolver configuration file was named > callresolver-config and as a result, the component currently expects > this name. This is the reason that the configtest is failing for the > Call Resolver. > > Was there any reason for changing the name of its configuration file? > Why was the velocity file name not also changed? If it is to remain > as sipxcallresolver-config then I'll open a Jira issue and change both > the software and the process xml file to now look for the new name. > > Thanks > Raymond >
Raymond, Sounds like a typo to me. sipXconfig should produce the file expected by the service, in this case callresolver-config. I'll check in a fix for that today. Would you mind opening a Jira issue if one doesn't currently exist? Thanks Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
