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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
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:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-3070 
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-09 20:16 CST
====================================================================== 
Summary:                    [patch] 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0131769) p_lindheimer (reporter) - 2011-02-09 20:16
 https://issues.asterisk.org/view.php?id=18772#c131769 
---------------------------------------------------------------------- 
The uploaded patch ccss.patch is a suggested fix for this issue. It allows
CallCompletionRequest() and CallCompletionCancel() to always return 0, in
all cases a CC_REQUEST_RESULT or CC_CANCEL_RESULT is set to PASS/FAIL and
in the case of FAIL, I have added another CC_REQUEST_REASON and
CC_CANCEL_REASON with some reason information. Someone may have something
better for the reason code but at least this allows for proper return to
the dialplan so that it can be handled as needed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-09 20:16 p_lindheimer   Note Added: 0131769                          
======================================================================