Octel O350 Digital Networking error 96

[almonddw]

Digital Networking between our Octel 350 ver 3.11 and AVAYA Message Networking Node ver 3.1 is not working. (Note. Message networking (using Digital Networking) is working fine between the O350 and another MN ver 3.1 node on our network). Messages sent from a user on the O350 to the MN node are not accepted by the MN node (MN CDR shows no activity). Octel System Manager mailbox reports Error 96 with Node 1 (MN node). I can't find any documentation that provides information regarding error 96.
Ping tests from O350 to MN node and from MN node to O350 are good.
Does anyone have any info regarding Octel error 96?

Menu 13.2 shows:

22 SEP 11 07:54:40AM Company Name CPU A: Active RYRYRY
VPMOD Serial # ........ 55555
Software Rel. .... Aria 03.11.05-1
Network Serial # ...... 6666 System Type ........... 350
Card 2 M Prom: 95.10 Disk: GE.03 Card 3 E Prom: 93.07
Card 5 N Prom: 05.F9 Card 6 A A: 93.01 B: 95.10 C: 91.01
Card 1 F Prom: GE.03 Disk: NA. Card 8 L DLC: NA. T1/E1: NA.
Card 10 L DLC: NA. T1/E1: NA. Card 12 L DLC: NA. T1/E1: NA.
Card 14 L DLC: NA. T1/E1: NA. Card 16 L DLC: NA. T1/E1: NA.
Card 18 L DLC: NA. T1/E1: NA.
Line Card Digitization Rate: B Telephone System Type: 1 - North American
Boot Prom ........ 96.12 IPL Extension .... 20.24 DLC .............. 90.03
Menus ............ 31.61 Termcap .......... 20.12 DSP .............. 12.05
ACP188 ........... 92.02 ACP386 ........... 33.13 T1/E1 ............ NA.
UDLC ............. 02.41 UDSP ............. 24.65
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

20 SEP 11 11:41:39AM
*** Digital Networking - Retries Exhausted
>>> NOTIFY SUPPORT REPRESENTATIVE
00000 14C0BE01 65010000 9201273D 76DE0100 *....e.....'=v...*
00010 01008CFF *.... *



Online CDR info

***** 22 SEP 11 02:07:32PM
DN_CONNCONNECT REQUEST)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:0
Channel: 164 IPAddr: 10.10.10.10 Serial: 80000 RemChannel: 0
OutChnl: 1 InChnl: 0 TotChnl: 16 MaxOutChnl: 12

***** 22 SEP 11 02:07:33PM
DN_MSG_GETGET MESSAGE FROM QUEUE)
TaskID:00bc SvcMode:1 OpType:0 Node:1 Status:0
MsgType: 6 MailID: 0x00000000 MsgIDSC: 0x00000000
MsgByte: 0 MsgSecs: 0 SegCnt: 0
Priority: 0 DelivTime: 22 SEP 11 02:07:00PM
DelivOpt: 0 SrcBox: DestBox: 5559440694
DestName: FaxIDSC: 0x00000000
FaxStat: 0 FaxPages: 0

***** 22 SEP 11 02:07:33PM
DN_ENVELOPEMESSAGE ENVELOPE)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:1
MsgType: 6 MailID: 0x00000000 MsgByte: 0 MsgSecs: 0
SegCnt: 0 SrcBox: 0000000000000000 DestBox: 5559440694
DestName: Priority: 0 DelivTime: 22 SEP 11 02:07:00PM
Forward: 0 DelivOpt: 0 RFlag: 0 TFlag: 0

***** 22 SEP 11 02:07:33PM
DN_MSG_GETGET MESSAGE FROM QUEUE)
TaskID:00bc SvcMode:1 OpType:0 Node:1 Status:0
MsgType: 1 MailID: 0x800004fa MsgIDSC: 0x800004fa
MsgByte: 32768 MsgSecs: 8 SegCnt: 1
Priority: 3 DelivTime: 22 SEP 11 02:07:00PM
DelivOpt: 0 SrcBox: 1110000 DestBox: 5559440694
DestName: FaxIDSC: 0x00000000
FaxStat: 0 FaxPages: 0

***** 22 SEP 11 02:07:34PM
DN_ENVELOPEMESSAGE ENVELOPE)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:0
MsgType: 1 MailID: 0x800004fa MsgByte: 49152 MsgSecs: 8
SegCnt: 2 SrcBox: 1110000 DestBox: 5559440694
DestName: Priority: 3 DelivTime: 22 SEP 11 02:07:00PM
Forward: 0 DelivOpt: 0 RFlag: 0 TFlag: 0

***** 22 SEP 11 02:07:34PM
DN_MSG_SEGMSG SEGMENT HEADER)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:0
MsgType: 1 SegType: 1 SegLabel: 1
MsgByte: 16384 LineSC: 0xb934 RecType: 0
SegFlag: 0 SegIDSC: 0x8010b934


***** 22 SEP 11 02:07:35PM
DN_MSG_SEGMSG SEGMENT HEADER)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:0
MsgType: 1 SegType: 1 SegLabel: 0
MsgByte: 32768 LineSC: 0x04fa RecType: 0
SegFlag: 0 SegIDSC: 0x800004fa


***** 22 SEP 11 02:07:35PM
DN_SAVESAVE MSG)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:255
MsgType: 0 Flag: 0

***** 22 SEP 11 02:07:35PM
DN_SESS_ENDSESSION END)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:0
MsgType: 0 Flag: 1

***** 22 SEP 11 02:07:40PM
DN_DISCDISCONNECT REQUEST)
TaskID:00bc SvcMode:1 OpType:1 Node:1 Status:0
Channel: 164 Serial: 80000
OutChnl: 1 InChnl: 0 TotChnl: 16 MaxOutChnl: 12

 

[KenMeans]

this is a name net issue with the user. The user sending the message has a very old name recorded(it was recorded before the octel was upgraded) you can look at the user record update in cdr of the user to see when the mailbox was added. and it is rejecting it. Have the user rerecord the mailbox name and it will work.

If the 350 was converted from an older aspen this can happen. you can force all users to rerecord the mailbox name in menu 1 2 i think. i can look it up if you need it.



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)

 

[almonddw]

The sending mailbox on the O350 is my own mailbox. My recorded name has been recorded well after the upgrade from the Maxum over 15 years ago.
I can send a voice message from it to one AVAYA Message networking node (ver 3.1) but when I send that same message to another AVAYA Message Networking node (ver 3.1 also), I get error 96 returned from just that one node.

 

[KenMeans]

the node setup in the one that does not work must be different in some way or you mailbox is not in range. did it work before and then just stop ?

is this a forwarded message as the DN_envelope shows 2 segments to the message.

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)

 

[almonddw]

This is a new MN node that I am adding and has a different dialing pattern (10 digits) than the other node (7 digits). But other than that they are the same. Do you have a manual or printout that provides an explaination of "error 96"? I have the documentation for analog and digital networking errors 4x and 5x series but nothing for 9x errors.

 

[KenMeans]

the code shows as an unknown error from the far end. Are other mailboxes able to send messages ? what is the networking S/N of the other working MN system ? I assume they are not the same as the one in the cdr is 80000 and that is the default of all MN systems.

When you say error 96 i assume you mean that is what you hear in the system mangers mailbox right. If so that just means that it could not talk to the far end.

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)

 

[KenMeans]

Any luck ?

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)