[asterisk-bugs] [Asterisk 0009225]: sip doesnt bind to all

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9225 
====================================================================== 
Reported By:                junky
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9225
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:            1.4.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             03-07-2007 10:45 CST
Last Modified:              01-19-2008 10:49 CST
====================================================================== 
Summary:                    sip doesnt bind to all
Description: 
if you set your bindaddr=0.0.0.0 in sip.conf this supposes to bind to all
addresses (WAN and LAN).
In this scenario, if the wan cant get an ip, it will disable the stack.


module reload chan_sip.so
  == Parsing '/flash/asterisk/configs/sip.conf': Found
  == Parsing '/flash/asterisk/configs/users.conf': Found
[Dec 31 19:01:48] WARNING[1070]: acl.c:383 ast_ouraddrfor: Cannot connect
[Dec 31 19:01:48] WARNING[1070]: chan_sip.c:16474 reload_config: Unable to
get own IP address, SIP disabled

It should listen to lan adresses even when the wan is down.

But setting the bindaddr=192.168.0.10 works perfectly.



====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 01-19-08 10:49  
---------------------------------------------------------------------- 
BTW, the specific issue is that we're relying on the routing mechanism to
tell us what our address should be, and when there is no default route
(which would be the case when the interface on which a default route is
configured is not up), this mechanism fails. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-19-08 10:49  Corydon76      Note Added: 0080898                          
======================================================================