Re: [Bayonne-devel] SIP configuration error with Bayonne 20050116...

[Daniel]

<cc: on reply, please>

Hi Aymeric,

On 16 Mar 2005, Aymeric Moizard <address@hidden> wrote:
> In the file: /etc/bayonne/drivers.conf, you have the "realm"
definition.
> These are the login/password for SIP Digest Authentication:
> 
> auth_user
> auth_passwd
> auth_realm
> 
> The number of "auth_user" must equals the number of "auth_passwd"
> as well as the auth_realm, else there is probably a bad
configuration.
> 
> These information will be used when sending REGISTER that needs
> authentication.
> 
> Aymeric

Thanks kindly for the quick reply.  However, as I mentioned farther
down in my first email, I already thought to look for that and listed
just one of each in the 'etc/drivers.conf' file:

  auth_user = someuser
  auth_passwd = somepasswd
  auth_realm = somerealm

Truth be told, as I wrote, I think the whole SIP issue might be a red
herring, and the real problem might be the inability of Bayonne to find
the right config files (since note how it prints, with my source
modification, that 0 users, passwords, and realms are find, even though
the above are listed; and also how it ignores invalid SIP port without
printing the warning from the source code).  However, I'm not sure why
it's missing the right files, since the 'etc' directory is correctly
listed when the server starts:

  SERVER VERSION 20050116; i686 Linux 2.4.26-1-686
  TGI VERSION 3.0; driver(s)= sip; etc=/home/someuser/Bayonne/etc/
  Loading TGI plugins...

I've also tested all the command-line parameters such as '--keypath',
'--sysconfdir', and '--sysconfig', and they all point to the correct
'etc/' directory or correct files in it.  Anyway, so I'm back to the
main issue likely being problems with Bayonne finding my config files,
though everything looks good.

Thanks for your help.  Anyone have ideas how to proceed though, please?

Take care,
Daniel

Full output of configuration step for bayonne:

./configure --prefix=/home/someuser/Bayonne \
 --sysconfdir=/home/someuser/Bayonne/etc --without-odbc \
 --without--postgres --without-mysql --without-ltapi --without-aculab \
 --without-openh323 --without-dialogic --without-vpb --without-capi \
 --without-users --without-xml --without-nodes


Full output of trace, listed again:

SERVER VERSION 20050116; i686 Linux 2.4.26-1-686
TGI VERSION 3.0; driver(s)= sip; etc=/home/someuser/Bayonne/etc/
Loading TGI plugins...
tgi: initialized; uid=116, pid=17840, buffers=32
tgi: control=/var/run/bayonne/bayonne.ctrl; cfd=4; time=10
Loading DSO plugin images...
debug: trace module loaded
sip device driver loaded
loading default trunk group
Compiling default scripts...
playrec: 30 steps compiled
playrec: 3 steps initial
record::initial: 13 steps compiled
record::record: 26 steps compiled
record::replace: 18 steps compiled
record: 1 steps initial
Configuration reloaded
Starting sip driver...
sip driver starting 16 ports
number of users: 0
number of passwords: 0
number of realms: 0
Configuration error: number of realms does not match number of users
drivers started for 16 port(s)
normal startup
fifo: path=/var/run/bayonne/bayonne.ctrl
Bayonne/20050116 running
trace: pid=16386 reason=11
trace(0):
/home/someuser/Bayonne/lib/bayonne/20050116/bayonne.bin(_ZN3ost5Debug10stackTraceEi+0x2e)
[0x807d98e]
trace(1): /home/someuser/Bayonne/lib/bayonne/20050116/debug/trace.dso
[0x40019852]
trace(2): /lib/libpthread.so.0 [0x40334825]
trace(3): /lib/libc.so.6 [0x403a3678]
trace(4):
/home/someuser/Bayonne//lib/libeXosip.so.3(eXosip_event_wait+0xb6)
[0x4054cfad]
trace(5):
/home/someuser/Bayonne/lib/bayonne/20050116/drivers/sip.dso(_ZN3ost12SIPUserAgent9uaProcessEv+0x32)
[0x404f8e02]
trace(6):
/home/someuser/Bayonne/lib/bayonne/20050116/drivers/sip.dso(_ZN3ost9SIPDriver3runEv+0xc8)
[0x404ee178]
trace(7):
/home/someuser/Bayonne/lib/libccgnu2-1.3.so.1(_ZN3ost10ThreadImpl17ThreadExecHandlerEPNS_6ThreadE+0xc2)
[0x401efc52]
trace(8): /home/someuser/Bayonne/lib/libccgnu2-1.3.so.1 [0x401eeb6f]
trace(9): /lib/libpthread.so.0 [0x4032ee51]
trace(10): /lib/libc.so.6(__clone+0x5a) [0x404516ea]
driver stopping service thread(s)