Yes i agree the call has connected but ARS may not have completed, ARS completes when the number of digits to follow in the ARS digits dialed has been reached, or the inter-digit timer on the COS for that device (10 secs by default) has expired.
When making a call using alog lines and the number of digits to follow is set to unknown the call gets left in a limbo state until the inter-digit timer expires this does not happen on ISDN due to the Call Proceeding / Ringing messaging sent back.
As per KwbMitels Post
CO Trunk Circuit Descriptor:
- Audio Inhibit Until Answer Supervision
This option is used to prevent a DTMF receiver, in line split mode, from being connected between the originating party and the outgoing trunk during the digit outpulsing phase of the call processing cycle. It is used for sites that are tied to very sensitive central offices or remote PBXs. When enabled, the audio path is fully connected and the two parties will be able to talk only after the answer supervision has taken place. Select "Yes" if a DTMF receiver, in linesplit mode, is NOT to be connected between the originating party and the outgoing trunk during digit outpulsing. Select "No" if a DTMF receiver, in linesplit mode, IS to be connected between the originating party and the outgoing trunk during digit outpulsing.
If the OP has indeed now set this option to NO, the call is still in and i quote "outpulsing phase of the call processing cycle" until ARS in completed hence now why he gets echo from the line for 2 secs and not no audio.
I do not mind being proven wrong by the OP, but i have seen the same symptom out in the field cause by ARS.
If its not broke tweak it..