Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IDC to Non-issued DN

Status
Not open for further replies.

janaya

IS-IT--Management
May 7, 2002
2,292
US
Ok get your thinking caps on. :)

We have an entire NPA-NXX range in our PBX. Ext 0000 through 9999, or however you want to look at it. We own all 10000 DID numbers.

The LEC pulses us the last 4 digits. We use 5 digits on our sets. We change this by inserting the lead digit, everyone is the same, in the IDC table. If you want to know why email me and I will explain. This has to do with implementing a corporate wide dialing plan.

Problem. If the DN is unused (ie. 21234) then, I get the following error

ERR0183 1234 X Y <-- X being the loop and Y the member

I want to give a busy signal/announcement, but since we have DNIS turned on, we get that 4 digit error when someone calls and the call is routed to the Attendant.

I have intercept programmed to BSY but it doesn't work.

Any ideas, and the clock is ticking. Not a problem anyone is reporting, but I would like to alleviate some traffic to the attendant.


John
 
The only thing I can think of is to have the IDC tables route any DID number which you don't use to a voicemail box via a acd with NCFW to the MMail instead of not having it in the IDC table.
 
ERR0183 dnis tn DNIS calls cannot terminate because the IDC Translation is invalid, or the
terminating station is not an ACD-DN.

correct me if I'm wrong

in LD 16 you have
DNIS YES
and you use the vacant number routing option
am i right or not?
 
We have DNIS turned on, on the route (YES) and I am trying the INT treatment CTVN (Call to Vacant Number). Yes.

I think that since we are recognizing the DNIS on the route, which would be the 4 digits, then the PBX does not know what to do if the numbers are not defined in the IDC table. Only problem, is that they went through a RIF and there are hundreds of unused DN's and we are using applications that read the DNIS that are programmed to read 4 digits.

I think if we were able to change what we get from the LEC to 5 digits we would be fine, since the DNIS' coming into the PBX would not require any manipulation in the IDC tables.

If anyone can shed any further light that would be great.
 
What do you mean. My LDN is 23700.


TYPE LDN_DATA
CUST 00
OPT XLDN
DLDN NO
LDN0 23700
LDN1
LDN2
LDN3
LDN4
LDN5
ICI 00 R000
ICI 01 R001
ICI 02 R002
ICI 03 RLL
ICI 04 INT
ICI 05 DL0
ICI 06
ICI 07 IAT
ICI 08 LD0
ICI 09 LD1
 
If I understand what you are saying you get 4 digits from the pstn, for example 2222. You are then adding a digit infront of that with IDC tables.
If you for example would like to add 4 infron it will be 42222.

Why cant you delete the IDC table and insert the digit on the route?

In that case you will not use the IDC tables and I guess the PBX would treat the incomming number as any other vacant/unused numbers..
 
If you mean insert the digit in the route with INST prompt ,it is not available if the DNIS is YES.
 
and at the finish line.......

It's a disqualificaton...

This is a known problem with the M1 line software. Currently there is no known fix and no one working the fix.

Information released as a Product Bulliten..

Those with access to the Nortel Knowledge Base can find this, I did.....thanks for all those participating.

John
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top