Extension Conflict with Station/Superset

[GatorIT]

We inadvertently changed the extension number of a device on the Desktop Device Assignments form.

This happened to be the superset so when we go to change it back we get the following message:
"Access code XXX conflicts with a station or SUPERSET prime number"

Can someone point us in the right direction? Possibly we will need to remove the superset flag, change the extension and then add back?

 

[kwbMitel]

Details please! (assuming sx-200 ICP)

What was the DN before changing?

What are you trying to change it back to?

What numbers in form 35 start with the same sequence of digits?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[GatorIT]

Yes, SX-200 ICP.

The extension was 120 previously and it's 119 now since it won't let us change back to 120.

Form 35 shows that there is a 119 Access Code defined as a SUPERSET and 120 defined as a Station. All of the other extensions are SUPSERSETS as well.

 

[GatorIT]

Maybe it would be easier to direct our inbound calls to extension 119 for the time being until we can figure out how to change the extension back to 120. What menu allows you to configure DIDs to extensions?

 

[kwbMitel]

The system is telling you that another station (analog) has been assigned ext 120.

2 mistakes?

You cant have 2 instances of the same number.

If you want the superset to be 120 then the existing 120 must be changed to some other number first.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[GatorIT]

Where would the 120 station be changed? Menu 35 appears to just display information. Here are two screenshots of Menu 35 and the Expand Set configuration of the device in question.

Does anyone offer phone/remote support for Mitel?

 

[kwbMitel]

Based on your screen shots, I think this may be a wild goose chase.

Both 119 and 120 will ring the station in question.
120 looks like it is possible just a phantom extension used for the purpose of having a message waiting indicator on the phone as well.

Back to the drawing board.

Instead of telling us what you think is wrong, tell us how it should be functioning and what is not functioning. I feel you may not be giving us the whole picture here.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[GatorIT]

kwbMitel,

I certainly appreciate your help so far. What's happening is that the main BTN rings straight to the night greeting.

Actually I found extension 120 by using the find ext function in Desktop Device Assignments. That is labeled "main number".

When night mode is off, it should ring directly to what is now EXTN 119. I'm trying not to ask questions but how can I determine what extension the "day" (non-night) calls go to? If I can determine that I can change extension 119 back to what it should be...right?

 

[GatorIT]

Call Rerouting Table - Menu 19

 

[kwbMitel]

Most likely issue is that system is in night mode and shouldn't be.

If that is not the case,

What type of trunks?

If analog trunks what are the termination points for the trunks for day and night in form 14.

If Digital trunks, and 120 is a DID, find ext 120 in form 9 (Esc-2 = Find Ext). Then make note of the tenant for ext 120 and post the form 19 image of the tenant routing for 120.



**********************************************
What's most important is that you realise ... There is no spoon.

 

[GatorIT]

I have confirmed that the system is not in night mode, at least based on the normal way it is applied - the user at extension 120 has a button.

We are working with digital trunks. 120 is now a DID - I changed it back to 120 because that's what it had to be before.

Here is Sub-Menu 09 Expand Set for EXTN 120:

Here is Menu 19 for tenant 1: