Avaya 03-300430 User Manual

Page of 2574
Denial Event Tables
Issue 1 June 2005
241
 
2056
No null caps SBS orig 
end
IncomingMsg. Null caps not 
received on originating end of 
Separation of Bearer and Signaling 
(SBS) trunk.
2057
No null caps SBS term 
end
IncomingMsg. Null caps not 
received on terminating end of 
Separation of Bearer and Signaling 
(SBS) trunk.
2058
Null caps on H323 trunk
IncomingMsg. Null caps received 
on terminating end of H323 trunk.
2059
SecCode change 
disallowed
Change of security code through 
Feature Access Code not 
supported for IP.
2060
SA8508:Off
Emergency access call to the 
attendant using the 2nd access 
code is not permitted because the 
SA8508 is not optioned. 
2061
Invalid Post msg dgt/tmo
Post message digit timeout.
2062
Post msg too many msg 
dgt
Post message too many digits.
2063
Post msg not stn user
Post message not station user.
2064
IP RRJ-NSD encode 
failed
Registration rejected because of 
failure to encode Non-standard 
Data (NSD) message.
UID
IP address
2065
IP RRJ-Invalid vendor id
Registration rejected because LSP 
requesting registration has not sent 
a valid vendor ID.
NULL
IP address
2066
IP RRJ-LSP obj not init
Registration rejected because the 
LSP object has not been initialized.
NULL
IP address
2067
IP RRJ-NSD improper 
OID
Registration rejected because the 
Non-standard Data (NSD) sent by 
the LSP contains an invalid OID.
NULL
IP address
2068
IP RRJ-Cannot decode 
NSD
Registration rejected because of 
failure to decode Non-standard 
Data (NSD) message sent by the 
LSP.
NULL
IP address
2069
IP RRJ-Unxpctd NSD
Registration rejected because of 
receipt of an unexpected 
Non-standard Data (NSD) message 
from LSP.
NULL
IP address
2070
MG must send full reg 
msg
Media gateway attempted 
registration with “warm start” 
condition, but the controller needs 
“cold start” data.
2071
Serial Number incorrect
Media gateway attempted to 
register with a different serial 
number.
Table 53: Call Process denial events (2021 - 2299)  (continued) 
Event
Type
Event Description, as it 
appears on the event log 
Explanation
Event Data 1
Event Data 2
 4 of 9