| Summary: | ASTERISK-26967: Billsec is not as expected- Asterisk 13 | ||
| Reporter: | Altmisha a Azam (altmish) | Labels: | |
| Date Opened: | 2017-04-25 15:41:52 | Date Closed: | 2020-01-14 11:13:51.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | CDR/General |
| Versions: | 13.14.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Libss7, dahdi, Asterisk, CentOS | Attachments: | |
| Description: | I am using asterisk 13, I called on my extention after playing some prompt call is getting forwareded to another user after disconnection of the call in CDR mysql there duration is 19 as well as billsec is also 19.
In other hand if i m using Asterisk 11 then duration is 19 and billsec is 9. This is correct as per my requirement. Please help me to solve the above issue as i want bill sec as in asterisk 11 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-04-25 15:41:52.907-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2017-04-26 09:37:26.466-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Asterisk Team (asteriskteam) 2017-05-10 12:00:01.796-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||