In this section:

Managing the H.323 Activity

This section outlines how to manage the H.323 activity.

To Manage the H.323 Activity

  1. Choose VoIP > H.323.

  2. Click Activity in the H.323 Settings navigation panel at the top of the page to open the H.323 Activity page.

  3. View H.323 activity using the information in the following table as a guide.

    H.323 Activity Parameters

    ItemDescription

    H.323 Current Activity

    Shows current H.323 activity.

    Current timeShows the current date and time.

    WAN Gatekeeper status

    		Describes the current gatekeeper mode settings.

    VoIP ALG Licensed Bandwidth In Use

    Displays the sum of RTP payloads of all current calls. For example, if two 384k calls are present, bandwidth use is 768. The system uses the field to subtract against the system licensed value as Video Bandwidth on the License page.

    To view the License page, choose Admin from the Configuration Menu and click license key under Registration Status. You can also choose VoIP from the Configuration Menu and click View license key at the bottom of the page.

    Current Total Bandwidth With IP Overhead

    		Displays the RTP payload of current calls and adds the estimated IP overhead. This allows you to budget the requirements for video traversing a customer WAN connection. The value is calculated by the RTP payload divided by .8 to add the IP overhead use to the total. For example, 384k/.8 = 480k of estimated bandwidth usage.

    H.323 Activity Logs

    Shows recent H.323 events such as call terminations and registration rejects. Abnormal events display specific information in red. See H.323 Call Activity Messages.

    Event/TimeType of event and the time that it occurred.
    SourceSource of the event as an IP address and an alias (when available).
    Destination

    Destination of the event as an IP address and an alias (when available).

  4. To clear H.323 activity logs, click Clear. To refresh current status, click Refresh Page.

H.323 Call Activity Messages

This section outlines the H.323 call activity messages.

H.323 Call Status Messages

Call status shows the last state of the call at the time of the event. Each call progresses through a number of states while being established. The following table lists call status messages.

Call Status Messages

MessageDescription

Caller admission request received

Received an admission request from the source endpoint and forwarded it to the gatekeeper.

Caller admission response received

Received an admission response (either confirm or reject) from the gatekeeper and forwarded it to the source endpoint.

Incoming Q.931 TCP connection established

Received an incoming Q.931 TCP connection from the source.

Attempting to establish outgoing Q.931 TCP connection

Successfully resolved the destination of the call and attempting to establish an outgoing Q.931 TCP connection to the destination.

Q.931 signaling received and forwarded

Both Q.931 TCP connections have been successfully established and Q.931 signaling has been received and forwarded.

Callee admission request received

Received an admission request from the destination endpoint and forwarded it to the gatekeeper.

Callee admission response received

Received an admission response (either confirm or reject) from the gatekeeper and forwarded it to the destination endpoint.

Incoming H.245 TCP connection established

Received an incoming H.245 TCP connection from the source.

Attempting to establish outgoing H.245 TCP connection

Attempting to establish an outgoing H.245 TCP connection to the destination.

H.245 signaling received and forwarded

Both H.245 TCP connections have been successfully established and H.245 signaling has been received and forwarded. At this point, the call is considered established, even though no media channels have been opened up yet.

Outgoing media channel established

An outgoing media channel (from the LAN/subscriber side to the WAN/provider side) has been opened.

Incoming media channel established

An incoming media channel (from the WAN/provider side to the LAN/subscriber side) has been opened.

Bidirectional media channels established

Media channels have been opened in both directions. This is a normal call where media is being sent in both directions.


H.323 Call Termination Messages

Call termination messages can help troubleshoot the cause of the call failure. The following table lists call termination messages.

Call Termination Messages

MessageDescription

Out of system resources

The call could not be completed because the system did not have enough 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

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 destination 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 connection 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

The call could not be established because the system already is at the maximum allowed bandwidth.

Call exceeds maximum per-call bandwidth

The call could not be established because the bandwidth requested for the call exceeds the configured per-call maximum.
Received admission rejectThe call was terminated because an admission reject was received from the gatekeeper.

Received disengage request

The call was terminated because the endpoint requested to tear down the call.

Received invalid data

The call could not be established because the system received invalid data on the signaling channel.

Cannot find client

The call could not be established because the called client could not be found.


  • No labels