User Manual V2IU 4350 Converged Network Appliance
Call Termination
The call termination cause may also give some information about why the call terminated or failed to be established.
•“Out of system resources”
The call could not be completed because the system was out of system resources.
•“Client owning the call has been deleted”
The call could not be completed because the client that made this call was deleted during the call setup.
•“Connection to destination could not be established” A TCP connection to the destination could not be established.
•“Connection refused by destination”
The call could not be completed because the destination refused the incoming
TCP connection.
•“No route to destination”
A TCP connection to the destination could not be established because the des- tination could not be reached. This could happen if there is no route to the destination or, if the destination is on the same subnet, the destination does not answer to ARP requests.
•“Connection to destination timed out”
The TCP connection attempt to the destination timed out before it could be established.
•“Call ended by source”
The call was gracefully terminated by H.323 signaling from the source. This usually indicates that the endpoint intended to terminate the call.
•“Call ended by destination”
The call was gracefully terminated by H.323 signaling from the destination.
This usually indicates that the endpoint intended to terminate the call.
•“Connection terminated by source”
The call was terminated because the source terminated the TCP connection without prior call termination signaling.
•“Connection terminated by destination”
The call was terminated because the destination terminated the TCP connec- tion without prior call termination signaling.
•“No admission confirm received”
The call could not be established because the admission response was not received from the gatekeeper.
•“Cannot resolve destination”
The call could not be established because the destination could not be resolved.
•“At maximum bandwidth usage”
3 - 54