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 jeremy.ardley@gmail.com 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?
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 95, Issue 47
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 jeremy.ardley@gmail.com 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?
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 95, Issue 47
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
"WARNING: no fork mode"
So you'll probably don't have any children for TCP...
Kind regards, Carsten
2013/4/12 Jeremy Ardley jeremy.ardley@gmail.com:
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 jeremy.ardley@gmail.com 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?
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 95, Issue 47
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@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:
Listening on tcp: 192.168.44.66:55060 Aliases: <snip>
WARNING: no fork mode and no udp listen address found
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@ng-voice.com wrote:
"WARNING: no fork mode"
So you'll probably don't have any children for TCP...
Kind regards, Carsten
2013/4/12 Jeremy Ardley jeremy.ardley@gmail.com:
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 jeremy.ardley@gmail.com 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?
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 95, Issue 47
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Carsten Bock CEO (Geschäftsführer)
============================================================= Visit us on the Kamailio World 2013, April 16th & 17th => http://conference.kamailio.com/k01/ See you there! =============================================================
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Dave,
When not in daemon mode ,only udp is available. and you can see more clue within the log file.
2013/4/12 David Wilson dw@zaq.com.au
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:
Listening on tcp: 192.168.44.66:55060 Aliases: <snip>
WARNING: no fork mode and no udp listen address found
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@ng-voice.com wrote:
"WARNING: no fork mode"
So you'll probably don't have any children for TCP...
Kind regards, Carsten
2013/4/12 Jeremy Ardley jeremy.ardley@gmail.com:
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 jeremy.ardley@gmail.com 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?
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 95, Issue 47
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Carsten Bock CEO (Geschäftsführer)
============================================================= Visit us on the Kamailio World 2013, April 16th & 17th => http://conference.kamailio.com/k01/ See you there! =============================================================
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@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.
Hello,
Have you loaded pv module?
Cheers, Daniel
Daniel-Constantin Mierla http://www.asipto.com
On 15 Apr 2013, at 06:31, David Wilson dw@zaq.com.au wrote:
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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Daniel,
That was it. Painfully obvious now that pv stands for pseudo-variable.
I've started by adding modules only as I need them which helps my understanding of the structure of the system, but generates the occasional issue.
Thanks for the tip.
Dave.
On 15/04/2013, at 6:24 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
Have you loaded pv module?
Cheers, Daniel
Daniel-Constantin Mierla http://www.asipto.com
On 15 Apr 2013, at 06:31, David Wilson dw@zaq.com.au wrote:
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.
Jeremy,
"Is it running?" was a very sensible question, especially since I said I was running from the command line. I'm actually using a second terminal to monitor the host while the first one is running kamailio in the foreground.
I like to work from the command line until the config is right, then I'll run the service.
Thanks for the tip on ss, but it also reports nothing listening on 55060 (or 5060).
Without the grep, netstat shows me other processes listening for TCP (on different ports). Other evidence is that a connection attempt fails.
'disable_tcp=yes' is NOT active. When it is (I checked) Kamailio doesn't report that it's listening on TCP.
Dave.
On 12/04/2013, at 3:11 PM, Jeremy Ardley jeremy.ardley@gmail.com wrote:
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 jeremy.ardley@gmail.com 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?
-
Carsten Bock -
Daniel-Constantin Mierla -
David Wilson -
Humming Zheng -
Jeremy Ardley