New DDIs/extensions starting with 9 (trunk prefix)

[fissure]

Hi there,

we have a customer with an ICP 3300 running v7.0.9.5 (upgrade to v7.1 due soon).

Their existing extension numbers, match with the last 3 digits of their DDI numbers.

eg internally 401
externally 222401

They were just assigned a new range of DDI numbers by the telco, which contain 9xx, eg 2229xx

The customer would prefer to keep the internal extension number matching the end of the DDI equivalent.

This causes a problem, when calling outside numbers, which start with numbers which conflict with internal extensions.

If you try to call an outside number 9-222222, you end up calling extension 922 (the system is not waiting after the first 3 digits, to see if you are going to dial more).

We've looked in the online help under:
Dialing - Conflicting Numbers

For the COS the phones are in we have default values:
Dialing Conflict Timer = 3
Interdigit Timer value = 10

We tried adding an ARS rule for for 3 digits, say 920, with 4 to follow, but it said this conflicted with an extension.

It would take a rule for 9200 with 3 to follow, but then we'd need to add loads of ARS rules (which we tried through import, but failed).

We've looked at using 8 as the trunk prefix instead of 9, but that smacks of nastiness.

Can anyone provide any suggestions?

Is 'Dialing Conflict Timer' the way to go/does it operate even if the digits dialled so far have matched an extension number?

Thanks in advance.

 

[kwbMitel]

You will be stuck with adding the "Loads" of enties if you want to match the digits.

If you cant get import to work, range programming works fairly swiftly.

100 entries 9000 increment 1 3 digits to follow going the appropriate route will get it done fairly quickly.

The dialing conflict timer is engaged when you dial the extension number. The system will wait for more digits for the length of the timer before dialing the extension. You can dial a # after the extension number to speed the process.

Your customer will never be happy with this solution. I suggest you convince them to accept non-matching extensions that do not conflict. The dial 8 option is also viable. I have had customers go this route to avoid the 911 misdial with little problem.



There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!

 

[fissure]

Thanks kwbMitel,

my problem is, if you have an extension 921 and try to dial an external number 9212121, as soon as you dial 921 it starts ringing that extension, it doesn't seem to initiate the 3 second 'dialing conflict timer'.

Any idea if that is fixable/right?

I'm thinking maybe extension numbers aren't subject to the 'dialing conflict timer', or maybe outgoing trunk calls/ARS calls aren't.

Online help says:
Enter a value in the range of "2" to "5" seconds in increments of one second. This timer defines the length of time the system waits for a dialed digit when the digits dialed to that point do not form a unique number. If two numbers have the same leading digits, a conflict arises when a station dials the digits required to complete a call to the number with the least number of digits. Since the two numbers have the same leading digits, the system is unable to route the call to the first number because there is the chance that the caller may dial the remaining digits for the second number. If a pause in excess of the dialing conflict timer is detected, routing of the call to the first station will take place. The Dialing Conflict Timer value must be less than the Interdigit Timer value.

 

[Lundah]

Personally I'd just use a different first digit for the extension number, and set up speed calls for 9xx pointing to the new extensions. Yes, for that range of DDI's there's some confusion, but that's a smaller inconvienience than having a conflict in the system dial plan.

 

[Lundah]

And now that I think about my post above, it wouldn't work anyway.

 

[kwbMitel]

for your example

Ext 921

Ars Entry

921X +3 (just remembered wildcards are allowed)

dialing 921 internally should wait before dialing extension.

This is not so???

There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!

 

[fissure]

Thanks kwbMitel,

Adding an ARS entry for:

921X +3 helps (there is a pause after dialling 921, and # can be used to force the call through)

92X +4 doesn't (numbers starting 921 still go to ext 921)

92XXXXXX +0 doesn't (numbers starting 921 still go to ext 921)

I'd just rather add one ARS entry than loads, also, I can't range program if I use a wildcard:
Note: In order to use "range programming" to program dialed digits, the dialed digit string must contain only the digits 0 through 9 (*, #, N, X or Y cannot be used).

But at least we can suggest this, or suggest the alternate digit for trunks (eg 8)

 

[SteveBarrett]

Why ont you change the o/g access to another number e.g 0.This is what they use in Europe.

 

[slapin]

0 is reserved for an operator.
I'd recommend to cut the matching part to 2 digits. We have 4 digits extensions and 3 last digits of DID match. Nobody died.

 

[kwbMitel]

A range program of:

9210 +3 Increment 1 Range of 100 would take care of 921 thru 930 inclusively

Range of 500 would take care of 921-970

Loads of entries but only takes 1 by the programmer

*******************************************************
The secret to success is knowing who to blame for your failures.