Naming Pilots Numbers (PLDN) 1

[maver0310]

I need to name pilot numbers so that when the call is presented to an extension is displays the name associated with the number.
For Example:

PLDN 2000 = Sales
PLDN 2001 = Accounts

etc....

I have tried to do this in LD 95 but it gived me an error at the DN prompt.

Help?!

 

[one234]

Hi,

What's the error??? Should work


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[maver0310]

This is from memory but I think that the sch code is 2119.
When you look it up it gives invalid response to DN.

 

[ArchibaldJCox]

Did you out the name in LD 95 before entering a new one?


Arch

 

[maver0310]

Tried "NEW" as it is a new PLDN. Not done chg or out.

 

[maver0310]

Just tried to out the name and at the DN prompt it gives the same sch code (2119).
Could there be something missing from the CDB that is stopping this from working?

 

[wdhb]

You can't name PLDN's or DISA extns

 

[maver0310]

Okay, I might be in trouble then. If you can't name a PLDN then is there a way I can go about configuring an incoming ddi to display a name when it is routed to a group of extensions?
Perhaps route it to a ghost DN, name the ghost DN and permanently call forward that to a group?

Matt.

 

[wdhb]

In the route data, LD16, you need IDC & DNAM = YES.
In LD49, IDC table needs all ddi numbers entered.
In LD95 under DCNO, (IDC table x = DCNO x) you can name the ddi number

 

[maver0310]

Thanks wdhb, I will give it a try today and post my results.

Matt.

 

[bluerigsby]

Hi,
wdhb's suggestion should work fine. An alternative would be to delete the PLDN & provide a phantom DN which can be configured to route to whatever you like. Name the phantom in LD 95 using DN. This is a good option if you want to be flexible with the routing such as in DisRec situations. (remote call forward DN to an alternate number)

 

[maver0310]

I have not tried wdhb's suggestion yet but will post as soon as I have. I have however already created a phantom ext (3851) and forwarded it to a pilot dn (4000) which uses list number 20 but when the call arrives at one of the extensions in the list it displays ACOD-TRK 3851 "F" not the phantoms name.
I do have CNDA in the cls on these extensions.
Any suggestion?

 

[maver0310]

Thanks wdhb worked a treat, just had to set DEXT to yes before DNAM came up as an option to change in the rdb.