Summary:	ASTERISK-04944: [request] [post 1.2] answeronpolarityswitch
Reporter:	inix (inix)	Labels:
Date Opened:	2005-08-31 12:19:09	Date Closed:	2011-06-07 14:02:54
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I would like to suggest that you guys modify the answeronpolarityswitch option to be a little more flexible. For example, we can retain current behaviour for answeronpolarityswitch=yes and answeronpolarityswitch=no. I suggest we add a answeronpolarityswitch=mixed. This will allow Zaptel to correctly answer when there is a polarity switch, and also state the call as answered when there is no polarity switch. Coming from where I'm from, the Telco provides Polarity switch only for chargeable numbers. This causes a problem when we're calling Toll-Free numbers as * will always be in a Calling State. When * does not send Answered to the SIP phone, we will not be unable to perform Transfers, On Holds. To resolve this we can set zaptel to answeronpolarityswitch=no. However, that will lead to a errornous CDR. With organisation that does interbilling, this is highly undesirable. With answeronpolarityswitch=mixed, * can then reset the billable seconds correctly. For the Toll Free numbers, * will still set the call as Answered, but the call-accounting can make adjustments for it. For your kind consideration please.
Comments:	By: Kevin P. Fleming (kpfleming) 2005-08-31 12:24:05 This doesn't make any sense; if the call is already in 'answered' state (because it doesn't need to wait for a polarity switch), then receiving a polarity switch cannot 'answer' it again. What you really want is to update the CDR (only) when receiving the polarity switch on a call that was already answered, which is an entirely different issue, and wouldn't be part of the 'answeronpolarityswitch' setting as it's currently defined to operate. By: inix (inix) 2005-08-31 12:30:41 You're quite right. using answeronpolarityswitch=no solves all my issues but the CDR, and it was my concern which I brought this up. Again, if there is anyway to reset the CDR for billable seconds, that should also do. I'm sure there are many people facing the issues I'm facing where loopstart, groundstart and kewlstart are not supported. Cheers! By: Michael Jerris (mikej) 2005-09-09 20:12:03 This feature request has revcieved no response.  Please move this featrue request to the bounties page on the wiki, or attempt to contract the work out if you are unable to create a patch yourself.  Feel free to re-open this bug if there is a patch to review.