How do I make 'busy' unused DN's?

[algonzalez]

Is there a way to make busy unused DN's. Calls to ex-employees(over 100) are somehow re-routed to our operator extension 0.
I have option 81 release 25. Thanks in advance.

Al

 

[janaya]

You can do two things to rectify this. First one is quick.

If you are using incoming PRI lines for DID, then just go into the route and say you want DNIS. In the Route you will see the DNIS prompt and change this to yes.

Two things will happen. The LEC will get a error from the PBX stating the number is not valid and it will return a message to the caller "The number you have dialed has been disconnected." Quick and easy.

Second, you will lose Caller ID information on any M2317 phones you are using.

Does not affect anything, unless you have some ivr type systems that are looking for DNIS. Most people do not turn this on. We have done so, and have seen no adverse affects.

The other thing you could do is:

1. Create a new RAN and assign all appropriate ACODS, and Universal Trunk members.

2. Go into LD 15 to your INT section
3. At the CTVN prompt change to OVF OVF OVF RAN
4. At the next prompt "RANR" you will enter the new RAN number.

If you recorded something like &quot;You have reached a non-working number at <insert your company name here>, that is what callers will hear.

 

[janaya]

Hope all that works....

John

 

[algonzalez]

Thanks for your response. I'm going to need a bit more help. I know the minimum to make it by.

On your first suggestion: I have 18 individual DID trunks cross connected to 18 individual TN's. I printed the TN's in LD11 but did not find anything regarding Route and DNIS.

On your second suggestion: First, the PRT command results in error SCH0099 - I want to see what I have before I make any changes. I think PRT in not a valid command in LD15; I'm looking at the input/output guide and I only see CHG as a valid command. What is RAN in the CTVN prompt? Again, I know very little. I had to look up what CTVN stands for - now I know (Call To Vacant Number).

You mentioned 'recording', I would have to create a number in the voice mail with that message, correct? Thanks again.

Al

 

[janaya]

PRINT ONE OF YOUR TN'S

LOOK FOR &quot;RTMB&quot;

You might have something that looks like:

RTMB 2 1

This is telling you Route 2 Memeber 1.

Go to LD 21

LD 21

REQ: PRT
TYPE: RDB
ROUT: 2 (or whatever your's is)

Look for DNIS. It might be set for no
You can change this to yes in ld 16

LD 16

REQ: CHG
TYPE: RDB
ROUT: 16

ENTER DOWN TO DNIS AND CHANGE.

This should work.....does on PRI. I'm not sure
now that you are saying analog trunks, but it
should work.

John

 

[learnhard]

Program a TN with extension (example 58888). Disable that extension on the TN block (to be extra safe, do a loopback on that TN, just in case you enable the whole card and forget to put back to disable mode).

In the IDC table (point to the IDC table for that DID group)
set those DNs you want to make busy by pointing it to 58888.

Hope it help.

 

[roupe]

You are correct to be looking at CTVN in the cust data block. Go into LD 15 at REQ enter Chg.. at TYPE enter INT at CTVN enter OVF OVF OVF OVF (These 4 columns represent station, attendant,Tie, and DID type calls) remembered as &quot;Score a touchdown!&quot; SATD....The change to OVF of the 4th column entry is supposed to give the caller Bsy instead of the Attendant, but what I have found on all the systems I have implemented is the CO actually (with PRI trks) does not even present the call to your system for overflow, but instead plays a central office recording &quot;You have reached a number that is not in service&quot; Cool!! Good Luck