Adding DN's to M2250 1

[jdlrez]

I am currently trying to find a way to add additional DN's that are not currently in use (this will be for DID's) to the unused keys on my attendant set.

I tried doing a CHG in LD 12:

REQ CHG
TYPE 2250
TN 12 0
SETN 012 0 00 01
ANUM
SSU
ICDR
CPND
LANG
SGRP
AADN
KEY 13 SCR SCH362
-----

That error gives the usual unhelpful (to me anyway) griping about store mnemonics.

So the question is: Am I doing this incorrectly, or is it not possible on an Attendant set?

Background: The idea behind this would be that we have CFV set up at some other office locations, which they sometimes use to forward their main number to the office here. We would like to have each location's forwarded calls ring to a unique key on the M2250 for clarity purposes.

Thanks in advance.

 

[GHTROUT]

Can't add DNs like that, but you can add up to a total of four LDNs in the Customer Data Block. What I'd do is create Phantoms that DCFW to "0" and name them "Detroit Office" or something so the Attendant will see the name


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[jdlrez]

Re: GHTROUT

Thanks for the reply. I'm going to have to plead ignorance here, as I have never programmed a 2250. A such I don't know anything about LDNs or Phantoms.

Could I get an outline of basic steps?

Thanks.

 

[GHTROUT]

A 2250 is programmed in more than one place, but this will summarize it:

The keys on the far right are done in LD12.

The keys on the far left are based on Trunk Group Number.

The "ICI" Keys to the left of the LDNs are defined in the ATT_DATA section of the LD15 Customer Data Block.

The LDNs (Listed Directory Numbers) are defined in the LDN_DATA section of the LD15 Customer Data Block.

The Night treatment is defined in the NIT_DATA section of the LD15 Customer Data Block.

How does one grasp all of this? Hmmm, not easy. My first thought would be to simply say "you can't add more DN Keys"

I have a little primer on Consoles here: faq798-6217


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[GHTROUT]

What I did at a previous company for situations like remote office weather closings, fire drills, staff shortages, etc. was this: Created a voice menu that said "Due to special circumstances at the office you dialed, your call has been transferred to the Corporate Headquarters of Acme Bird Seed, Inc. If you wish to speak to someone, please stay on the line or press zero. Otherwise, please call back at the start of or next business day"

Then we would Remote Call Forward the office to that menu. We had a lot of Florida hurricane closings so it cam in very handy and kept the volume at Corporate down, as many customers figured out the closing reason and simply decided to call back the next day.

I'll bet that is pretty close to why you are doing this hey It's too cold to work!


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[jdlrez]

Thanks for the info. Think I'll sleep on it.

 

[GHTROUT]

Ooops, I meant "ICI keys are to the left of the Loops Keys, which are left of the dial pad"


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[jdlrez]

That's not a bad idea.

Actually we're doing this because the staff at our satellite locations has been cut to a skeleton crew and there is often nobody available to answer the phone.

And our one office person in each place likes to take a lunch break once in a while