[asterisk-bugs] [Asterisk 0014230]: [patch] Calls are not accepted from an outbound proxy

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14230 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14230
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-13 10:19 CST
Last Modified:              2009-01-15 04:09 CST
====================================================================== 
Summary:                    [patch] Calls are not accepted from an outbound
proxy
Description: 
find_peer does not make a match between a received invite and a peer if the
invite comes from the outboundproxy rather than directly from the host. 

For example if a peer has the following sip.conf:

[mytrunk]
host=sip.myitsp.net
port=5060
outboundproxy=nat.myitsp.net:5082

an invite from nat.myitsp.net:5082 is not matched to peer mytrunk

This is a problem for applications in which a natproxy is used for both
incoming and outgoing calls. 
====================================================================== 

---------------------------------------------------------------------- 
 (0097870) oej (manager) - 2009-01-15 04:09
 http://bugs.digium.com/view.php?id=14230#c97870 
---------------------------------------------------------------------- 
And why can't you add a peer for the outboundproxy to take incoming calls
and then separate on the To: header.

I know it's clumsy, but I don't agree with this way of doing it. The real
fix would be do recognize the incoming calls based on the domain you
register with and where the calls are coming from. The outbound proxy might
resolve by SRV or multilple A records to multiple IP hosts, so your patch
won't solve the problem at all for all cases. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-15 04:09 oej            Note Added: 0097870                          
======================================================================