asterisk users - Jan 2005 - troubles with getting odbc to load data

Hi

I'm using asterisk 1.0.3_1 from the freebsd ports.

Everything works ok, except I can's get res_config to populate sip.conf
(or any other conf file for that matter).

my unixodbc works and I can access the database with the isql tool. There
are no warnings or anything else in the asterisk log file indicating a
problem.

I have used the guide from http://www.voip-info.org/wiki-Asterisk+res_config.

res_config_odbs.conf:

[settings]
table => ast_config
connection => asterisk

res_odbc.conf:
;;; odbc setup file

[settings]
dsn          = asterisk
USER         = asterisk
Password     = <password>
loguniqueid  = yes
pre-connect  = yes

extconfig.conf:
[settings]

;uncomment to load queues.conf via the db engine.
;queues.conf => odbc
sip.conf => odbc

odbc.ini and odbcinst.ini should be ok, as i can access the mysql database
with the isql commandline tool.

I have an empty sip.conf in the asterisk directory, owned by root
(asterisk is startet as root).

in the full log fil I get:

Jan 14 09:58:45 NOTICE[30105]: Loading Config sip.conf via odbc engine
Jan 14 09:58:46 VERBOSE[30105]:   == Creating H.323 Endpoint
Jan 14 09:58:46 NOTICE[30105]: Binding: sip.conf to odbc
Jan 14 10:00:08 NOTICE[30156]: res_odbc loaded.
Jan 14 10:00:08 NOTICE[30156]: Registered Config Engine odbc
Jan 14 10:00:08 NOTICE[30156]: Binding: sip.conf to odbc
Jan 14 10:00:08 NOTICE[30156]: res_config_odbc loaded.
Jan 14 10:00:08 NOTICE[30156]: Loading Config sip.conf via odbc engine
Jan 14 10:00:08 VERBOSE[30156]:   == Creating H.323 Endpoint
Jan 14 10:00:09 NOTICE[30156]: Binding: sip.conf to odbc
fido|ttyp0:/usr/local/etc/asterisk#

so no indications that there is a problem, but a "sip show users"
shows no
users at all, just:

Connected to Asterisk 1.0.3 currently running on fido (pid = 30105)
fido*CLI> sip show users
Username         Secret           Accountcode     Def.Context     ACL  NAT
fido*CLI>

I have used the load_res_config.pl tool to add my old (working sip.conf)
to mysql.

any idees as to where the problem might be or how to further debug it is
most welcome.

thank you

/Rasmus