[asterisk-bugs] [Asterisk 0010313]: Chan SIP and ACL Source Based Routing

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=10313 
====================================================================== 
Reported By:                bfsworks
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   10313
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.9  
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 69944 
Request Review:              
====================================================================== 
Date Submitted:             2007-07-26 18:22 CDT
Last Modified:              2010-09-14 14:51 CDT
====================================================================== 
Summary:                    Chan SIP and ACL Source Based Routing
Description: 
If asterisk is connected to two ISP connections statically. SIP
registrations fail and ACL reports cannot connect. Asterisk uses the
routing table and does not pass a source ip to the table and all routing
will default to the default route or gateway. If a SIP registration comes
in on ISP1 and the default route is for ISP2 then any and all responses go
out ISP2. 
====================================================================== 

---------------------------------------------------------------------- 
 (0126954) lmadsen (administrator) - 2010-09-14 14:51
 https://issues.asterisk.org/view.php?id=10313#c126954 
---------------------------------------------------------------------- 
I don't believe anything has been done to correct for that really. This is
starting to sound like a feature request to me, but we'll triage it and
figure out what to do with it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-14 14:51 lmadsen        Note Added: 0126954                          
======================================================================