"Error P1 on message type P2 on timeslot P3"
Posted: 14 Sep 2009 10:11
Hi,
recently there are many of those "Error P1 on message type P2 on timeslot P3" errors on my OmniPCX Enterprise 9.0
Detailled information is:
"Zusätzlicher Text Error 14 on message type 3 on timeslot 0
Information Fehlerdiagnose-Identifizierer: 4403
Diagnose "Error P1 on message type P2 on timeslot P3
P1 Error number
An error occurred during call setup or teardown
P1 :
- 1 : message size is wrong
- 2 : 8021Q parameters are missing
- 3 : bug in TLV
- 4 : timeslot is missing or is wrong in TLV
- 5 : message is not consistent
- 6 : transit is not available
- 7 : not enough resource on coupler
- 8 : unknown connection from cpu
if appears after CPU switch over, check up the CPU
- 9 : volume is too big
- 10: volume is too small
- 11: load problem - communication accepted
- 12: load problem - communication rejected
- 13: local communication release decision
- 14: message handling time too long => lost message
P2 :
- 1 : MSG_RTP_CONNECT - during com establishment
- 2 : MSG_VCOMP_SETUP - during voice parameters configuration
- 3 : MSG_RTP_DISCONNECT - during com disconnection
P3 : timeslot number in decimal
no reaction of the system
Check coupler binary and cpu compatibility if
P1 = 1,2,3,4,5,6.
Bug on coupler if P1 = 7,14.
Bug on cpu (due to switch over) if P1 = 8.
Check cpu parameter volume if P1 = 9,10.
"
Well, what does it actually want to tell me?
recently there are many of those "Error P1 on message type P2 on timeslot P3" errors on my OmniPCX Enterprise 9.0
Detailled information is:
"Zusätzlicher Text Error 14 on message type 3 on timeslot 0
Information Fehlerdiagnose-Identifizierer: 4403
Diagnose "Error P1 on message type P2 on timeslot P3
P1 Error number
An error occurred during call setup or teardown
P1 :
- 1 : message size is wrong
- 2 : 8021Q parameters are missing
- 3 : bug in TLV
- 4 : timeslot is missing or is wrong in TLV
- 5 : message is not consistent
- 6 : transit is not available
- 7 : not enough resource on coupler
- 8 : unknown connection from cpu
if appears after CPU switch over, check up the CPU
- 9 : volume is too big
- 10: volume is too small
- 11: load problem - communication accepted
- 12: load problem - communication rejected
- 13: local communication release decision
- 14: message handling time too long => lost message
P2 :
- 1 : MSG_RTP_CONNECT - during com establishment
- 2 : MSG_VCOMP_SETUP - during voice parameters configuration
- 3 : MSG_RTP_DISCONNECT - during com disconnection
P3 : timeslot number in decimal
no reaction of the system
Check coupler binary and cpu compatibility if
P1 = 1,2,3,4,5,6.
Bug on coupler if P1 = 7,14.
Bug on cpu (due to switch over) if P1 = 8.
Check cpu parameter volume if P1 = 9,10.
"
Well, what does it actually want to tell me?