Octel 250 / Nortel PBX - MWI's not turning off

[nessman]

Getting an increasing number of complaints about MWI's not extinguishing when folks are checking their voice mail. Running an Octel 250/Aria 3.11.05-1 with FLT cards on a Nortel Option 61c PBX running Succession 3.0

Enhanced traces of the MWI ports on the PBX show MIK/MCK activity when voice mail arrives or is checked.

Anyplace I need to start looking? Port tests come up clean in the Octel system. Not seeing any problems/error on the PBX.

Thanks.

19 OCT 87 08:26:28AM Spacely Sprockets
VPMOD Serial # ........ 17702 Software Rel. .... Aria 03.11.05-1
Network Serial # ...... 17702 System Type ........... 250
Card 1 F Prom: 98.12 Disk: GE.03 Card 2 L FLT: NA. T1/E1: NA.
Card 3 L FLT: NA. T1/E1: NA. Card 4 L FLT: NA. T1/E1: NA.
Card 5 L FLT: NA. T1/E1: NA. Card 6 L FLT: NA. T1/E1: NA.
Card 8 N Prom: 98.12
Line Card Digitization Rate: B Telephone System Type: 1 - North American
Boot Prom ........ 98.12 IPL Extension .... 20.33 FLT/DLC .......... NA.
Menus ............ 31.61 Termcap .......... 20.12 FLT/DSP .......... NA.
CVT_ROM .......... 98.02 CVT .............. 02.21
VTIC_ROM ......... 02.06 VTIC ............. N01.19
LAN Card/OS ...... 20.F3 LAN Card/APP ..... 01.01
Operating System .......... 99.31.12 System Services ........... 99.31.10
Trees ..................... 99.31.06 System Manager ............ 99.31.11
Purge Task ................ 99.31.04 Line Tasks ................ 99.31.12
Integration Tasks ......... 99.31.02 X25 Operation ............. 99.31.02
ACL Task .................. 99.31.04 ASA Task .................. 99.31.07
ASA SUD Task .............. 99.31.06 IMSO Task ................. 99.31.05
OET Task .................. 99.31.04 Background Task ........... 99.31.02
System Bkup/Rstr .......... 99.31.02 LAN Card Router Task ...... 99.31.02
DN Mail Tasks ............. 99.31.02

VERSION 3321
RELEASE 3
ISSUE 00 + Incomplete DepList x210300_cpp

IDLE_SET_DISPLAY NORTEL

IN-SERVICE PATCHES : 33
PAT# PRS/CR PATCH REF # NAME DATE FILENAME
00 Q00934989 ISS1:1OF1 p20144_1 24/06/05 p20144_1.cpp
01 Q01004707 ISS1:1OF1 p19030_1 24/06/05 p19030_1.cpp
02 Q00982051 ISS1:1OF1 p19414_1 24/06/05 p19414_1.cpp
03 Q00987144 ISS1:1OF1 p19864_1 24/06/05 p19864_1.cpp
04 Q01053376 ISS1:1OF1 p19973_1 24/06/05 p19973_1.cpp
05 Q00850201 ISS1:1OF1 p18470_1 24/06/05 p18470_1.cpp
06 Q00743283_ ISS1 1OF1 CORE 24/06/05 p17889_1.cpp
07 DEPLISTPAK ISS3:1OF4 CORE 24/06/05 p18000a3.cpp
08 DEPLISTPAK ISS3:2OF4 CORE 24/06/05 p18000b3.cpp
09 DEPLISTPAK ISS3:3OF4 CORE 24/06/05 p18000c3.cpp
10 DEPLISTPAK ISS3:4OF4 CORE 24/06/05 p18000d3.cpp
11 DEPLISTPAK ISS3:1OF2 TERMINALS 24/06/05 p18004a3.cpp
12 DEPLISTPAK ISS3:2OF2 TERMINALS 24/06/05 p18004b3.cpp
13 DEPLISTPAK ISS3:1OF3 IP 24/06/05 p18005a3.cpp
14 DEPLISTPAK ISS3:2OF3 IP 24/06/05 p18005b3.cpp
15 DEPLISTPAK ISS3:3OF3 IP 24/06/05 p18005c3.cpp
16 DEPLISTPAK ISS3:1OF5 INTL 24/06/05 p18006a3.cpp
17 DEPLISTPAK ISS3:2OF5 INTL 24/06/05 p18006b3.cpp
18 DEPLISTPAK ISS3:3OF5 INTL 24/06/05 p18006c3.cpp
19 DEPLISTPAK ISS3:4OF5 INTL 24/06/05 p18006d3.cpp
20 DEPLISTPAK ISS3:5OF5 INTL 24/06/05 p18006e3.cpp
21 DEPLISTPAK ISS3:1OF3 EURO 24/06/05 p18007a3.cpp
22 DEPLISTPAK ISS3:2OF3 EURO 24/06/05 p18007b3.cpp
23 DEPLISTPAK ISS3:3OF3 EURO 24/06/05 p18007c3.cpp
24 DEPLISTPAK ISS3:1OF5 FEATURES 24/06/05 p18008a3.cpp
25 DEPLISTPAK ISS3:2OF5 FEATURES 24/06/05 p18008b3.cpp
26 DEPLISTPAK ISS3:3OF5 FEATURES 24/06/05 p18008c3.cpp
27 DEPLISTPAK ISS3:4OF5 FEATURES 24/06/05 p18008d3.cpp
28 DEPLISTPAK ISS3:5OF5 FEATURES 24/06/05 p18008e3.cpp
29 Q00769624 ISS2:1OF1 CORE 24/06/05 p18050_2.cpp
30 Q00744653 iss1:1of1 CORE 24/06/05 p18380_1.cpp
31 Q00815822 ISS1:1OF1 p18774_1 24/06/05 p18774_1.cpp
35 Q01029538 ISS1:1OF1 p19555_1 14/07/05 P19555_1.CPP
LOADWARE VERSION: PSWV 88++
INSTALLED PATCHES : 3
PAT# PRS/CR PATCH REF # NAME DATE FILENAME
00 Q00912139- ISS1:1OF1 Taurus set 20/09/04 p18840_1.lw
01 Q00912139- ISS1:1OF1 Taurus set 20/09/04 p18810_1.lw
02 Q00912139- ISS1:1OF1 TAURUS SET 20/09/04 p18717_1.lw

Phone sets are mostly M3904's running various firmware (likely 8.9).

 

[nessman]

Some more info. Was able to pull CDR out of the Octel system - and I can see where they're checking messages, but there's no MWI activity. Where should I be looking?

Test calls I'm making I can see MWI on/off. So this is a random / intermittent issue.

Thanks.

 

[KenMeans]

So when you make a test call you see the MWI event 18 in the CDR but not on others ? How many MWI ports do you have ? You say random so it works sometimes for the same user that it fails on ?



Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[nessman]

I'm not seeing an event 18 (where should I look?). But here's output from the CDR showing message waiting set and clear.

We have 4 MWI ports, about 1000 mailboxes, and this happens randomly across the board.

***** 13 OCT 87 11:05:17AM
SMSSESSION MODE SET)
Port: 3G Mode: 1 Box: 5554880
AppID: 0

***** 13 OCT 87 11:06:10AM
MSMESSAGE SENT)
Port: 3G Type: 0 Attr: 0 Snd/Rcv: 1
DstBox: 5554880 SrcBox: 3495213 DstAppID: 0 SrcAppID: 0
Time: 13 OCT 87 11:06:00AM
MsgID1: 80213d28 MsgID2: 00000000
Len1: 43 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

***** 13 OCT 87 11:06:12AM
MWMESSAGE WAITING SET/CLEAR)
Port: 2H Box: 5554880 Ext: 01424880 Dir: 1 Stat: 0

|
***** 13 OCT 87 11:11:59AM
PWTPASSWORD TEST)
Port: 1E Box: 5554880 Result: 0 AppID: 0 PWType: 0

***** 13 OCT 87 11:11:59AM
SMSSESSION MODE SET)
Port: 1E Mode: 2 Box: 5554880
AppID: 0

***** 13 OCT 87 11:11:59AM
MSGCNTMESSAGE COUNT)
Port: 1E When: Entry Box: 5554880
Unheard Voice: 1 Heard Voice: 0 Archived Voice: 1
Unheard Fax: 0 Heard Fax: 0 Archived Fax: 0

***** 13 OCT 87 11:12:01AM
MWMESSAGE WAITING SET/CLEAR)
Port: 3H Box: 5554880 Ext: 01424880 Dir: 0 Stat: 0

***** 13 OCT 87 11:12:53AM
MDMESSAGE DELETED)
Port: 1E Why: 0 Type: 0 Stage: 0
Snd/Rcv: 1 Box: 5554880 AppID: 0 Time: 13 OCT 87 11:06:00AM
MsgID1: 80213d28 Len1: 43 Len2: 0
FaxID: 0 FaxPage: 0

 

[KenMeans]

the MW is the event 18 i was asking about. The best thing to do is to match a complaint with the CDR and see if the MW event shows or not. You may want to look to see if you have retry set on MWI but I don't remember if it works on this setup offhand.
Nortel is known for ignoring MWI if it is busy doing something else.

You might try moving the MWI ports to a low traffic loop / shelf


***** 13 OCT 87 11:12:01AM
MWMESSAGE WAITING SET/CLEAR)
Port: 3H Box: 5554880 Ext: 01424880 Dir: 0 Stat: 0

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[nessman]

I am doing just that - matching complaints to CDR's. When I do that, I'm seeing instances where I'm not seeing a "'message waiting clear'; 'Dir: 0'" come out of the CDR log when they check their messages. So it's not even telling the PBX to invoke an MCK from emulated 2616 set on the FLT card.

 

[KenMeans]

It will lot beanie rondo that if the port from the mortal is not available I would change the ports of the Mwi ports and see if that makes a difference

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)