How to display non-extension numbers

[VinceWhirlwind]

If I want to find a spare extension, I do a "locate all free dn 1000 to 1099".
 
The problem is, somebody has used the DID form to send incoming calls to certain extension numbers (that are not assigned to anybody) onto a hunt group.
 
so the DID form looks like this example:
0298761001 --> 1001
0298761002 --> 1002
0298761003 --> 1003
0298761004 --> 6650
 
I am forever finding "1004" as spare and assigning it to a new extension and then discovering that the number is being used.
 
How do I prevent this from happening? How do I get 1004 to NOT show up in the "locate all free dn..." command, in this example?

[VinceWhirlwind]

I guess I should explain, the reason I put this here is that I provision users using MiCollab, from Windows AD.
 
So what I *really* want is something that will tell MiCollab that a number is unavailable. There are a few ways of doing that, presumably some of them I don't know about...
 
This system will be upgraded to v7 soon, but it's on v6 for the moment.

[ZuluAlpha]

In the case above, you cannot use ext 1004 because it is a DID and instead of having an extension 1004 for the DID it goes to hunt group 6650?

[VinceWhirlwind]

Yes, so in that example, a LOCATE ALL FREE DN 1000 TO 1099 will tell me that 1004 is free. But it isn't. It's being used as an external number that goes to a Hunt Group.
How do I tell the controller that 1004 isn't free, without actually using a licence by configuring an extension for it?
I can't seem to think of a proper way of managing this.
There are various similar cases that cause the same problem.

[johnp]

Create a speed dial 1004 that dials the same as the DID. This should keep it from showing as available

[sarond]

Create a speed dial 1004 that dials the same as the DID. This should keep it from showing as available

^^^^^^^^^^
This

[VinceWhirlwind]

OK, I was never a fan of using the DID form for this kind of thing - if you use the DID form, the target number is not internally dialable.
If I leave the DID form just sending stuff to the correct internal numbers, then I can have a Speed Dial for any that don't exist and need to be forwarded elsewhere.
Much better.
 
Is there any drawback to using heaps of speed dials?

[sarond]

Speed dials was always a common method of assigning a DID.

The advantage of setting it in the DID form is that it should correctly show the DID on outbound calls.
Although there are ways around this as well with CPN Substitution.

On a new site I will normally create the last 4 digit of the DID as extensions (number plan permitting) absorb the required digits from the trunk to route incoming calls. For outgoing DID to display I program DID ranges for CPN Substitution.

Each to their own really, there are always mores ways than 1 to achieve your goal.

[johnp]

I like the DID table, makes it easier when you get a we want calls for this number to go elsewhere when they are setup as a digit match. Yes it will populate the user and you can choose to use it as outbound display in an easy fashion. The only fail on Mitel's side is if you delete the user, the DID get removed from the form.

[VinceWhirlwind]

The only fail on Mitel's side is if you delete the user, the DID get removed from the form.

Yes, this drives me nuts.