I hope this fix is only intended for your development env. :) Isn't kind of going back in time the change from UTF-8 to LATIN1? Wouldn't it bring other issues regarding non ASCII characters in CDR?
- MM On Sun, Mar 6, 2011 at 20:06, Mircea Carasel <[email protected]> wrote: > > > On Sat, Mar 5, 2011 at 12:44 AM, Matt White <[email protected]>wrote: > >> >>> Mircea Carasel 03/04/11 1:46 PM >>> >> > >> > >> >After install I made sure that I checked : Enable Call Detail Records in >> CDR >> >service page >> >Also I made sure that I have the postgres odbc driver: psqlodbc.so >> installed >> >and located in/usr/lib >> > >> >When I make calls I would expect that my SIPXCDR database to be >> populated, >> >but this does not happen >> > >> >Does anyone have any clue? >> >> >> >> >> If you set the proxy log to debug you might be able to see where the issue >> is. I recently had a fresh build where CDR was empty and the proxy log >> revealed it was unable to load psqlodbc.so >> >> >> I recent update to the psql package had changed the name to >> psqlodbcw.so...so a softlink to the old name fixed my issue. >> >> >> Well, in my case it was a different problem but also related to postgres > odbc driver. I had [unixODBC] client encoding missmatch error which looks > like it was related to an incompatibility between my postgres version > (8.4.4) and the odbc linux driver that I installed. The driver was too old > Anyway, I fixed my problem by changing the encoding: > > alter user postgres SET client_encoding to LATIN1; > > Thanks, > Mircea > >> -M >> >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
