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
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
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)
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
WARNING: no fork mode
So you'll probably don't have any children for TCP...
Kind regards,
Carsten
2013/4/12 Jeremy Ardley jeremy.ard...@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
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,
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
Hi
Yesterday I got fatal: read error: Connection reset by peer to my git pull
command.
I thought it was only temporary network error, but same problem still exist
today.
I can however access other remote git repositories succesfully from the same
host.
--- #sip-router
10.58 mslehto hmm... I
Am Freitag, 12. April 2013, 12:52:17 schrieb Mikko Lehto:
Yesterday I got fatal: read error: Connection reset by peer to my git
pull command. I thought it was only temporary network error, but same
problem still exist today.
I can however access other remote git repositories succesfully from
Hello,
I just checked too, it's works to me fine.
2013/4/12 Henning Westerholt h...@kamailio.org
Am Freitag, 12. April 2013, 12:52:17 schrieb Mikko Lehto:
Yesterday I got fatal: read error: Connection reset by peer to my git
pull command. I thought it was only temporary network error, but
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 d...@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...
Am Freitag, 12. April 2013, 13:00:22 schrieb Henning Westerholt:
Am Freitag, 12. April 2013, 12:52:17 schrieb Mikko Lehto:
Yesterday I got fatal: read error: Connection reset by peer to my git
pull command. I thought it was only temporary network error, but same
problem still exist today.
Am Freitag, 12. April 2013, 16:43:29 schrieb Henning Westerholt:
I've decreased the runs of the cron runs for the doxygen generation, the
load should be much less now. I'll do a few more system maintenance tasks,
sip- router.org will be therefore not available for a few minutes. I'll
announce
Hi, I have troble with authentication on Kamailio using RADIUS
authentication. For configure freeradius and radiusclient I used this
tutorial:
http://www.kamailio.org/docs/openser-radius-1.0.x.html
In config file of freeradius I have enabled digest in modules. In
sites-available/default is
14 matches
Mail list logo
