The H.323 Call Status page displays information about active H.323 calls.
- Choose VoIP > H.323.
Click Call Status in the H.323 Settings navigation panel at the top of the page to open the H.323 Call Status page.
View H.323 in-progress call status using the information in the following table as a guide.
H.323 Call Status Parameters
Item | Description |
---|
Current time | Shows the current date and time. |
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 Call Status Logs Shows current H.323 call status. Refer to H.323 Call Activity Messages. |
Start Time | The time the call was initiated. |
Source | Source 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). |
- To refresh current status, click Refresh Page.
Terminate specific calls by clicking the delete icon next to the call.
Only calls where the Q.931 (and H.245) TCP connections are routed through this system can be terminated. If no Q.931 TCP connection has been received for a call, this call cannot be terminated using the H.323 Call Status page.
Some calls (for example, Gatekeeper-routed calls between two clients to this system) may show up as two calls. This is because each client has a call leg established to the outside system. In this case, terminating one of the call-legs will eventually lead to both calls disappearing, but this will not be shown immediately.