Interconnectech
Programmer
I've got a MiVoice Office 250/Mitel 5000 Release 6.1 that I'm hooking some analog centrex loop-start lines from AT&T up to. The problem I can't seem to get around (and that Mitel tech support can't seem to grasp what I'm trying to do), is that the digits are outpulsed too early in certain dialing scenarios. Here's every scenario I run into:
- Pick up handset
- Press 8/Outgoing button
- Begin dialing one of the following digit strings (X is any digit):
1) XXX (this is used to dial another department within the same Centrex group - it's the last 3 digits of a centrex number so departments can call each other more easily). This goes through without a hitch, although there is a pause waiting for more digits to be dialed.
2) 9 XXX-XXXX (This is local calling. 9 tells the CO you want to dial outside of your Centrex group to a non-Centrex line.) The problem is that the digits are outpulsed before the last digit is pressed. If you go ahead and dial the last digit after outpulsing, it's hit or miss whether the call goes through or not, and displays the number wrong in the SMDR logs and on your screen).
3) 9 1(XXX) XXX-XXXX (This is obviously long distance calling. 9 tells the CO you want to dial outside of your Centrex group to a non-Centrex line.) The system acts like this is a local call because the leading digit isn't 1, so the digits are outpulsed at this point 9 1(XXX) XX, and then everything else is after-outpulse DTMF. Again, this is hit-or-miss whether it actually goes through or not.
I tried setting up ARS on the 5000 thinking it would help solve my issues, which I've never dealt with before. Even after thinking I had configured it correctly, it still behaves in the same manner. Can someone walk me through how to set up ARS, unless there is a better solution? I am very familiar with the MCD ARS setup, and the 5000's is throwing me for a loop. Any help, insight, and suggestions would be greatly appreciated.
Regards,
Josh
- Pick up handset
- Press 8/Outgoing button
- Begin dialing one of the following digit strings (X is any digit):
1) XXX (this is used to dial another department within the same Centrex group - it's the last 3 digits of a centrex number so departments can call each other more easily). This goes through without a hitch, although there is a pause waiting for more digits to be dialed.
2) 9 XXX-XXXX (This is local calling. 9 tells the CO you want to dial outside of your Centrex group to a non-Centrex line.) The problem is that the digits are outpulsed before the last digit is pressed. If you go ahead and dial the last digit after outpulsing, it's hit or miss whether the call goes through or not, and displays the number wrong in the SMDR logs and on your screen).
3) 9 1(XXX) XXX-XXXX (This is obviously long distance calling. 9 tells the CO you want to dial outside of your Centrex group to a non-Centrex line.) The system acts like this is a local call because the leading digit isn't 1, so the digits are outpulsed at this point 9 1(XXX) XX, and then everything else is after-outpulse DTMF. Again, this is hit-or-miss whether it actually goes through or not.
I tried setting up ARS on the 5000 thinking it would help solve my issues, which I've never dealt with before. Even after thinking I had configured it correctly, it still behaves in the same manner. Can someone walk me through how to set up ARS, unless there is a better solution? I am very familiar with the MCD ARS setup, and the 5000's is throwing me for a loop. Any help, insight, and suggestions would be greatly appreciated.
Regards,
Josh
