Internal Number Translation

[FonePhreak]

Equipment:
Option 11c. VERSION 2121 RELEASE 4
PRI's for connection to outside using DIDs.
Internal 4 digit dialing.

Here is the problem.
Our internal company phone booklet has users listed twice,
once by their last name (alphabetically) and then again under their department.
Mr. Smith's DN is listed correctly by last name (1234)
Mr. Smith's DN is NOT listed correctly under the department listing (1324)
1234 is a valid DID on our system.
1324 is NOT a valid DID on our system.

What we want to do is redirect internal users that call Mr. Smith's wrong DN to his correnct DN.
(We realize that if an outside caller dials the wrong number, they won't get here from there no
matter what. We don't care.) This is an internal phone directory and we are interested in just
getting internal callers to the right DN.

Is there a way to redirect or translate Mr. Smith's incorrectly listed DN (1324 - NOT in our DID
range) to his correct DN (1234 a valid DID) when internal users dial the wrong 4 digit number.

Thanks for reading this.

 

[EddieDuece]

You can do that in LD 49, IDC table.

 

[EddieDuece]

>ld 49
DGT000
MEM AVAIL: (U/P): 23417906 USED U P: 4840374 299028 TOT: 28557308
DISK SPACE NEEDED: 498 KBYTES
2MB BACKUP DISKETTE(S) NEEDED: 1 (PROJECTED LD43 - BKO)
REQ chg
TYPE idc
CUST 0
DCNO 1
IDGT 1324

1324 1234

IDGT-return
Return
done!

 

[StanleySteamer]

IDC table will only apply to external callers.

For internal callers you could use CDP.

Best thing would be to reprint the internal directory.

 

[EddieDuece]

Oooops. O.K. then, how about this.

>ld 23
ACD000
MEM AVAIL: (U/P): 23417906 USED U P: 4840374 299028 TOT: 28557308
DISK SPACE NEEDED: 498 KBYTES
2MB BACKUP DISKETTE(S) NEEDED: 1 (PROJECTED LD43 - BKO)
ACD DNS AVAIL: 23828 USED: 172 TOT: 24000
REQ new
TYPE acd
CUST 0
ACDN 1324
MWC
DSAC
MAXP 1
SDNB
BSCW
ISAP
RGAI
ACAA
FRRT
SRRT
NRRT
FROA
NCFW 1234
FNCF
FORC
RTQT
SPCP
OBTN
RAO
CWTH
NCWL
BYTH
OVTH
TOFT
HPQ
OCN
OVDN
IFDN
OVBU
EMRT
MURT
RTPC
STIO
TSFT
HOML
RDNA
DAL
RPRT
RAGT
DURT
RSND
FCTH
CRQS
IVR
OBSC
OBPT

This will accomplish what you need.

 

[jrmeridian]

I agree with Eddie..ACD is the way to go...

 

[Johnthephoneguy]

If you do both suggestions, the IDC and the ACD then you will take care of both external and internal calls.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[FonePhreak]

EddieDuece:
We implimented the acd solution. (Thanks for the example.) It works but the only minor drawback is the 3 rings before it rolls to the correct number. Ideally, it would just ring the correct number (1234) without going to the acd (1324) first, but I guess when you fat finger the phone directory, you have to live (temporarily) with your mistakes and the solutions needed to correct them. Oh well, a new directory will be out in 6 months.


Thanks everyone for taking your time to help.
I really appreciate it.

Carl.

 

[EddieDuece]

FonePhreak,
I tested this out on my system and it works without delay, Like you want it to? Not sure what is going on with your switch, but there should not be a delay?

 

[acewarlock]

EddieDuece is right, there shouldn't be any delay. But if it was me I would have just added the wrong ext to his phone.

 

[EddieDuece]

That's a good point Ace. I often overlook the easy logical solution. Add 1324 to key 1, allow hunting in the CLS and change the LHK (last hunt key) to Key 1. That givesthe end user a litle flexibility when answering calls as well.

 

[johnpoole]

a maxp 1 almost has to ring at almost the same time as ringback.. using the ncfw is instant, that group is always in nights, no agents are logged on, just take all the defaults except acdn maxp 1 and ncfw

john poole
bellsouth business
columbia,sc

 

[jrmeridian]

If ACD is not working try a phantom TN.

 

[acewarlock]

Like I said, why is everyone trying to make this harder then it needs to be.