We are in the process of setting up a Mitel SX200 MX Revision 4.0. We have the PRI programmed and have been doing some testing.
Now we are able to make are out bound local and toll calls but when you try to call in on the DID it gives a fast busy (rejection) The only way we can get around this is by inputting either an VM box or Extention under Vacant under the forms. The problem is that all DID's will only ring to that extention.
What we are trying to do is allow the DID to ring to the extention for EX: DID 123-456-4185 Needs to ring to EXT 4185 But its not allowing us to do this. We want each DID to ring to its corresponding EXT/Station What forms do we need to change. By the way the PRI is on the T1 DID/Tie .
I think you will have to create an extension under vacant & call fwd it to the desired extension via the console. DID's on a sx200 aren't the most friendly. Hope this helps.
Now the Hospitality Package that is in reference to this device is this why we cannot get the DID's to ring to the certain extentions on there own?
In form 15, how many digits are you expecting?
Are you SURE the carrier is ending the right digits?
Are you set up for caller ID??
If not, the carrier is sending * ANI * DNIS, and your system is looking for an extension that begins with *
Is this embedded PRI or is it in a peripheral bay?
Embedded PRI
And I will look at what I have in form 15 a second time. Will add in a second.
I have the PRI on Bay 5 Slot 2 CCT 1
All 23 channels are in and I am using COS 7 COR 1 Ten 1 N 4 which the CO is giving us 4 Digits (Telnet is the CO) M 0 X (right now for X we have #6 as we were trying another route in regards to Digit Translation. The MOSS Info has Lodging which we cannot unload. And then CDN 2 is being used. What am I missing here. They were saying something about a * is what was being sent from the CO?
When we did the print out of the calls trying to come in we were getting:
Date - Time - Duration - Trunk Number - *** *906
337
in which 906 is the area code.
The * is the first digit of the * ani * dnis pattern.
Go to the class of service of the trunk, and enable option 811 (ANI Trunk).
That tells the system to ignore the *ani*, and just react to the dnis.
Given the information. This option is already Enabled. I'm just curious how a normal call is supposed to look under the print.
For some reason its not allowing the DID to route to the proper Extention
What we need is for ex:
DID 906-444-4185 to ring to Extention 4185 And everything is setup in COS correctly and trunks are there. But do I need to use Form 55 Digit Translation Table or can I just delete what I put in there and ignore it?
I have the PRI on Bay 5 Slot 2 CCT 1
All 23 channels are in and I am using COS 7 COR 1 Ten 1 N 4 which the CO is giving us 4 Digits (Telnet is the CO) M 0 X (right now for X we have #6 as we were trying another route in regards to Digit Translation. The MOSS Info has Lodging which we cannot unload. And then CDN 2 is being used. What am I missing here. They were saying something about a * is what was being sent from the CO?
When we did the print out of the calls trying to come in we were getting:
Date - Time - Duration - Trunk Number - *** *906
337
in which 906 is the area code.
As long as you have an extension number, that matches the DID digits exactly, the call will route right to the extension.
If you insert the access code for the DID routing table, in the "X" column, the DID digits then must match an entry in that table.
If you want to do an unusual test, create ext
*906 in form 9, and see if an incomiing call routes there!!