[Home]

Summary:ASTERISK-12983: After receiving a 302 Temporarily Moved response, call is not sent in to users defined context
Reporter:Jon Webster (jon)Labels:
Date Opened:2008-10-29 14:47:43Date Closed:2011-06-07 14:08:06
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Transfers
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 302temporarly_moved.log
( 1) no_302temporarly_moved.log
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.



****** ADDITIONAL INFORMATION ******

The patch from issue 13523 has been applied.

Attached files:
1) A call that processes a temporarily moved request and incorrectly spawns extension (inbound,4167,1)
2) A call that does not process a temporarily moved request and correctly spawns extension (exchange12,4167,1)


[general]
context=inbound

[exchange12]
type=friend
host=66.192.107.236
disallow=all
allow=ulaw
transport=tcp
port=5065
promiscredir=yes
insecure=port,invite
context=exchange12
Comments:By: Russell Bryant (russell) 2008-10-31 06:14:29

Give the latest code in the 1.6.0 branch a try.  I think this issue may have been fixed after the 1.6.0 release.

$ svn co http://svn.digium.com/svn/asterisk/branches/1.6.0 asterisk-1.6.0
By: Russell Bryant (russell) 2008-10-31 06:16:14

Nevermind, I now see in your description that you applied the patch that I'm talking about ...
By: Leif Madsen (lmadsen) 2009-02-13 13:19:14.000-0600

Pinging the original reporter. Have you had a chance to try testing with the latest 1.6.0?

I will close this issue in 7 days if no response.

Thanks!
By: Jon Webster (jon) 2009-02-15 23:27:21.000-0600

Works in latest 1.6.0
By: Joshua C. Colp (jcolp) 2009-02-16 08:28:03.000-0600

Closed per reporter. Issue has already been fixed.
By: Mark Michelson (mmichelson) 2009-02-16 17:11:09.000-0600

Re-opening at request of reporter.
By: Jon Webster (jon) 2009-02-16 17:17:35.000-0600

Don't think i reloaded sip.conf the first time I tested this. Confirmed it's still an issue in 1.6.0 branch, r175952
By: Joshua C. Colp (jcolp) 2009-04-28 09:20:06

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.