[asterisk-bugs] [Asterisk 0015994]: Wrong handling of INVITE with Diversion tag when Asterisk has seen the callid before

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15994 
====================================================================== 
Reported By:                orn
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15994
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           Older 1.6.0 
JIRA:                       SWP-2325 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-30 14:18 CDT
Last Modified:              2010-10-06 07:13 CDT
====================================================================== 
Summary:                    Wrong handling of INVITE with Diversion tag when
Asterisk has seen the callid before
Description: 
Same scenario as 15095, but on 1.6 this time with very different (worse)
behaviour. Same hardware and operating system as that report.

When asterisk receives a call (via PSTN in this case), sends an INVITE to
a SIP proxy, that SIP proxy adds a Diversion tag and sends it back to
asterisk to get back to the PSTN, the call doesn't complete an asterisk
complains with a peculiar error:
[Sep 28 15:41:24] WARNING[32316]: chan_sip.c:4224 create_addr: No such
host: 5555555

5555555 is the number being forwarded to, and is nowhere specified as a
destination host.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015095 Behaviour when dealing with Diversion t...
====================================================================== 

---------------------------------------------------------------------- 
 (0127738) orn (reporter) - 2010-10-06 07:13
 https://issues.asterisk.org/view.php?id=15994#c127738 
---------------------------------------------------------------------- 
I've tested it multiple times again and it seems like 1.8 is handling this
correctly every time now -- it is handling the INVITE as a new call and not
sending any CANCEL messages.

Here's what it looks like now:

Asterisk                   Proxy
   |                         |
   |---------INVITE A------->|
   |                         |
   |<-------100 Trying-------|
   |                         |
   |<--INVITE B w/diversion--|
   |                         |
   |-------180 Ringing------>|
   |                         |
   |<------180 Ringing-------|
   |                         |
   |---------200 OK--------->|
   |                         |
   |<--------200 OK----------|
   |                         |
   |-----------ACK---------->|
   |                         |
   |<----------ACK-----------|

So, as I said above, I have no idea whether I misread the earlier capture
(or looked at the wrong one?) or what was going on, but my further testing
shows this behavior every time (though once I saw a 482 Loop detected, but
call processing was normal). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-06 07:13 orn            Note Added: 0127738                          
======================================================================