Summary:	ASTERISK-29278: Forensic Analysis on Asterisk PBX 13.5.0
Reporter:	Ajin A (aajin@deloitte.com)	Labels:
Date Opened:	2021-02-04 15:12:04.000-0600	Date Closed:	2021-02-04 15:12:05.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	. I did not set the category correctly.
Versions:	13.5.0	Frequency of Occurrence
Related Issues:
Environment:	Hosted in Linux machine	Attachments:
Description:	Hi, Currently, I am working on a case where some of the incoming calls into a toll-free number were diverted /routed into fraudsters. As per the IVR traversal report, the call was not landed on the agent desk. IVR is waiting for input from the customer. But actually during that time only the fraudster talk with the customer. I am new to the asterisk community. Requesting everyone's help for the following queries 1. Is it possible to route calls from asterisk to a GSM number/ IP phone    outside the network? 2. What are the logs available in asterisk to identify the root cause of this     issue? 3. What are the configuration files I need to analyze to identify the     configuration changes? 4. How to identify on which number the call are diverted/routed? Thank you
Comments:	By: Asterisk Team (asteriskteam) 2021-02-04 15:12:05.269-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2021-02-04 15:12:06.383-0600 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].