2 second delay before calls can be heard 1

Typically audio is not cut through until the 3300 determines that they have been answered. That is normally accomplished by answer supervision. Check your CO trunk circuit descriptor to see if what you have set for ignore answer supervision. If yes change to no. You may not be getting it from the CO. so you can always try setting fake answer supervision to yes.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

ok, thanks, ive given it a go but wont be able to tell if its worked untill we need to phone someone...

if your trunks are analog then the issue will be:

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. [highlight #FCE94F]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.[/highlight] 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.


**********************************************
What's most important is that you realise ... There is no spoon.

agree with kwbMitel. The system is waiting for answer supervision before providing audio. So either get it answer supervison or shut off the audio inhibit.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

This is all-so caused by setting the number of digits to follow to unknown in dail digits the system will not pass audio until it assumes you have finished dailing your number try pressing # at the end of the number if it work the you just need to reprogram your ARS

If its not broke tweak it..

Not caused by ARS.

ARS will cause a delay in dialling, not in voice cut thru.

The call has been dialled by the system, ARS is completed.

**********************************************
What's most important is that you realise ... There is no spoon.

I've changed the answer supervision so hopefully e problem will stop. The only way I will know if it's sorted is whether the problem continues so I will keep you informed . Thanks for the help.

problem stopped but now we have an echo for the first 2 seconds or so

did you look at the ARS ?

If its not broke tweak it..

^

I have dreamed a dream, but now that dream has gone from me.

Hovus don't discount what im saying, just because you may not have experienced this fault,



If its not broke tweak it..

I just don't understand your reasoning. The call is already connected per the OP's description. That being said, ARS is working properly. The problem at this point would either be CoS or issues with the lines themselves. I'd say run an LS measure test on the lines after hours and see if the problem persists.

I have dreamed a dream, but now that dream has gone from me.

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..

Yes i agree the call has connected but ARS may not have completed

Click to expand...

These 2 events are mutually exclusive. It is not possible for the call to be connected unless ARS has completed.

The 3300 will not seize the line until ARS has completed.

You may be thinking of a SX-200 and analog lines where line seizure can occur before the ARS is completed. This does not happen on the 3300.

**********************************************
What's most important is that you realise ... There is no spoon.

Yes in this case ARS has not completed leaving the call in a "digit outpulsing phase" not technically connected, what the OP has done is force the audio path open before the ARS has completed with the "Audio Inhibit Until Answer Supervision" option


If that was the case whats the purpose of "Digits Before Outpulsing" setting this to anything other than Blank causes the line to be seized and digits sent even before the user has completed dialing the number, if i remember correctly even Mitels wizard sets this option to 4

I experience this problem my self and it was caused by the installer importing ARS forms originally from a system with ISDN lines and the ARS settings not suitable






If its not broke tweak it..

You questions have led me to overlap outpulsing which is what I was refering to when I mentioned the SX-200.

I've never enabled, nor would I.

You questions may, and I stress may, be applicable if overlap outpulsing is enabled. If not, then not.

**********************************************
What's most important is that you realise ... There is no spoon.

Never worked on the sx-200

But that is an interesting comment pretty much all the systems a have worked on have this set to 4 digits im wondering if its a uk thing

If its not broke tweak it..

UK Thing?, Can't say, sorry.

Regarding the echo issue, I might try setting my trunks to 600 ohm instead of National.

**********************************************
What's most important is that you realise ... There is no spoon.

I have always had issues with analogue trunk settings; especialy Echo and Initial Delay

Years ago I set the following changes from the default:

Dis con timer 100
Calling Party Disconnect - No
Ringing expected - No
Release supervision expected - No
Audio Inhibit Until Answered supervision - No
High Loss Option - Yes
Drop digit receiver..... - Yes
Trunk Category - Unknown

Once the easy LS measure tool was introduced I found that cured most problems. I wrote myself the following reminder for programming:

1)
Within System Config/Trunks/Analogue Trunks/Loop Trunks/CO Trunk Circuit Descriptor
Leave all settings as Default but add :
Milliwat Tone as - 01291 611 6000
and
Silence tone as - 01291 611 6010
2)
Within System Config/Trunks/Analogue Trunks/Loop Trunks/Analogue Trunk Assignment
Change Auto Select to ON (And note the PLID)
3)
Within Maintenance and Diagnostics/Line Quality Measurement
Run Test on Individual Line and choose the relevant PLID
The Trunk will make a phone call to the Mitel test numbers, make measurements and then program the Circuit Descriptor with the correct values.
It will also advise re the echo status of the line Green, Yellow or Red