![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 588](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550588.webp)
14-14
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 14 General Troubleshooting
Command Responses
Fault Reason Responses
The following responses can be returned for the fault reason (fault-reason) response for a
subscriber
termination
command. One or more values can be returned, depending upon the operating conditions
of the Call Agent.
•
The media gateway is down.
•
The media gateway is unreachable.
•
The media gateway is in a faulty state.
•
The media gateway is transitioning to another state.
•
The transaction could not be executed, due to a transient error.
•
The transaction could not be executed because the endpoint is unknown.
•
The transaction could not be executed because the endpoint is not ready.
•
The transaction could not be executed, endpoint does not have enough resources available.
•
The transaction could not be executed because a protocol error was detected.
•
The transaction could not be executed because the command contained an unrecognized extension.
•
The transaction could not be executed because the gateway is not equipped to detect one of the
requested events.
•
The transaction could not be executed because the gateway is not equipped to generate one of the
requested signals.
•
The transaction could not be executed because the gateway cannot send the specified announcement.
•
Invalid conn identifier.
•
Invalid call ID.
•
Unsupported mode or invalid mode.
•
Unsupported or unknown package.
•
Endpoint does not have a digit map.
•
The transaction could not be executed because the endpoint is restarting.
•
Endpoint redirected to another Call Agent.
•
No such event or signal.
•
Unknown action or illegal combination of actions.
•
Internal consistency in local connection options.
•
Unknown extensions in local connection options.
•
Insufficient bandwidth.
•
Missing remote connection descriptor.
•
Incompatible protocol version.
•
Internal hardware failure.
•
CAS signaling protocol error.
•
Failure of a group of trunks.
•
Unsupported values on local connection options.
•
Response too big.