On Fri, Jan 30, 2009 at 6:22 PM, Daniel-Constantin Mierla
<miconda@gmail.com> wrote:
Hello,
On 01/29/2009 07:04 PM, mayamatakeshi wrote:
Hello,
If I start a second instance of kamailio by mistake, if the cfg file instructs it to listen to tcp ports, the second instance will exit with something like this:
tcp_init: bind(7, 0x81b28ec, 16) on 127.0.0.1:5060 <http://127.0.0.1:5060> : Address already in use
But if the cfg file only instructs kamailio to bind to udp ports, the second instance will not exit. Is this a bug?
I'm curious because if we start kamailio and a udp port is in use by another application (not kamailio), kamailio will exit with
udp_init: bind(4, 0x819f274, 16) on 192.168.88.29 <http://192.168.88.29>: Address already in use
Why is that so?
probably is related to how the kernel allows applications to bind/listen to a port. At the end, the UDP socket is represented by a file descriptor that can have access rights. What is your OS?
Hi Daniel,
I'm using Fedora Core 5.
As you said, looking at the code (udp_server.c), I can see the error message comes from bind so this is probably some OS issue (I don't know much about linux yet), not a bug in kamailio. Thank you.
--
Daniel-Constantin Mierla
http://www.asipto.com