Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Phone disconnects after 9 + outgoing call

Status
Not open for further replies.

cakestick

IS-IT--Management
Jul 25, 2003
41
US
Hello,

I'm currently running Merlin Legend 6.1 v11, and am having an odd problem when users dial 9 to get an outside line. It seems that randomly, after dialing 9 + phone number, the system will wait a few seconds before cutting off the line they are using. The line button on the phone will go out (both red and green), as if they never tried to make a call.

I vaguely remember that there is a transfer time when somebody dials 9 to get out, but even after having them wait 3 seconds before dialing the actual number, the issue still arises. This leads me to believe the problem is separate from any outside equipment issues.. any hints?
 
You probably want to look at either the Interdigit Timer parameter or (less likely) the LS Disconnect.

Do a printout of SYSTEM SETUP and look about 40 lines down. It's below the "Behind Switch Code" and above "Automatic Backup". If unadulterated, the line should look like:
Inter-digit Timers (seconds) : 5 24 24 10 10 10 10 5 5

____________________________
Any sufficiently advanced technology is indistinguishable from Magix. --Arthur C. Clarke (imbellished).
 
You may also have a defective line port on the Legend or line ckt from Telco, or possibly a loose connection on one of the lines in the pool. Find out if that condition occurs on one line or all the lines in the pool and go from there.

Hope this helps!

....JIM....
 
I think Syquest hit it, sounds like a line that's dead in the pool ..
(and yep, could be a bad CO port)

If your in PBX mode and you have the CO lines on the console, have the operator go through each CO/line button & confirm dial tone.

MrTelecom1
Living the AT&T/Lucent/Avaya issues
since 1979!
 
Looks like it's either a bad line coming into, or a bad port on my 100D blade. Before I put a call out to the provider, is there any way I can troubleshoot to determine which is the problem? It'd be easy with the real lines that are coming into the 408 blades, but I'm at a loss with T1 stuff.

If not, thanks anyway!
 
I had a similar issue. You would pick up the phone and dial the number but nothing would happen. I checked each line on the main console and found out that one of my lines was dead. I hope that helps you out.
 
cakestick:
How is the 100D configured?

Is the trunking conventional DS1 channelized as LS/GS or E/M?

If so you can access each channel (line/trunk) by using this test access code: *03 Test Trunk Access: maintenance pw† + logical trunk number (01 - 80), it will connect to the trunk and you should get DialTone if it is working. Or you can use
the Pool number assigned (70,890,891, etc.) then cycle thru the lines/trunks looking for no DialTone. Depending on the line configuration from Telco, they may also have a number assigned to the line. I would test the incoming also, see if you get ring-no-answer or ?.

† same as the system login pw.

Using one of the above methods should help you isolate the defective trunk(s) in the system. Let us know what you find.

....JIM....

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top