Q: My operator asked me to reprogram her console’s ESS key and PAG to appear on the bottom keys instead of where they were. I found the programming and changed keys 0 and 1 but now it won’t let me add back the BIN and BVR features to keys 8 and 9. Why won’t it take the programming?
A: Features BVR and BIN can only appear on keys 0 and 1, respectively. You can put something else on those keys if you wish, but if you use those features they must appear on their home keys.
Q: Programming rollover keys on my phones has gotten to be a real chore. We have a DID range of 3000 numbers, 2000-4999. We use 5000-6000 for rollovers. Since many of our phones are analog we should have plenty of rollover numbers, but I spend a lot of time printing available DNs to use whenever I program a phone. There must be an easier way to do this.
A: Whoever initially created your numbering plan surely wasn’t responsible for doing the programming. You’re right—that’s a real chore. In other companies where I’ve worked, the rollover numbers are usually directly related to the DID number on key 0. For example, if the DID was x3905, the rollover might be x6905. It made it easy to assign numbers because there was only one choice. The only exception was if a phone required additional rollover numbers. Those required the same process you use, but there were far fewer of the phones with additional rollover lines.
More recently I’ve started using rollover lines that use more digits to conserve dial plan utilization and to simplify number assignment. Let’s say, for example, your DID number is 234-567-8901. You could assign key 0 with your extension 8901 and key 1 with extension 5678901. That assumes there is no extension 5678 in your system. Do you see how much this helps your dial plan? And you don’t have to implement this by reprogramming all your phones at once. You can start using it whenever you like and reprogram phones as you get to them. You still have to do something innovative on additional rollover keys, but can perhaps consider using 678901 and 78901 if those numbers are available in your dial plan, or make them available by reprogramming whatever is using them.
Q: Hi Phil! Do you remember me? I'm the person who asked about NCOS utilization and I would like to ask something else, but refering to CLID table. Can you help me to configure in the PBX a specific DN and CLID number that has to be send out, for example:
DN CLID
12687 05400
12686 05401
12685 12688
In this case a specific DN, has to show another number. Do you know the way I can do this?
A: Let's start with eliminating the easy solutions. Consider the first entry in your list, 12687 to show 05400. Let's also assume you are sending calls out PRI, and your programming determines what CLID goes out. You probably have CLID entry 0 on most or all of extensions.
If the DN on key 0 is 05400 and another key on that phone is 12687, program 12687 like this: KEY 2 SCR 12687 D. The D says to start at key 0 and go up the keys until you reach a CLID entry that is not D.
You probably thought of that, so let's look at the harder way. Each DN should have a CLID entry following the DN on the key. Even an analog extension has a CLID entry after the DN. You can create a special CLID entry for that key, or you can use it on other keys as well.
In LD 21, print the CLID entries (this is from memory, so bear with me).
REQ: prt
TYPE: clid
CUST: 0
RANGE:
This should print all of your CLID entries.
You can program the first available CLID table in LD 15 with the number you want instead of a DID entry.
REQ: chg
TYPE: NET
(press Enter until you get this:
CLID: yes
SIZE:
INTL:
HNTN: (duplicate what is in your existing entries here)
HLCL: (fill in the rest of the phone number, including the 05400)
(Enter through the rest of it)
Use the table entry for the CLID on your extension. Test it!
Reach the author at philruffin@hotmail.com.
© 2008 Telecom Reseller. All Rights Reserved.