Serenade Octel 200 Alarms

[melben]

I have had alarms on a Serenade Octel 200.

TYPE SLOT CHNL #BAD DATA1 DATA2 DATA3 DATA4
24 08 01 6 00000009 00000028 00000000 00000003
24 08 01 1 00000009 00000027 00000000 00000003

According to the Hardware Error Type and Remedies section in the admin guide it states that the above alarm indicates that "got call, but no call record (or call was too late)" Data 2 = Port #call came in on. Data 3/4 not used. The call rang in on the port but the ATTIC card didn't send the call information. Therefore, the Octel port answered and played Co greeting.

The remedy states to check the digital display line config in the PBX. Pay particular attention to the port appearance on the keys.

My question is What should I look at in the PBX? The ports associated with the Octel look fine. Nothing has changed. Is there anyway to reset the card. This Attic card has 40 line appearances and only 20-27 come up in the Data 2 section of the alrams. Thanks

 

[jon24422531]

What is the PBX, and what release is it on? Also what release is the Octel on?

The Octel line cards can be reset by pulling them out and reseating them.

Jonathan Schofield

http://www.jonschofield.com

 

[melben]

The Octel 200 is at release S.1.1.0-2. The PBX is a Definity G3r6. Thanks

 

[doktor]

Hi melben

Is there some kind of data link between the Octel 200 and the PBX (AVAYA Definity)??
With some PBX as Ericsson MD110 or Nortel Meridian the installation could have made with a serial cable (RS-232 / V24).
The type 24 fault will occur if the data packet (or call record) on the serial interface arrives later (than a given timer) or just does not arrive at all.
For instance the MD110 from Ericsson expects the data packet with info of the callers ID and so on - to arrive before the actual call opens the analogue or digital port in the OCTEL voice mail system.

So there could be a timing problem.

There is in the PBX a table telling what port number in the PBX is equivalent to what port number in the OCTEL 200.

Maybe some of these ports have been swapped or forgotten.
If this is the case you will get the type 24 alarm every time you call the individual port number.

Hope that this can give you some ideas.

Let me know your progress...

BR doktor

 

[doktor]

Resetting will not help you in this case.

Maybe the line (port) numbers mentioned in DATA2 has to be swapped. Are you using analogue lines or are the lines AVAYA system specific (system phones with AVAYA special signalling)?

br doktor

 

[melben]

There are 48 analog (2500) lines programmed on 16 port TN746B cards. The displays all read D-3800 through D-3847. I see nothing wrong with the card or the ports. Any idea?

 

[jon24422531]

I would suggest pulling the ATTIC card in the Octel and reseating it, followed by the line card(s). If still no joy, then perhaps a re-boot of the Octel (@resta). I am beginning to think that it may be a faulty card though, most likely the ATTIC. (AT&T Interface Card)

Jonathan Schofield

http://www.jonschofield.com

 

[doktor]

melben

Seems to be a big system!

Please try to erase the alarm log by @C H.

Then check @L H after calling to each individual analogue port D-3800 through D-3847.
This @L H you should paste here that I can have a closer look.

What has happened just before the fault was seen?
Did you have loss of power?
Maybe a @RESTA will help.

Still I think there is a mismatch between system port numbers and physical port numbers in the PBX or in the Octel. These tables must match, so that when the PBX sends a call to system port number 8, then the physical port 8 should go off-hook.

BR doktor

 

[typetwo]

Would have to agree with doktor on this sounds like a mismatch with the ports ... unless the octel has got itself in a bit of a state cant see how a reboot will help but I suppose if it is not going to cause too much disruption it is worth a try.

 

[doktor]

Nice point of view, typetwo.
After many years of OCTEL experience TYPE 24 faults are only observed when some cabling has been changed by the customer himself or engineers with lack of knowledge.

doktor

 

[joeOctel]

Note that the Data2 field is usually a hex value in this instance so make sure that you are looking ports 39 (hex 27) and 40(hex 28). Also note that you can do a List Trace at the time these hardware errors occurred to see if this will give you any clues. In an ATTIC integration the analog voicemail ports should not normally be receiving calls directly, only the ATTIC ports (7405 digital phones in the voicemail hunt group) should be sending calls to the analog voicemail ports. You should check to make sure that regular user stations are restricted from calling these analog stations directly. You should also follow the previous suggestions to make sure that the last 8 ports (32 through 40) are wired up correctly to the blocks and that the programming for the slots table is correct as well.