Filter
Top Products
Denial Event Tables
Issue 1 June 2005 239
2027 Annc not found on board User attempted to play
MO_VAL_BD announcement and
file was not found on board.
2028 Annc file has bad format User attempted to play
MO_VAL_BD announcement and
file had bad format.
2029 IP GRJ-NSD has invld
OID
Gatekeeper Request rejected
because the Non Standard Data
(NSD) from the registered
application has an invalid object ID.
UID IP address of the endpoint
2030 IP GRJ-Can't decode
NSD
Gatekeeper Request rejected
because of failure to decode Non
Standard Data (NSD) element.
UID IP address of the endpoint
2031 IP GRJ-Unexpected NSD
msg
Gatekeeper Request rejected
because of unexpected Non
Standard Data (NSD) message
from the registered application
endpoint.
UID IP address of the endpoint
2032 Force Unregistration Req Force Unregistration Request.
Instruct the RAS manager to
cleanup a User ID which had just
been registered prior to a system
restart. This event is not logged, but
only passed in the URQ.
2033
Communi-
cation
Manager
Release
2.2 and
earlier
IP FURQ-Demand
Unregister
Force Unregistration Request. The
command to force unregister
endpoints has been executed from
the SAT.
User ID IP address
2033
Communi-
cation
Manager
Release
3.0
IP FURQ-Demand
Unregister
Force Unregistration Request.
Reset ip-stations was executed
from the SAT to force unregister
endpoints.
NULL NULL
2034 Illegal TSC interaction A QSIG Non Call
Associated-Temporary Signaling
Connection (NCA-TSC) tried to
route out an AT&T TSC, or vice
versa, and this interaction is not
supported. This might occur when a
bsr_poll call over an IP trunk tries to
use a QSIG TSC but is tandemed
out an AT&T TSC.
2035 NCA-TSC not available Possible causes:
● The terminated
administered TSC
endpoint is disabled
● The incoming Non Call
Associated-Temporary
Signaling Connection
(NCA-TSC) call arrived at
the wrong signaling group
● The Maximum number of
NCA-TSC is set to 0
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
2 of 9