My new telecom provider is going to charge us a fortune to have our DNIS digits as anything other than the last four digits of the toll-free number they are assigned to. (ie 800-999-9999 has DNIS 1501 not 9999) The problem is that our toll-free numbers are not unique in that format and are only unique at 10 digits.

My PBX vendor is saying we can only route 7 DNIS digits because the system only allows 7 digit extensions, speed dials, etc.... It doesn't make sense to me that the PBX can accept 10 digits but we can't route on them...Any advice?? I played with ARS etc with no luck....

Our system is a Mitel 3300 ICP....

I don't know at 3300 ICP but at SX 2000 LW this can be done if you are using a PRI card wich can be programed at incoming digits translations with IMAT software. If you want I can check to see how many lines can be programed in that tabel.(not too many).

If ya got PRI it's set via IMAT , if its other than 3300 . If ya got external DSU/NSU it's set via IMAT . If ya got embedded T1 and it's 7.0 or higher it's set via CPN forms . I think you may need to ask someone other than the person you asked at your VAR . Try calling their office and ask for the SM or go to Mitel.com and post a question . Hope this helps . Your PRI will be down because you have to reset the card . Takes about 5 minutes ! by the way . Please complete your profile . You left out some important info . Thanks

Default modified entries form is 10 modified numbers , Using IMAT , 3300 CPN I think is 100 . I think !

I reread your post . I think I understand it now . You can strip and insert via your TSA form . Better left to your local professional Mitel Tech's . Are you a Network guy?

I reread you post too, and I must say that I misslead you with the setings in IMAT because those are for outgoin CPN Setup and I think you need incoming digit translations but If your provider route to your 3300 only the last 4 digits and if yoou have 2 (or more) tool numbers with the same last 4 digit (in your example you have 9999) you can't solve the problem only if they deliver as many digits to make the numbers you receive unique because you probably want to ring at diferent extensions (answer points). I think it may help to give more informations about the DID number ranges and all tool free numbers and the extensions (answer points) you want for them.

The path of least resistance would seem to be to absorb the first 3 DNIS digits (usually 800-888 etc.), then route based on the remaining 7 digits.
As long as the last digits don't conflict, you could absorb as many digits as possible!

Yes
I think if you go to TSA you can absorb whatever is needed .You can then build your Hunt groups or ACD Paths . Then enter those digits as your TSA incoming targets . P O C right ?

That's my whole problem...I am not unique at 7 digits...ie. 800-397-8888 & 888-397-8888....They both need to take different paths unfortunately.

I want to shoot the person that planned this number scheme....

What if you used the first 7 digits to route the call? The Mitel will route the call as the digits are received, reacting to the first 7, and ignoting the last 3.
Is that a possibility?

That will probably work! What form(s) do I need to look at for this? Hopefully my vendor will know this answer but they haven't come up with anything yet; I want to be specific on how to do this....

Using your example, program the digits "8003978" or "8883978"as the speed dial, hunt group, or ACD path (whichever option you were going to use).

Do I not need to tell it to ignore the last 3 anywhere?

You can't have it ignore just the last 3 . If the calls reside on the same PRI you are sol . One entry per TSA sorry . But there's a work around some where . You could front end with a vm call processor and use that to direct to differnt groups . It would also give you TOD/Holiday control ! Just a Thought !

Nevermind...I understand now....However I just discovered we are not unique on the first 7 either for all numbers invovled....

Does anybody know why Big Telcom Man charges so much for custom translation? I have never had this problem with other providers....

You would have to name a provider . Just don't bad mouth them here . It's not allowed ! Also fill in the blanks on your profile , please !

I think on SX-2000 this can be done !
As I said before I never worked with 3300 so I don't know there, but if at 3300 is the Form named : "Node Identity Assignment" (NO) like at SX-2000 I think this can be done at 3300 too. Maybe Mr. OBTW can say if this is posible at 3300 too.
The second condition is of course that your provider routes all 10 digits or at least the last digits that can make a diference between the toll free numbers - in your example at least the last 8 digits.
There are much more particulary conditions especially your internal and external plan number and how many normal DID range number (not toll free) with the same first 6 digits you have.
The idea is that we can make the diference from the 2 toll free numbers in your example by absorbing diferent amout of digits from behind and remaining with maximum 7 digits so that we cam internaly route them.
To understand exactly I continue your example with the supose that you have the only 2 toll free numbers (is posibly with 4 too) and only one DID range of 1000 numbers with the same 6 digits in front , example 343 545 xxx .
1) Ask your provider to route all 10 digits to you.
2) In the "Trunk Service" form for the DID trunks you write 0 in digits to absorb.
3) In "Node Identity Assigment" (NO) form you write at "Local Node Indentifier" the folowings lines:
343545
800397
88839
This digits are absorbed from the front of numbers. The inconvenient is that they will be absorbed in all DID links not only in that one !
So the 800 397 8888 became 8888 number and 888 397 8888 number became 78888 number.
4) Program sistem speed calls or hunt groups for 8888 and 78888 to route to the numbers you want if you want that the stations remain with normal internal numbers too.
You have to check that the numbers 8888 and 78888 are not conflicting with others numbers or codes or ARS exactly .
In the NO form you can have only 5 Local Nodes Indentifiers with maximum 7 digits each. In your example is enough but I don't know in your real case if this is enough.

XO

Sorry I don't know what means XO .
Did you solve your problem ?

XO communications...

We installed another trunk card...Routed based on 10 digits to the trunk, performed digit modification and looped it back. We tied the trunks together with a crossover cable. Costs some money but saved us a TON over what XO wanted to charge for custom DNIS.

I thinked at this solution too, but I cosidered too expensive because you have to use 2 digital links (crossovered) and the provider has to send to you all 10 digits.
In my solution the telecom provider has to send all 10 digits too but you don't need 2 crossover digital links (I say digital because you probably want to maintain caller ID on that tool free mumbers).