[asterisk-bugs] [Asterisk 0013803]: After receiving a 302 Temporarily Moved response, call is not sent in to users defined context

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13803 
====================================================================== 
Reported By:                jon
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   13803
Category:                   Channels/chan_sip/Transfers
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-10-29 14:47 CDT
Last Modified:              2009-04-28 09:20 CDT
====================================================================== 
Summary:                    After receiving a 302 Temporarily Moved response,
call is not sent in to users defined context
Description: 
These calls are coming from asterisk 1.4 using IAX through asterisk 1.6 to
an MS Exchange Unified Messaging server. The UM Server is redirecting the
call to asterisk.


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

---------------------------------------------------------------------- 
 (0103875) file (administrator) - 2009-04-28 09:20
 http://bugs.digium.com/view.php?id=13803#c103875 
---------------------------------------------------------------------- 
After further examining the logs everything is working exactly as it
should. In one case a 302 Moved Temporarily is being used WITH a REFER. In
that scenario since the 302 Moved Temporarily essentially dials based on IP
address the sections in general are used, which sets the context to
inbound. When it performs the REFER (blind transfer) it thus uses inbound.
In the second scenario the peer is dialed directly and NO 302 Moved
Temporarily happens. This means the context used is the one configured in
sip.conf for that peer, exchange12. When it performs the REFER (blind
transfer) it uses that configured context, exchange12. Everything is
working exactly as it is configured and exactly as it should. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-28 09:20 file           Note Added: 0103875                          
2009-04-28 09:20 file           Status                   assigned => resolved
======================================================================