Huijun Yang wrote: > > >> If I had to guess I would go with invalid setting file. Try running > >> ant test-models > >> in neoconf and every plugin module that you changed. >> It should catch the error. > > Thanks for your help, Damian. > > "ant test-models" did pass, and so do the unit tests for sipXconfig, but > I still got error on user portal. I am looking into it. The following is > the partial exception. Not sure it means anything to you with a quick > look. >
I could not reproduce this problem in my working copy: it's a large patch and maybe there were some problems with applying it. I decided to fix RPM issue myself and commit it so that you can check-out a clean copy from subversion. For the record: it introduces 2 major changes that may cause new issues in provisioning polycom. (1) We now copy default configuration files in addition to generating polycom files (2) polycom plug-in is in its own directory I did not want to sit on those changes for too long since committing it makes all the patches pretty much useless. I hope it'll result in many fixes and improvements to polycom plugin. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
