OCTEL Delivers Late

[clock67]

Our OCTEL 250 software 3.11.05-1 is delivering messages late at random. This is not an everyday thing. It also does not seem to be patterned to specific vmail boxes. Any thoughts from the group would be great!

 

[KenMeans]

What is prompting the user to think the messages are late? Is it the MWI light?

I have worked on the Octel for more than 20 years and in that time have never seen a delayed message. It has always been the light or a user error in all cases.

Have you looked at the CDR for the mailboxes that are reporting this? What PBX and integration are you using?

Are all of your drives running in menu 12?

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)

 

[clock67]

Ken - Apparently this has been reported a few times over the past few years, but the latest incident occurred to one of our techs. He indicated to me that he had check voicemail both Monday and Tuesday. On Wednesday, he had 16 new messages, over half from Monday and Tuesday. Our OCTEL is connected to a NORTEL MICS. Message indication is by stutter tone. Yes, both drives are running. 74% free message space. I have not looked at CDR info yet, but will look at this today. I agree, this seems bizarre. Any thoughts?

 

[KenMeans]

When you look at the CDR for this mailbox for Monday and Tuesday can you post it? The one thing to look for is the entry and exit to see how many messages are in the mailbox. Also it will show when they arrived.

In all my years of working with the Octel the CDR never lies.

But you never know.

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)

 

[JcBWF]

Ken, agreed that CDR never lies, bu I have had delayed msgs. Usauly the ony fix was to delete the mbx and then add is as new again. Had one customer where we called in AVAYA and that was the answer from an engineer that I really trusted.


Perfection is expected, Excellence is Tolerated

 

[clock67]

I have looked at CDR info. It tells a different story than that of the user. Below is the CDR info, I am sorry it is soooo long. I ended with the access that was recorded. Thoughts?


***** 25 FEB 08 10:40:35AM
SMSSESSION MODE SET)
Port: 1B Mode: 1 Box: 8249
AppID: 0

|
***** 25 FEB 08 10:41:06AM
MSMESSAGE SENT)
Port: 1B Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 25 FEB 08 10:41:00AM
MsgID1: 80009f3e MsgID2: 00000000
Len1: 17 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

***** 25 FEB 08 10:41:06AM
MWMESSAGE WAITING SET/CLEAR)
Box: 8249 Ext: 5748249 Dir: 1 Stat: 0

/
***** 25 FEB 08 02:08:08PM
SMSSESSION MODE SET)
Port: 2E Mode: 1 Box: 8249
AppID: 0

***** 25 FEB 08 02:08:31PM
MSMESSAGE SENT)
Port: 2E Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 25 FEB 08 02:08:00PM
MsgID1: 8000a5ec MsgID2: 00000000
Len1: 14 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

/
***** 25 FEB 08 02:35:37PM
SMSSESSION MODE SET)
Port: 2F Mode: 1 Box: 8249
AppID: 0

-
***** 25 FEB 08 02:35:53PM
MSMESSAGE SENT)
Port: 2F Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 25 FEB 08 02:35:00PM
MsgID1: 8000a6b4 MsgID2: 00000000
Len1: 8 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

\
***** 25 FEB 08 05:33:52PM
SMSSESSION MODE SET)
Port: 2D Mode: 1 Box: 8249
AppID: 0

|
***** 25 FEB 08 05:52:26PM
SMSSESSION MODE SET)
Port: 2E Mode: 1 Box: 8249
AppID: 0

/

***** 25 FEB 08 06:28:02PM
SMSSESSION MODE SET)
Port: 2D Mode: 1 Box: 8249
AppID: 0

***** 25 FEB 08 06:28:44PM
MSMESSAGE SENT)
Port: 2D Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 25 FEB 08 06:28:00PM
MsgID1: 80102350 MsgID2: 00000000
Len1: 33 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

***** 25 FEB 08 06:46:36PM
SMSSESSION MODE SET)
Port: 1G Mode: 1 Box: 8249
AppID: 0

\
***** 25 FEB 08 08:15:26PM
SMSSESSION MODE SET)
Port: 2E Mode: 1 Box: 8249
AppID: 0

***** 25 FEB 08 08:15:47PM
MSMESSAGE SENT)
Port: 2E Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 25 FEB 08 08:15:00PM
MsgID1: 8000ab06 MsgID2: 00000000
Len1: 13 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

\
***** 26 FEB 08 09:09:05AM
SMSSESSION MODE SET)
Port: 2F Mode: 1 Box: 8249
AppID: 0

/
***** 26 FEB 08 09:23:53AM
SMSSESSION MODE SET)
Port: 1F Mode: 1 Box: 8249
AppID: 0

-
***** 26 FEB 08 09:24:25AM
MSMESSAGE SENT)
Port: 1F Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 09:24:00AM
MsgID1: 8000ad42 MsgID2: 00000000
Len1: 17 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

/
***** 26 FEB 08 09:37:09AM
SMSSESSION MODE SET)
Port: 1D Mode: 1 Box: 8249
AppID: 0

-
-

***** 26 FEB 08 09:38:05AM
MSMESSAGE SENT)
Port: 1D Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 09:38:00AM
MsgID1: 8000ada8 MsgID2: 00000000
Len1: 48 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

\
***** 26 FEB 08 10:12:24AM
SMSSESSION MODE SET)
Port: 2D Mode: 1 Box: 8249
AppID: 0

|
***** 26 FEB 08 10:13:07AM
MSMESSAGE SENT)
Port: 2D Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 10:13:00AM
MsgID1: 80102906 MsgID2: 00000000
Len1: 34 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

-
***** 26 FEB 08 10:56:16AM
SMSSESSION MODE SET)
Port: 1F Mode: 1 Box: 8249
AppID: 0

***** 26 FEB 08 10:56:37AM
MSMESSAGE SENT)
Port: 1F Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 10:56:00AM
MsgID1: 80102a4e MsgID2: 00000000
Len1: 12 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

***** 26 FEB 08 10:58:35AM
SMSSESSION MODE SET)
Port: 2E Mode: 1 Box: 8249
AppID: 0

\
***** 26 FEB 08 10:59:37AM
MSMESSAGE SENT)
Port: 2E Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 10:59:00AM
MsgID1: 80102a60 MsgID2: 00000000
Len1: 54 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

\
***** 26 FEB 08 11:27:34AM
SMSSESSION MODE SET)
Port: 2A Mode: 1 Box: 8249
AppID: 0

-
***** 26 FEB 08 12:24:49PM
SMSSESSION MODE SET)
Port: 1E Mode: 1 Box: 8249
AppID: 0

\
***** 26 FEB 08 12:32:42PM
SMSSESSION MODE SET)
Port: 2E Mode: 1 Box: 8249
AppID: 0

|
***** 26 FEB 08 12:33:07PM
MSMESSAGE SENT)
Port: 2E Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 12:33:00PM
MsgID1: 80102dbc MsgID2: 00000000
Len1: 15 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

|
***** 26 FEB 08 12:51:43PM
SMSSESSION MODE SET)
Port: 2G Mode: 1 Box: 8249
AppID: 0

/
***** 26 FEB 08 02:36:25PM
SMSSESSION MODE SET)
Port: 2B Mode: 1 Box: 8249
AppID: 0

-
***** 26 FEB 08 02:37:13PM
MSMESSAGE SENT)
Port: 2B Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 02:37:00PM
MsgID1: 80000726 MsgID2: 00000000
Len1: 38 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

|
***** 26 FEB 08 02:41:19PM
SMSSESSION MODE SET)
Port: 1G Mode: 1 Box: 8249
AppID: 0

***** 26 FEB 08 02:41:44PM
MSMESSAGE SENT)
Port: 1G Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 02:41:00PM
MsgID1: 80000774 MsgID2: 00000000
Len1: 17 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

/
***** 26 FEB 08 04:08:09PM
SMSSESSION MODE SET)
Port: 1C Mode: 1 Box: 8249
AppID: 0

-
-

***** 26 FEB 08 04:50:46PM
SMSSESSION MODE SET)
Port: 1E Mode: 1 Box: 8249
AppID: 0

***** 26 FEB 08 04:53:51PM
SMSSESSION MODE SET)
Port: 2C Mode: 1 Box: 8249
AppID: 0

\
***** 26 FEB 08 05:10:47PM
SMSSESSION MODE SET)
Port: 1C Mode: 1 Box: 8249
AppID: 0

|
***** 26 FEB 08 05:11:10PM
MSMESSAGE SENT)
Port: 1C Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 26 FEB 08 05:11:00PM
MsgID1: 80000a6c MsgID2: 00000000
Len1: 14 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

/
***** 27 FEB 08 09:50:11AM
SMSSESSION MODE SET)
Port: 1G Mode: 1 Box: 8249
AppID: 0

***** 27 FEB 08 09:50:34AM
MSMESSAGE SENT)
Port: 1G Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 27 FEB 08 09:50:00AM
MsgID1: 80000ec0 MsgID2: 00000000
Len1: 15 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

|
***** 27 FEB 08 11:47:54AM
SMSSESSION MODE SET)
Port: 1A Mode: 1 Box: 8249
AppID: 0

***** 27 FEB 08 11:48:09AM
MSMESSAGE SENT)
Port: 1A Type: 0 Attr: 0 Snd/Rcv: 0
DstBox: 8249 SrcBox: DstAppID: 0 SrcAppID: 0
Time: 27 FEB 08 11:48:00AM
MsgID1: 80001172 MsgID2: 00000000
Len1: 5 Len2: 0 SegCT: 1
DstNode: 0 SrcNode: 0 Node Type: 0
FaxID: 0 FaxPart: 0 FaxPage: 0
PhoneNum: OCLCmd: 0

/
***** 27 FEB 08 03:10:28PM
SMSSESSION MODE SET)
Port: 2B Mode: 1 Box: 8249
AppID: 0

***** 27 FEB 08 03:12:18PM
SMSSESSION MODE SET)
Port: 2H Mode: 1 Box: 8249
AppID: 0

***** 27 FEB 08 03:12:38PM
PWTPASSWORD TEST)
Port: 2H Box: 8249 Result: 0 AppID: 0 PWType: 0

***** 27 FEB 08 03:12:38PM
SMSSESSION MODE SET)
Port: 2H Mode: 2 Box: 8249
AppID: 0

 

[KenMeans]

Well what i do not see is a MSGCNT for entry or exit so that tells me that the user never logged into the mailbox for the whole time that the CDR is showing.

So user error may have been logging into a different mailbox?

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)

 

[clock67]

I agree. I have asked him to log his access to the vmail system. I will compare to CDR and see the results. I expect as you, user error.

Thanks for your guidance.

 

[kxboy]

This is pretty common. No where in the CDR does it have a mailbox access, or password test event. When the user says they checked voicemail, maybe they checked their cell phone voicemail or, they called someone, and the call forwarded to voicemail and they left a message. The users will say "I was in voicemail yesterday" But they never actually logged in to their own mailbox. Also, there is a CDR event for MWI after the first message. A lot of delayed message reports are the result of MWI not working correctly. This can be very random, and hard to find. But if the user depends on the MWI light on the phone, and it does not go on, it will result in a delayed message report, not a "my MWI did not go on" report. I would look closely at the MWI for any problems.

 

[JcBWF]

kxboy - not sure what software your on but my CDR shows an event for the person pgiing in and listening to msgs.



Perfection is expected, Excellence is Tolerated

 

[KenMeans]

That just depends on what you are collecting in the online CDR for message detail.

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)