|
|
00 |
Normal call termination (no error). |
01 |
A storage resource shortage has occurred on the local device. |
02 |
A storage resource shortage has occurred on a remote device controlled by the local device. |
03 |
A media resource shortage has occurred. |
04 |
A media failure has occurred because of the failure in the underlying hardware or through management action. |
05 |
A continuity test has failed. |
06 |
The requested media resource is blocked or has been quiesced. |
07 |
Media is in use by another call. |
08 |
Media is not configured. |
09 |
An error has occurred due to a configuration inconsistency. |
10 |
Media is unavailable. |
11 |
Media is congested. |
12 |
An internal error has occurred. |
13 |
No terminations are available. |
14 |
An error other than a failure, resource, or bandwidth shortage has occurred in the media layers. |
15 |
A request to reset a termination has failed. |
16 |
An interworking error has occurred. |
17 |
A security error has occurred. |
18 |
This is not a valid address. |
19 |
This is not a valid transit network. |
20 |
There is no route available to the specified destination address. |
21 |
There is no route available to the specified transit network. |
22 |
This number is unavailable because the number has changed recently. |
23 |
This is an unallocated number. |
24 |
There is no route-to-destination address due to congestion. |
25 |
There is no route-to-transit network due to congestion. |
26 |
LNP call is misrouted to the exchange that does not serve the destination number. |
27 |
Internal congestion has occurred. |
28 |
The media capabilities requested for the call are not supported. |
29 |
The maximum number of routing retries are exceeded. |
30 |
The resources are unavailable for SBC. |
31 |
The destination resource is incompatible with request. |
32 |
This is an invalid message. |
33 |
This is an unrecognized signaling message type. |
34 |
Recovery on timer expiry. |
35 |
Unrecognized or unimplemented signaling parameter has been passed on. |
36 |
Unrecognized or unimplemented signaling parameter has been discarded. |
37 |
The signaling protocol error has occurred. |
38 |
This is a temporary failure. |
39 |
No answer. |
40 |
The destination is out of order. |
43 |
Unauthorized request. |
44 |
Network congestion. |
45 |
The request is not supported for an unspecified reason. |
46 |
The specified resource is not equipped. |
47 |
Call to call services. |
48 |
An unspecified or miscellaneous error has occurred. |
49 |
The named digit map requested by the call agent is unknown to the media gateway. |
50 |
The media bandwidth is insufficient. |
51 |
The routing has failed because no digits were dialed. |
52 |
A subscriber has attempted to dial a number that is restricted. |
53 |
QoR call to a subscriber has failed because the subscriber was not found. |
55 |
Called user has rejected the call. |
56 |
The call could not be routed to a subscriber because the subscriber's termination could not be located. |
57 |
Called subscriber is busy even though media can be allocated to the subscriber. |
64 |
A branch that was successfully audited internally following a Call Agent failover does not indicate that the call failed during the Call Agent failover. |
65 |
A subscriber attempted to register for an interval that was too brief. |
66 |
This request is unauthorized by proxy. |
67 |
The call's early media exceeded the time limit set by access control before the call was connected. |
68 |
A glare scenario was detected, where each party in the call sent a message of the same type simultaneously. |
69 |
An endpoint has attempted a renegotiation at an illegal point. |
70 |
An endpoint has sent media parameters that were unparseable. |
71 |
A message or one of its subcomponents was too large to process. |
72 |
An endpoint indicated that a request must be redirected. |
73 |
(CAC-specific) Call setup rate have exceeded a maximum limit. |
74 |
(CAC-specific) Number of call updates have exceeded the maximum limit. |
75 |
(CAC-specific) Number of calls have exceeded the maximum limit. |
76 |
(CAC-specific) Number of media channels used have exceeded the maximum limit. |
77 |
(CAC-specific) Bandwidth used have exceeded the maximum limit. |
78 |
(CAC-specific) Number of registered endpoints have exceeded the maximum limit. |
79 |
(CAC-specific) Rate of endpoint registrations have exceeded the maximum limit. |
80 |
Media could not be established because an acceptable media transport type could not be negotiated for any media stream. |
81 |
Media is not yet established because of redirection. The system is retrying. |
82 |
No subscriber record with the specified search keys is found. |
83 |
(CAC-specific) Rate of in-call messages have exceeded the maximum limit. |
84 |
(CAC-specific) Rate of out-of-call requests have exceeded the maximum limit. |
85 |
Register request from endpoint was rejected because a delegate subscriber exists in subscriber database (SUBDB) with matching search keys. |
86 |
(CAC-specific) Media transport settings of the call caused it to fail. |
87 |
Routing failed because the route to the address is unavailable. |
88 |
No acceptable codec that can be used for a call. |
89 |
The number of media channels requested is greater than the maximum number the SBC supports. |
90 |
An attempt to transfer the call has failed. This is used when the reason for a call is released after an attempt to transfer it to a third party has failed. |
91 |
The E.164 number mapping (ENUM) processing encountered an error. |
92 |
The SBC received a message with SDP parameters that were unparseable. |
93 |
A subscriber signaling bearer channel is unavailable. |
94 |
A subscriber media bearer channel has failed mid-call. |
95 |
A subscriber media bearer channel was rejected, either during call setup or during renegotiation. |
96 |
Privacy requirements could not be satisfied for the call. |
97 |
A CAC-specific error code indicating that a policy disallowing the RTP for the call caused it to fail. Note: This error code is used only in internal-to-ICC, and should not be communicated to the signaling stacks. |
98 |
A CAC-specific error code indicating that a policy disallowing the SRTP for the call caused it to fail. Note: This error code is used only in internal-to-ICC, and must not be communicated to the signaling stacks. |
99 |
Policy disallowing the RTP or the SRTP IW for the call caused it to fail. |
100 |
No media gateway (MG) that is able to support the SRTP was found for the call, causing it to fail. |
101 |
SRTP processing encountered a miscellaneous error. |
102 |
Call released because media packets forwarding (MPF) has detected a fatal error. |