[SR-Users] Kamailio 4.0 & Asterisk realtime (Failed to import bind_ob, auth: qop set, but nonce-count ...)

Daniel-Constantin Mierla miconda at gmail.com
Fri Jun 7 11:20:28 CEST 2013


Hello,

first, as pointed in other related discussions in this mailing list, it 
might be better to use a different approach if you start everything from 
scratch. That will be doing all signaling handling in kamailio and use 
asterisk only as media server. Practically all user data is in kamailio, 
routing to asterisk only when needed for media services. The tutorial is 
more targeting existing asterisk deployments. Nevertheless, see more 
comments inline.

On 6/5/13 10:59 PM, Thomas Martin wrote:
> Hello,
>
> being new to Kamailio, I have been closely following Daniel's tutorial 
> "Kamailio 4.0.x and Asterisk 11.3.0 Realtime Integration using 
> Asterisk Database",
> hoping to be able to setup a basic SIP server with voicemail-boxes 
> attached to the the accounts. (Eventually, UACs that live behind 
> either port-restricted or
> symmetric  NATs should be supported (i.e. experience two way audio), 
> so, I guess, eventually "WITH_NAT" needs to be defined and rtpproxy 
> needs to be
> installed as described in the "Run your own Skype-like service in less 
> than one hour" tutorial... ?)
>
> Anyway, I am encountering a couple of difficulties in an early stage 
> and hope for some insights form the experts:
>
> 1) Even though launching Kamailio with "/etc/init.d/kamailio start" 
> seems to succeed ...
>
> root at jm1:~# /etc/init.d/kamailio start
> Starting Kamailio:
>  loading modules under 
> /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/
>   Listening on
>              udp: 127.0.0.1:5060
>              udp: 178.254.20.156:5060
>              tcp: 127.0.0.1:5060
>              tcp: 178.254.20.156:5060
> Aliases:
>              tcp: rv1192.1blu.de <http://rv1192.1blu.de>:5060
>              tcp: localhost:5060
>              udp: rv1192.1blu.de <http://rv1192.1blu.de>:5060
>              udp: localhost:5060
>              *: jingle-me.org <http://jingle-me.org>:*
>
> kamailio started.
> root at jm1:~#
>
> ... SIP Clients (I have tried several) cannot register and receive the 
> response: 401 Unauthorised.
>
> cat /var/log/syslog yields:
>
>
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: rr 
> [../outbound/api.h:49]: *Failed to import bind_ob*
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: rr [rr_mod.c:159]: 
> outbound module not available
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: usrloc 
> [hslot.c:53]: locks array size 512
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: auth 
> [auth_mod.c:350]: auth: qop set, but nonce-count (nc_enabled) *support 
> disabled*
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: <core> 
> [udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 229376
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: <core> 
> [udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: <core> 
> [udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 229376
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2180]: INFO: <core> 
> [udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142
> Jun  5 21:59:01 jm1 /usr/sbin/kamailio[2200]: INFO: ctl 
> [io_listener.c:225]: io_listen_loop:  using epoll_lt io watch method 
> (config)
>
> I suspect that the "INFO: auth [auth_mod.c:350]: auth: qop set, but 
> nonce-count (nc_enabled) *support disabled*" hints to the problem, but 
> have no clue how to fix that.
It should go fine with this message (to try to get rid of it, paste here 
the module parameters for auth and auth_db modules). Anyhow, the logs 
you provide are from startup. You have to get the logs when the phone 
attempts to register. Set debug=3 in your config, restart and then 
register with a phone, you should see lots of log messages. Paste them 
to mailing list if you cannot sort out the issue by yourself.

>
>
> 2) Kamailio does _not_ start on boot-up, even though 
> "/etc/init.d/kamailio start (stop/restart/status)" work(s), and 
> /etc/default/kamailio looks like this:
>
> RUN_KAMAILIO=yes
> USER=kamailio
> GROUP=kamailio
> SHM_MEMORY=64
> PKG_MEMORY=4
> SSD_SUID=no
> DUMP_CORE=no
>
> Right after a re-boot, root at jm1:~# chkconfig kamailio yields: 
> "kamailio on",
> however, root at jm1:~#/etc/init.d/kamailio status yields: "Status of 
> Kamailio: kamailio is not running." at this time.

Can you do "ps auxw | grep kamailio" and see if kamailio processes are 
listed?

Cheers,
Daniel
>
> Any hints are appreciated!
>
> Best regards,
>
> -Thomas
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
   * http://asipto.com/u/katu *

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130607/07450296/attachment-0001.html>


More information about the sr-users mailing list