[asterisk-bugs] [Asterisk 0014725]: Asterisk doesn't add Route headers in NOTIFY when the SUBSCRIBE came from a proxy

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14725 
====================================================================== 
Reported By:                ibc
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14725
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-23 12:05 CDT
Last Modified:              2009-07-10 10:56 CDT
====================================================================== 
Summary:                    Asterisk doesn't add Route headers in NOTIFY when
the SUBSCRIBE came from a proxy
Description: 
Client ---- Proxy ---- Asterisk

The Client sends a SUBSCRIBE (Event: dialog) and the Proxy routes it to
Asterisk adding "Record-Route" header.

The correct behaviour would be:
1) Client sends SUBSCRIBE to Proxy
2) Proxy routes SUBSCRIBE to Asterisk adding Record-Route
3) Asterisk replies 200 and mirrors Record-Route in the reply (correct)
4) Proxy routes teh 200 to the Client
5) Asterisk sends an in-dialog NOTIFY containing a Route header (with the
value of the received Record-Route).
6) The proxy routes the NOTIFY to the client.

But Asterisk fails in step 5 since the NOTIFY generated by Asterisk
doesn't contain a Route header.

Of course, that NOTIFY MUST contain a Route header since it's in fact an
in-dialog request, and the dialog was created using loose_route (the
request forming the dialog, the SUBSCRIBE, had Record-Route inserted by the
proxy).
====================================================================== 

---------------------------------------------------------------------- 
 (0107571) svnbot (reporter) - 2009-07-10 10:56
 https://issues.asterisk.org/view.php?id=14725#c107571 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 205776

_U  trunk/
U   trunk/channels/chan_sip.c

------------------------------------------------------------------------
r205776 | mmichelson | 2009-07-10 10:56:45 -0500 (Fri, 10 Jul 2009) | 16
lines

Merged revisions 205775 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
  r205775 | mmichelson | 2009-07-10 10:51:36 -0500 (Fri, 10 Jul 2009) | 10
lines
  
  Ensure that outbound NOTIFY requests are properly routed through
stateful proxies.
  
  With this change, we make note of Record-Route headers present in any
SUBSCRIBE
  request that we receive so that our outbound NOTIFY requests will have
the proper
  Route headers in them.
  
  (closes issue https://issues.asterisk.org/view.php?id=14725)
  Reported by: ibc
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=205776 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-10 10:56 svnbot         Checkin                                      
2009-07-10 10:56 svnbot         Note Added: 0107571                          
======================================================================