![]() | |
| |||||||||||||||
| |||||||||||||||
| Mitel Ask Questions and Find Answers on Mitel Systems: |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #31 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Thanks.Switch is ax 200 digital.Its copper trunck,any number local and ld.Brief ARS is digit 8 ARS line is 2to 9 xxx followed by 7 digit,trunk group is 1 and all copper trunks (9 lines) defined under same trunk group.Out of 5 , 4times it takes 1 to 2 minutes for call to get connected. Some solution or advise will highly appriciated | ||||||||
| | |
| | #32 (permalink) | |||||||||
| Moderator ![]() ![]() acejavelin is a high-tech, heavy metal redneck!
Location: North Dakota Rep Power: 2 ![]() | Quote:
1) Check all the trunks with a butt-set to verify ALL 9 are OK at they PBX system block. If this just started on a working system and nothing else has changed, this could be a issue with a bad trunk from telco, probably the first trunk in the trunk group. 2) Check Trunk Circuit Descriptriptors in Form 13 to verify they are all correct, especially DTMF setting. I would also set the Guard Timer to 2000ms, and enable No Seize and No Release Alarms at least temporarily to look for individual trunk issues 3) Check your trunks COS for option 802 (Limited Wait for Dial tone) is enabled, and System Option 48 (Limited Wait For Dial Tone Timer) is set less then 5 seconds (I usually set for 1 sec). Also verify that System Options 47 & 50 are not set very high (5 Seconds is normal). 4) Turn on Traffic Reports in maintenance, and check them for individual trunk issues Also, if you have 9 trunks, you must have two trunks cards, try swapping them around. I would also verify the local dial plan is 10 digits for local calls. 1 to 2 minutes is an EXTREME amount of time for a call to complete, this should be easy to track down especially if it happens 4 out of 5 times. Normally slow call completion on analog trunks is an ARS issue, but there are no timers for ARS that even go that high (at least by default), so I would look at a trunk issue. Using the SMDR Monitor in maintenance maybe helpful well troubleshooting also. If this just started, I would try a system reset only after a valid backup has been completed. The older Digital systems were floppy disk based, and they are getting very old and tired now, some do not survive a reboot because of disk/drive issues. This was the Digitals main downfall, most would still be running if it wasn't for the drives... Last edited by acejavelin; February 16th, 2009 at 08:01 AM. Reason: added detail... | |||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| configure a console | johnson | Meridian Systems | 1 | May 14th, 2008 12:31 PM |
| Need a help to configure PRI in 81c | 43215241 | NORTEL | 5 | July 7th, 2007 03:28 AM |
| Can't Get ITG Card to configure | websrfr | Meridian Systems | 1 | June 13th, 2005 03:27 PM |
| ITG 2.1 won't configure | epsilon6 | Meridian Systems | 4 | July 20th, 2004 07:50 PM |
| How to Configure PRI to be B8ZF | Diny | Meridian Systems | 10 | December 20th, 2002 08:15 AM |