[asterisk-bugs] [Asterisk 0014344]: Outbound proxy not used for registrations

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14344 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14344
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1-beta4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-27 05:15 CST
Last Modified:              2009-01-27 06:17 CST
====================================================================== 
Summary:                    Outbound proxy not used for registrations
Description: 
If callbackextension is defined for a peer it successfully causes a
registration to occur but the registration ignores the outboundproxy
settings for the peer
====================================================================== 

---------------------------------------------------------------------- 
 (0098836) Nick_Lewis (reporter) - 2009-01-27 06:17
 http://bugs.digium.com/view.php?id=14344#c98836 
---------------------------------------------------------------------- 
The obproxy_get() function that is called during registration really needs
to be passed a peer so that peer specific obproxies can be used during
registration. The problem at the moment is that the registration string
(whether directly from sip.conf registration string or generated by a peer
with callbackextension) does not contain a peername field. For a number of
reasons this needs to be added. It could be something like:

register=peername?transport://user@domain:authuser:secret@host:port/callback~expiry

This would also allow other parameters omitted from the registration
string to be taken directly from the peer definition 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 06:17 Nick_Lewis     Note Added: 0098836                          
======================================================================