[asterisk-bugs] [Asterisk 0018772]: CALLCOMPLETION(cc_monitor_policy) has no affect after the call attempt ends

[Asterisk Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18772 
====================================================================== 
Reported By:                p_lindheimer
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18772
Category:                   Core/CallCompletionSupplementaryServices
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!): 306575 
Request Review:              
====================================================================== 
Date Submitted:             2011-02-08 15:44 CST
Last Modified:              2011-02-08 15:44 CST
====================================================================== 
Summary:                    CALLCOMPLETION(cc_monitor_policy) has no affect
after the call attempt ends
Description: 
In my scenario, my goal is to not set any CallCompletion settings in
sip.conf (or other channel specific files). Instead, I am using
CALLCOMPLETION() function to set all the settings on call setup based on
information in AstDB for both the Agent (caller) and the Monitor (target
extension(s) I am calling.

I am finding that the setting appears to take based on the debug messages
but as soon as I hangup the call (in a scenario where the target extension
is NOANSWER) the settings get forgotten and everything gets dumped thus I
can never campon the call. As soon as I set the cc_monitor_policy against
the target device I am calling in sip.conf, everything works. However, this
should not be necessary.

EXPECTED BEHAVIOR:

any cc_monitor_* setting that is set with CALLCOMPLETION() function should
'stick' to any devices that you attempt to call at least for the purpose of
any subsequent call back attempts that are to be made to that target
extension such that no channel specific settings are needed. (This is
important for scenarios like hot-desking where it may change depending on
who is logged onto a device).

I have added a call trace without cc_monitor_policy set in sip.conf and
then with it set to show the difference.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-08 15:44 p_lindheimer   New Issue                                    
2011-02-08 15:44 p_lindheimer   Asterisk Version          => SVN             
2011-02-08 15:44 p_lindheimer   Regression                => No              
2011-02-08 15:44 p_lindheimer   SVN Branch (only for SVN checkouts, not tarball
releases) => 1.8             
2011-02-08 15:44 p_lindheimer   SVN Revision (number only!) => 306575          
======================================================================