| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: lights, message, waiting |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 6 ![]() | No voicemail 11c r25 Our company has this annoying little setup for our sales staff. Each person gets a digital set + a 500 set for a cordless headset, each with the same extension. The digital set is the marp set in each case. This works fine throughout the company (about 30 people have this set up) except for a group of 4 - 3904 sets. when a message is left in any of the 4 mailboxes, the message waiting light will not come on. The only way I have been able to successfully resolve the problem is to 'out' or change the DN assignment on the corresponding 500 set- once I do this, the message waiting light works as it should. (like I said, I have verified the 3904 is the marp set). Of course, it almost defeats the purpose to give them 2 different extensions, they want to be able to answer calls to their personal extensions on their cordless headsets. any suggestions? | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Junior Member
Rep Power: 6 ![]() | message waiting lights the DN is not on key 0 (as you will see), but if the corresponding 500 set does not exist, the light works fine....?? here are the TNBs.. By the way, the 3904 is acquired by SECC. TN 025 0 00 13 TYPE 3904 CDEN 8D CUST 0 FDN 2770 TGAR 1 LDN NO NCOS 2 SGRP 0 RNPG 21 SCI 0 SSU LNRS 16 XLST 0 SCPW CLS CTD FBD WTA LPR PUA MTA FNA HTA ADD HFA GRLD CRPD STSD MWA RMMD SMWD AAD IMD XHD IRA NID OLA VCE DRG1 POD DSX VMD CMSD CCSD SWD LNA CNDA CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD LLCN MCTD CLBD AUTU GPUD DPUA DNDA CFXA ARHD FITD CNTD CLTD ASCD CPFA CPTA ABDD CFHD FICD NAID BUZZ AHD DDGA NAMA DRDD EXR0 USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN CPND_LANG ENG RCO 0 HUNT 2770 LHK 5 LPK 6 PLEV 02 SPID 1454 AST IAPG 0 AACS YES ACQ AS: TN ASID 16 SFNB 2 5 6 9 10 11 12 13 15 16 17 18 19 SFRB 1 2 15 USFB 1 3 4 5 6 7 9 10 12 13 14 15 CALB 1 3 4 5 6 8 9 10 11 12 FCTB 1 ITNA NO DGRP PRI 01 MLWU_LANG 0 DNDR 0 KEY 00 ACD 2526 0 1948 AGN 01 MSB 02 NRD 03 SCR 2948 0 MARP CPND NAME Homer Simpson XPLN 24 DISPLAY_FMT FIRST,LAST 04 SCR 4948 0 MARP CPND NAME Homer Simpson XPLN 24 DISPLAY_FMT FIRST,LAST 05 06 07 08 09 10 11 12 13 14 15 16 MWK 2770 17 TRN 18 AO6 19 CFW 16 2770 20 RGA 21 PRK 22 RNP 23 24 PRS 25 CHG 26 CPN 27 28 29 30 31 and, the 500 - DES R TN 027 0 00 07 TYPE 500 CDEN 4D CUST 0 WRLS NO DN 2948 0 CPND NAME Homer Simpson XPLN 24 DISPLAY_FMT FIRST,LAST AST NO IAPG 0 HUNT TGAR 1 LDN NO NCOS 2 SGRP 0 RNPG 21 XLST 0 SCI 0 SCPW CLS CTD DTN FBD XFD WTA THFD FND HTD ONS LPR XRD CWD SWD PUA MWD RMMD SMWD LPD XHD CCSD LND TVD CFTD SFD MRD C6D CNID CLBD AUTU ICDD CDMD LLCN EHTD MCTD GPUD DPUD CFXD ARHD OVDD AGTD CLTD LDTD ASCD MBXD CPFA CPTA DDGA NAMA MCRD EXR0 SHL ABDD CFHD DNDY DNO3 CWND USMD USRD BNRD OCBD RTDD RBDD RBHD FAXD CNUD CNAD PGND FTTC PLEV 02 AACS NO MLWU_LANG 0 DATE 28 APR 2003 Thanks for the help! | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Junior Member
Location: WNY Rep Power: 6 ![]() | SIMPLE FIX???? Simmy, According to the NTP's (and I'm assuming you've read those. . cause the 3904's are a bit different) you can only put MSB and NRD on keys 8-11. You need to put the primary DN on key 0. Everything I read recommends that. Try that and let us know what happens. Try to read up on these a bit as the 3904's have a few quirky features. AB | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Junior Member
Rep Power: 6 ![]() | message waiting lights simmy, Read my first post. The TN's show exactly what I had said, you have an ACD set so the DN that you are trying to light the light for is not key 0. Message waiting will light the light for key 0 or any other single appearance key on your set. If your key 4 DN 4948 is a single appearance, make it the notification DN in mail. That will resolve your problem also. | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member
Rep Power: 6 ![]() | OTM Thank you all for your replies- AB- tried changing MSB and NRD to keys 8 and 9, didnt help.. I have read the NTPs.. MSB and NRD do work on keys 1 and 2 regardless of what they say- although I am open to the idea that putting those buttons there may cause weird problems.. but it doesnt look like the case this time. PP- thanks for pointing that out... made a couple of changes recently, there were appearances on 5 and 6 and forgot to change the LHK and LPK settings... but, not the cause of my problem. Tech_anon- I had read your first post before.. I guess I didnt understand that what you meant was that BECAUSE the extension appears on 2 sets, the appearance on the 3904 must be on key 0 (I think that is what you are saying?). I thought you meant that no matter what, the appearance had to be on key 0 (that is why I responded in my last post that the light works fine if the analog set does not exist). And, my VM system does not allow me to do that, its not meridian mail.. This is fairly inconsiquential to my problem, but I feel maybe I need to explain why the phone is set up the way it is. I have a 60+ position call center which has 2616 and 3904 sets throughout. The agents that work in this call center tend to move around and log into different sets all of the time- so, I attempt to build all of the sets in the call center to 'look' as similar as possible so when moving from one phone to another, the agent doesnt lose his/her mind (both 2616 and 3904s have keys 0 - 2 ACD buttons, on 2616 keys 8 and 9 are personal DNs on 3904s, 3 and 4 are personal DNs-- makes the buttons at least resemble each other). Unfortunately, putting MSB and NRD buttons on keys 8 and 9 means that I need to show agents how to use the 'shift' button-- I dont know about anyone else on this board, but it has been my experience that most people CAN NOT use the shift button properly and never really unerstand it no matter how many times I train them, so I avoid it whenever possible. So, sorry for the long post... There is a reason for my button configuration- and since the light works just fine when there is no analog set w/ the same extension, I figured I might be able to keep it. once the current agent logs out, I will change the ext. assignment to key 0 to see if that works | ||||||||
| | |
| | #10 (permalink) | ||||||||
| Junior Member
Rep Power: 6 ![]() | message waiting lights Once again, message waiting will light for key 0 or any other single appearance on the set. This is the reason it will not light the MW light, it is not a single appearance or key 0. If you cannot make key 4 the notification DN, read up on extended message waiting keys. | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| message waiting light? | Shanks | Meridian Systems | 10 | 03-02-2006 12:20 PM |
| Problem with message waiting lights on remote Avaya pbx. | eoolose | Definity Support | 4 | 01-26-2005 08:16 PM |
| Message waiting Indicator lights on G3Si | EA6BMECH | Definity Support | 4 | 11-17-2004 11:46 AM |
| Message Waiting lights on a LU PBX | paiscool | Definity Support | 1 | 04-28-2004 09:55 PM |
| Message Waiting Lights | PD | Meridian Systems | 8 | 04-08-2003 10:47 AM |