Beofre I do that, is there a way i can understand the phone book ordering (which books get loaded in what order) for a phone? I would thing that a preference order of some type in how the books and speed dials are displayed might have a bearing on the failure. I dodn't see anything in the wiki to explain phonebook ordering (which get loaded first and the order they are displayed)
If I don't hear anything, i'll open the bug anyway. Thanks, Tony. >>> Damian Krzeminski <[EMAIL PROTECTED]> 06/09/08 09:45AM >>> Tony Graziano wrote: > I am using 3.10.1 stable. 3.10.2 is not production/stable yet so I > haven't gone there. > > I did: > > sipxconfig.sh --database drop-index > sipxproc -r ConfigServe > > Which didn't help. After looking in the sipxconfig.log I saw: > > "2008-06-09 > 09:28:39,879":ERROR:AbstractProfileManager:?:org.sipfoundry.sipxconfig.phonebook.PhonebookManagerImpl$CsvFileFormatError: > Too few columns. required columns First name, Last name, Number > > The phone beloneged to a group, and I had a couple of test phone books > assigned to the group. After deleting them, it worked fine. They loaded > without issue in 3.81, but something must have happened. > > So the lesson learned here is that an incorrectly formatted phonebook > csv file will keep any speeddial's from being pushed onto the config of > a Polycom phone I guess. The sipxconfig.log is your friend. > It's still a bug though. sipXconfig should report but ignore the problems in external phonebook files... Do you mind opening an issue? Thanks, D. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
