Interdigit timers

[NewNic]

I put in a PRI and had troubles with the call hanging for 5 to 8 sec before sending. I played with the Interdigit timers to resolve. Have no Idea exactly what these are doing. Avaya seems to think everything it to seceret. Grrrrrrrrrrr. Anyone know ? Heres what the book says

rogramming for interdigit timers is reserved for Lucent Technologies technical
support personnel or authorized dealers.
Interdigit timers are used by the MERLIN LEGEND System to determine when a
user originating an outside call has completed dialing the digits. The information is
necessary to allow the system to perform subsequent operations. You should not
change the factory settings for interdigit timers unless instructed to do so by
Lucent Technologies technical support or by an authorized dealer.

 

[merlinman]

OK, I can only give limited info based on what I have seen on other posts.

INTERDIGIT is for Loop and Ground Start lines, as I recall.

WITH PRI, you will want to look at LINES/TRUNKS > PRI > PROTOCOL > TIMERS....

And that's where my knowledge STOPS.

But I know that other folks on this BBS have tweaked that to do what they want...

Is this new enough that you can talk to AVAYA Tier 3?

 

[NewNic]

I was able to make it work with changeing the interdigit timers, but it was just from hacking. My experince with Avaya tac is poor. they will not give you any information, they just want to dial in and make the changes and say its
propriatary information. Id rather not deal with them

 

[coladmin]

I had a similar issue a while back where the PRI would basically time out waiting for digits and I had to adjust the T303 timer to be 8 seconds. There is still a long pause before the call goes out...but most people did not even notice. I am curious to hear how you fixed your issue

Thanks

COLADMIN

 

[NewNic]

I tried the PRI timers 1st. Then i went to the interdigit timers, i just started hacking one at a time. Timer 9 did the trick, i set it to 1 sec.

 

[coladmin]

thanks I will give that a shot

COLADMIN

 

[mikestl]

We just switched over from a T1 to a PRI (The pri doc in the faq section is awsome by the way, thanks!)and along with the PRI came the annoying delay after dialing the phone number. I adjusted the interdigit timers and that helped. The one I adjusted was actually interdigit timer 8. I set it to 3 seconds. Basically I believe that timer is the amount of time the system will wait for the person to dial an 8th digit. By that I mean the 8th digit not including the 9 dialed for ARS. While setting this timer down to 1 second would make the calls go out even faster, its also going make your employees have to be very quick on the draw to punch in an 8th digit when they are dialing for example 11 digits to call long distance.

Aside from this, someone mentioned adjusting PRI timers to make the call go out faster. Has anyone actually had any success with this? Timer...T313 I think it was comes to mind. I checked mine and it was already set to 4 seconds which is the lowest it would go. To me it seems like these timers were more along the line of timeout values, as in being the maximum ammount of time the system will wait if something goes wrong. It didn't seem to me like adjusting these timers any lower would speed things up. I'm not actually a phone tech though, so what I am saying could very well be incorrect.

Mike

 

[merlinman]

OK, here is a SECRET bit of info,

TO ELIMINATE THE DELAY, PRESS THE POUND (#) SIGN.

Let me know if that works.....

 

[mikestl]

Hey the pound sign thing does work here. Thanks. I guess a delay is just normal with a PRI? Seems like the delay is happening with the magix system rather than on the telco side. To me all this bussiness of changing interdigit timers, PRI timers, pressing pound etc seems like a bandaid fix for some poor coding on AT&T/avaya's part. Anyone with experience with other PBX brands such as Nortel know if they have the exact same issues with a PRI? If not then I'd hope Avaya is working on a software patch.

Mike

 

[NewNic]

LOL....No a delay is not normal. Im sure there is a correct way to rectify this issue, but none of us here are willing to pay Avaya to dial in...make a change and still not tell us what it was. shhhhhhh...top secret

 

[merlinman]

The interdigit timers were made accessable just for issues of delay.

In "older versions" they were there, but they were not adjustable, nor accessable.

When delay became an issue, we were given access to change them.

When a person dials a phone number, they have x number of seconds to do so. While they are dialing, touch tone SENDERS are being allocated. So, the TIMERS help control some one "HOGGING" the touch tone makers.

So, if you dial REALLY SLOWLY, you could be "kicked OFF" of the facility.

The call would attempt to complete, but the Central Office will give you an error.

As you can see, there are 9 interdigit timers.

INTER means BETWEEN, so, since a number can be as long as 10 Digits, then timer 1 is for the time between Dialed Digits 1 & 2, Timer 2 is for the time between Dialed digits 2 & 3, etc. (With Timer 9 for the time between digits 9 & 10.)

Also, let's just say you quickly dial 3 digits, and then stop. You have now started InterDigit timer number 3, so whatever that value is, you have that long to dial another.

So, if you dial (in a 7 Digit Number) 7 digits rather fast, then the Legend will not see the call as complete until the 7th ID Timer has expired.

Which also means, you could set ID Timer 7 to 1 second, and it would not seem to be an issue.

But what happens if you drag your dialing finger doing an LD call?

I have my Magix R 3.0 set for HOT DIAL PAD, a REALLY COOL FEATURE, I must say, and, without fooling with my interdigit timers, I hit the POUND Sign, and the call completes RIGHT THEN.

FYI....


As far as the LEGEND is concerned, the POUND SIGN has always forced a MANUAL END OF DIALING to the system.

I know it is wierd, but it is LEGEND.

The Bell Labs folks once said, "What, you don't dial a POUND SIGN when you dial a number?"

 

[mikestl]

Thanks for the info. The strange thing is, when we had the system set up on a standard T1, and you would dial a 7 digit number, the call would go through almost instantly rather than waiting for the coresponding interdigit timer to expire. Its like as if it knew what type of number you were trying to dial and would realize "ok, that was a local call, skip the interdigit timer and put the call through imediatly". I am not sure if this was ARS matching part of the number against a table or what.

So to me it seems like this is the issue. For some reason it when you switch it into PRI mode, it throws whatever logic out the window that it used when in standard T1 mode to skip past the interdigit timer. Could this have something to do with the fact that PRI mode throws in a second routing table that is similar to ARS that it must go through after the ARS table? Geesh I wish Avaya would just make the software the system uses open source so customers could fix their coding problems, remove avaya's gaping security holes and backdoor passwords they have hard coded in (for authorized avaya personell only of course), etc. *ok getting off my soapbox now and going for some more coffee*

Mike

 

[merlinman]

There are the TIMERS in the PROTOCOL part of PRI.

I really have not played with them, but they are WELL DEFINED in the Feature Reference.

Perhaps these are what you should try to tweak.