netstat is a bit tricky. Luckily it's now obsoleted by ss Try netstat -a -n | grep 5060 Also check if your kamialio.cfg file has "disable_tcp=yes" Comment it out if it does. P.S. I only asked about whether it was still running because it can easily die on startup if the scripts detect some error like the control files still exists. I just checked now on my system which I installed using 'official' RPMs for Centos 6. The 'service kamailio restart' command appears to work but fails quietly for the following reason Apr 12 14:55:40 sentinel /usr/sbin/kamailio[7501]: ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) On 12/04/13 14:37, David Wilson wrote: _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi Carsten, I would expect that if it didn't have children, it wouldn't report that it's listening. However, you have asked the right question... On my command line, I was using the -D flag to prevent daemon mode. When I configure to ONLY listen for tcp, I get: With that clue, I tried it without the -D flag, configured for both tcp and udp... now it is verifiably listening for tcp! So, it turns out that with -D, the report that it is listening is inaccurate. Thanks for your suggestion! Dave. On 12/04/2013, at 4:48 PM, Carsten Bock <carsten(a)ng-voice.com> wrote: [ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) quite that obvious! the io watch method (auto detected) is initially 229376 is finally 262142 Ctrl-C. that it is listening on port 5060 for both TCP and UDP. I see the same behaviour with the default cfg. and an attempted connection is rejected consistent with there being no open socket. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi All, Using Kamailio 4.0.0 with a minimal configuration, trying to get some logging to help me understand the system, I can get static log messages easily enough with log, but now want something more useful. When I use this route (xdbg example from the tutorial): route { xdbg("SIP Request: method [$rm] from [$fu] to [$tu]\n"); } the log file shows these messages: DEBUG: <core> [sr_module.c:935]: DEBUG: init_mod: xlog DEBUG: <core> [main.c:2539]: Expect (at least) 13 SER processes in your process list DEBUG: <core> [route.c:927]: fixing xdbg() DEBUG: <core> [pvapi.c:390]: PV <$rm> is not in cache DEBUG: <core> [pvapi.c:269]: PV cache not initialized, doing it now ERROR: <core> [pvapi.c:761]: error searching pvar "rm" ERROR: <core> [pvapi.c:965]: wrong char [m/109] in [$rm] at [2 (0)] ERROR: xlog [xlog.c:363]: wrong format[SIP Request: method [$rm] from [$fu] to [$tu]#012] and Kamailio shuts down. Have I missed something obvious? Cheers, Dave. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

netstat is a bit tricky. Luckily it's now obsoleted by ss Try netstat -a -n | grep 5060 Also check if your kamialio.cfg file has "disable_tcp=yes" Comment it out if it does. P.S. I only asked about whether it was still running because it can easily die on startup if the scripts detect some error like the control files still exists. I just checked now on my system which I installed using 'official' RPMs for Centos 6. The 'service kamailio restart' command appears to work but fails quietly for the following reason Apr 12 14:55:40 sentinel /usr/sbin/kamailio[7501]: ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) On 12/04/13 14:37, David Wilson wrote: > Hi Jeremy, > > Thanks for the suggestion, I'm hoping I haven't overlooked something quite that obvious! > > The last debug output I see on startup is: > >> Listening on >> udp: 192.168.44.66:55060 >> tcp: 192.168.44.66:55060 >> Aliases: >> <snip> >> >> WARNING: no fork mode >> 0(20372) INFO: <core> [tcp_main.c:4833]: init_tcp: using epoll_lt as the io watch method (auto detected) >> 0(20372) INFO: usrloc [hslot.c:53]: locks array size 512 >> 0(20372) INFO: <core> [udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 229376 >> 0(20372) INFO: <core> [udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142 > netstat shows listening for UDP on 55060, but nothing on TCP: > > $ netstat -l | grep 5060 > udp 0 0 192.168.44.66:55060 *:* > > ps shows four kamailio processes running, all of which end when I Ctrl-C. > > Cheers, > Dave. > >> Date: Fri, 12 Apr 2013 14:22:45 +0800 >> From: Jeremy Ardley &lt;jeremy.ardley(a)gmail.com&gt; >> Subject: Re: [SR-Users] Kamailio 4.0.0 not listening on TCP >> >> >> Have you checked to make sure it's still running? >> >> >> On 12/04/13 14:19, David Wilson wrote: >>> Hello All, >>> >>> New to Kamailio, I'm running 4.0 on Ubuntu 12.04 (precise). >>> >>> Running from the command line with a minimal config, it tells me that it is listening on port 5060 for both TCP and UDP. I see the same behaviour with the default cfg. >>> >>> However, netstat does not list anything listening on TCP port 5060 and an attempted connection is rejected consistent with there being no open socket. >>> >>> Any suggestions on where I need to be looking to fix this? >>> >> >>