Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

M3903 Key Labeling 2

Status
Not open for further replies.

FuzzyCub

MIS
May 12, 2004
88
US
Hello,

Is there a way to change the label of a key through the computer? My rollover DN shows the actual extenxion but I would rather it say "Line 2". Employees have been giving out the rollover DN which is not accessible from the outside.

Thanks!!
 
I have been starting to program sets with
key 0 MCR 1111
key 1 MCR 1111

instead of the "traditional" way of
key 0 SCR 1111
key 1 SCR 2222

I haven't been able to come up with a downside, but I am afraid I am going to experience some unintended consequences down the road. Can anyone come up with a good reason not to use MCR keys? I always hated the idea of giving up perfectly good numbers. In the past, I would always make the rollover a 7 digit number, but MCR seems to be a better option as far as I can tell.

Any thoughts?
Rob
 
Interesting teekow! The only downside I can think of is the initial call will ring on both buttons at the same time. I guess that doesn't bother your users?

War Eagle!
Lions Baseball '09!
 
no, nobody cares/notices (call flashes on both keys for first incoming call).....IRA still works as well as hunting so I can't find any issues so far (plus you don't have to add alternate extensions to CP mailboxes), but the fact that almost everyone does NOT do it this way makes me think that there must be some reason that I shouldn't either
 
Cool solution Teekow! I can't see any problems with that programming other than the two keys will flash at the same time when a call arrives. Most of our employees just grab the handset without even noticing the DN keys. Thanks for your input!
 
I did find one downside for the MCR arrangement that I described above. Only one call can be ringing at any given time. A second call that comes in at the same time as the first one is still ringing will get HUNT treatment (usually voicemail) since all of the keys are busy and ringing at the same time on your phone. This only was really an issue at the recept station but wanted to let everyone know in case you are thinking of this.

Hope this helps
Rob
 
Finally, someone else noticed that :)

Can you imagine all the MCRs out there where nobody thunk of that...

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
Even though the MCR gives busy when ringing, I still often recommend it instead of Group Hunt nowadays.
Simply because Hunt Groups in TM is left on the server in List Manager and cannot be administered through the WEB interface.
 
I got two complaints for MCR.

1. My boss has an IP set and a soft phone. Usually, he uses the handset of the IP set to receive calls. But if the call is too long, he will "transfer" to his headset of his soft phone. Such "transfer" can only be done by SCR.

2. My co-work's phone is very busy. Sometimes, he doesn't want to pick up an incoming call, but wants to make an outgoing call. With MCR, he has to wait the call CFNA to voice mail. With SCR, he can use his phantom line to call out in this case.
 
@nanningmiss:

Solutions for your issues:

1. A) Use a park key to park the call while changing sets (this is not a transfer or a "transfer"). B) Transfer the call to the same extension and it will ring on the MCR keys.

2. Provide a 3rd DN key which is unpublished.
 
Thanks MagnaRGP.

1. I thought of transfer but didn't try it, since it was not a big deal for my boss.

2. Then we still need an extra extension number.
 
I like the 7 digit rollovers like TNPhoneman. It allows for 10 rollups for each DN and conserves dialing plan. I was using 6 digits, and Fletch showed me how to use the last digit.

First two digits are rollover identifier. (18 in example)
Next four digits is the DN identifier. (2250 in example)
Last Digit is a count of 0-9.

key 10 scr 1822500 d
key 9 scr 1822509 d
key 9 scr 1822508 d
.
.
key 2 scr 1822502 d
Key 1 scr 1822501 d
Key 0 scr 2250 0
 
To me, the unique part of tnphonemans 7-digit numbers was, they were mirrors of the users actual telco phone number.

So, if my telco NXX was 555 and my DN was 2752, my keys could be this:

KEY 1 SCR 5552752
KEY 0 SCR 2752


~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
That's how I was originally doing it. Now say your user wants two rollovers for some reason. What would be the 3rd?

If you make the first two and identifier, then you can use the last digit as a counter. Now the user can have 10 rollovers for that DN.
 
Yes, there are limitations to everything. Your idea has rhyme and reason, so it's pretty cool too.

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top