Summary:	ASTERISK-28289: Feature: Allow detection of inband progress for outbound channels
Reporter:	Corey Farrell (coreyfarrell)	Labels:
Date Opened:	2019-02-13 10:23:58.000-0600	Date Closed:	2019-12-30 11:53:24.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Applications/app_dial
Versions:	13.25.0 GIT 16.2.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) beep-beep-beep.ulaw ( 1) func_sit.c
Description:	I've created a dialplan function which adds a framehook to detect inband progress tones in pre-media of outbound channels. My current implementation is a dialplan function which adds the framehook, so dialplan might be as follows: {noformat} [sit-hook] exten => s,1,Set(SIT_WATCH()=1) same => n,Return() [default] exten => _X.,1,Dial(${TRUNK}${EXTEN},30,b(sit-hook^s^1)) {noformat} The value set to SIT_WATCH is currently ignored, in the future this might allow specifying which types of tones should be recognized.  So far I've tested using Local channels calling Playtones without answering.  The busy and congestion tones both result in DIALSTATUS=BUSY.  The 'info' tone results in DIALSTATUS=CONGESTION. I have not been able to test against a "real" busy or fast busy call, I have tested against a call that plays the info tone (beep-beep-beep the number you have dialed is out of service).  This is not detected as CONGESTION.
Comments:	By: Asterisk Team (asteriskteam) 2019-02-13 10:23:59.197-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. 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. By: Corey Farrell (coreyfarrell) 2019-02-13 10:25:26.147-0600 beep-beep-beep.ulaw was extracted from a PCAP of a real life call (to/from Verizon NY if that matters). By: Corey Farrell (coreyfarrell) 2019-02-13 10:26:56.161-0600 func_sit.c is functional (DSP issues aside).  Not ready for gerrit yet - it needs xmldoc for the function, probably needs to handle arguments for enabling busy/congestion detection. By: Corey Farrell (coreyfarrell) 2019-12-30 11:53:24.297-0600 I'm not confident this can be made reliable so I don't want to support it.  I've helped the customer understand that reporting is only as accurate as information provided by the telco.