| |||||||||
 |
| ||||||||
| |||||||||||||||
| |||||||||||||||
| BCM and Norstar ICS, CICS, MICS, BCM, BCM 50 BCM 200 and BCM 400, Startalk Voicemail call pilot 150 |
| Tags: desktop, going, msging, mwi, nam, using |
 |
| | LinkBack | Thread Tools | Display Modes |
| |||||||||
|
| ||||||||
| |||||||||||||||
| |||||||||||||||
| BCM and Norstar ICS, CICS, MICS, BCM, BCM 50 BCM 200 and BCM 400, Startalk Voicemail call pilot 150 |
| Tags: desktop, going, msging, mwi, nam, using |
|
| | LinkBack | Thread Tools | Display Modes |
 04-26-2005, 02:07 PM | #1 (permalink) | ||||||||
| Junior Member 
Location: Tampa Rep Power: 6  Gender:  Country:     | I've got a NAM 4.1 centralized between 2 MICS 6.1's with PRI tie lines. New msg's come into the sets and light up the MWI. You get your msg's via Desktop Messaging and read/delete them and the MWI on the phone does NOT extinguish. Nortel said corrupt data, so I got a brand new NAM 4.1, set it up in a perfect environment and it does the same thing. Anybody ever seen this? P.S. - long time no see guys.!! Thanks Gabe | ||||||||
 |   |
| 04-27-2005, 10:40 AM | #2 (permalink) | ||||||||
| Junior Member
Rep Power: 0 Country: | whats up dog! welcome back to the forum, your spending too much time outside. unfortunately i can't help you w/your problem, as you know i don't know about desktop msging. but, does F#65 remove the light? it may just be a temporary fix and it may have to be done on a regular basis. i take it, you want the light to go away after the msg has been read? we could do w/out the mugshot...hahaha | ||||||||
| | |
| 04-27-2005, 12:05 PM | #3 (permalink) | ||||||||
| Junior Member
Location: Tampa Rep Power: 6 Gender: Country: | Logging in F981 or using F#65 makes the light go out like it should. But this customer only uses Desktop Messaging. We have two MICS 6.1's tie'd together with a NAM 4.1 in between. Normally Desktop Messaging puts the light out the second you read the message, but 4.1 isn't doing it. It's in 2nd level ETAS right now, they are duplicating it in their lab and then will most likely create a patch for it. Unfortunately the customer is impatient and is not willing to use work arounds since it worked prior to me upgrading them to 4.1. | ||||||||
| | |
| 04-29-2005, 05:17 PM | #4 (permalink) | ||||||||
| Junior Member
Location: Tampa Rep Power: 6 Gender: Country: | A Nortel engineer got back with me today and emailed me a patch for the nam 4.1 to correct the MWI problem. If anyone needs this patch for a similar problem let me know and I will email it along with instructions on applying it. Works like a champ!! | ||||||||
| | |
|
| 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 |
| CP 2.02 Desktop Client for Outlook and other callpilot bugs | sneexy69 | Meridian Systems | 1 | 10-27-2003 08:59 PM |
| desktop messaging revisited | martyatherton | BCM and Norstar | 7 | 05-05-2003 07:46 PM |
| Norstar NAM4 desktop messaging issue | martyatherton | Meridian Systems | 2 | 01-17-2003 11:39 AM |
| Desktop Messaging ? | AK88 | BCM and Norstar | 2 | 11-25-2002 06:34 PM |
Linear Mode
