[asterisk-bugs] [Asterisk 0014294]: [patch] X-Asterisk-Hangupcause header only in challenged BYEs

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14294 
====================================================================== 
Reported By:                klaus3000
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   14294
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 169203 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-21 04:41 CST
Last Modified:              2009-01-28 08:58 CST
====================================================================== 
Summary:                    [patch] X-Asterisk-Hangupcause header only in
challenged BYEs
Description: 
Hi!

The X-Asterisk-Hangupcause is added in transmit_request_with_auth()
function, but not in transmit_request(). Why?

IMO, the Hangupcause header should be added to all BYE requests
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0013385 [patch] Reason header support
====================================================================== 

---------------------------------------------------------------------- 
 (0098957) klaus3000 (reporter) - 2009-01-28 08:58
 http://bugs.digium.com/view.php?id=14294#c98957 
---------------------------------------------------------------------- 
works for me, thanks. I think a logical next step would be to 
- make these headers a config option
- support for reading this headers with a config option (avoids loss of
hangupcause information due to multiple cause code mappings) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-28 08:58 klaus3000      Note Added: 0098957                          
======================================================================