|Summary:||ASTERISK-01393: when running asterisk as non root user, sip fails to bind to 0.0.0.0|
|Date Opened:||2004-04-10 20:19:25||Date Closed:||2011-06-07 14:10:19|
|Description:||IAX2 has no problems binding to 0.0.0.0, but sip doesnt like it.|
filling in an actual ip adres resolves this, but can't be used for dynamic ip adresses.
|Comments:||By: zoa (zoa) 2004-04-10 20:25:21|
== Parsing '/etc/asterisk/sip.conf': Found
Apr 12 03:13:51 WARNING: config.c:593 cfg_process: No '=' (equal sign) in line 54 of sip.conf
Apr 12 03:13:51 WARNING: chan_sip.c:6555 reload_config: Unable to get IP address for obelix, SIP disabled
== Registered channel type 'SIP' (Session Initiation Protocol (SIP))
== Registered application 'SIPDtmfMode'
== Parsing '/etc/asterisk/enum.conf': Found
By: Mark Spencer (markster) 2004-04-12 10:59:47
This has nothing to do with root or non-root. If you set the bind address to 0.0.0.0 or simply don't specify one, we still have to use "gethostbyname" on your hostname to know what IP address we originate our messages from. So, in short, this is a DNS configuration issue. Your hostname should resolve to an IP (see /etc/hosts)
By: zoa (zoa) 2004-04-14 08:24:19
It has something to do with root or non root, running as root it binds fine, running as non root, it doesnt bind. (it has a different behaviour).
About the DNS, you are probably very right, i just don't get why it works as root and refuses to work as non root.
By: Mark Spencer (markster) 2004-04-15 08:50:17
Why don't you try doing a "host obelix" as root and as non-root and see if it makes a difference. perhaps permissions are wrong on /etc/hosts or /etc/resolv.conf?
By: Brian West (bkw918) 2004-04-15 10:34:29
I agree its not a root non-root issue. Non root processes can bind to anything over 1024 ... it clearly can't find its own hostname.
By: zoa (zoa) 2004-04-15 12:40:40
i'll try all the above when i awake in a few days :)