Admin status
From Pbxnsip Wiki
This tab contains the overall system status related pages.
Contents |
General
This page contains general status information about the PBX.
Version: This field shows the version that is currently running. The first number is the major software number, the second the minor software release and the third number the patch level. The fourth number is the build number. It also displays the operating system information.
License Status: This field shows the descriptive text of your license. This text is embedded in the license string.
License Duration: This filed shows you how long the license will last. If you see "Permanent", then you have a permanent license and there is not expiry on it.
Additional license information: This typically shows you the usage of accounts and extensions.
Ex: Extensions: 10/200 Accounts: 17/400.
Working Directory: As the name suggests, this is the working directory for the PBX. All the data is stored under this directory. If you want to backup your data, you should copy the data in this directory.
MAC Addresses: Displays all MAC addresses for different interfaces on your system.
Calls: This field tells you how many successful/unsuccessful calls were made on the system after restart. Successful calls are those calls that were in the connected state. For example, when the other side did not pick up, that call counts as unsuccessful. The CDR number in brackets shows you how many CDR entries the PBX keeps internally for listing purposes. If this number grows too large, you should consider making the Keep CDR Duration shorter. The Last number shows how many calls are currently active on the system.
Ex: 127/16 (CDR: 385) 1/2 Calls
SIP packet statistics: This field shows how many SIP packets have been sent and received by the PBX since the last restart.
Ex: Tx: 560 Rx: 559
Emails: Number of successful and unsuccessful emails sent by the PBX. If the last email could not be sent successfully, you will see a special warning.
Ex: Successful sent: 26 Unsuccessful attempts: 0
Uptime: This field gives you information how long the system is running. The format for this line is "date current time(in HH:MM:SS) uptime in number of days and HH:MM:SS). In Windows, you will also find additional information about the memory usage. The PBX will also show how many WAV file it has currently in memory (typically because there is IVR going on).
Ex: 2009/3/27 16:43:52 (uptime: 0 days 01:01:06) (10MB/2030MB 60% 2647956-0) WAV cache: 1
In this same status page, PBX also displays some useful graphs. They include, Media CPU usage, Calls and the Registration graphs.
For the Media usage, here is legend.
- The x-axis represents the time as 0-24 hrs
- The y-axis represents the percentage of CPU usage as 0-100%
- The blue horizontal line shows the CPU load when new calls are being rejected because of performance problems.
- The yellow/lime green vertical line shows you where the log is currently writing into the graph.
- The green fields show you the average load (averaged over a period of six minutes)
- The blue lines above the green fields show you the peak usage of the CPU (averaged over a period of three seconds)
For the Calls, here is the legend.
- The x-axis represents time as 0-24 hrs
- The y-axis represents a number (of calls/call legs)
- The blue represents number of call legs. Note that for a basic call, there will be 2 call legs.
- The red represents the number of calls.
For the Registrations, here is the legend.
- The x-axis represents time as 0-24 hrs
- The y-axis represents a number( of registration and subscriptions).
- The blue represents number of registrations.
- The red represents number of registrations + subscriptions.
Logfile
The log file contains a list of the most recent log entries. It is actually not a file; it is an internal list of the last messages. The number of the messages that are shown to you here is a setting that was discussed in the Settings section.
For every log entry, the PBX shows the time when the message was generated and the log level. For SIP packets and in some other situations, the PBX attaches the respective content to the log message, so that the formatting gets easier. If messages are being repeated, the PBX reports just the number of repetitions.
You may clear or reload the logfile with the links that are presented on the page. If you want to trace a longer context, you should write the log messages to a file and use a standard text editor to go through the messages. Also, when reporting trouble, try to make a snapshot of the log messages that help to find the problem.
Call Log
The call log shows the last calls that were made on the system, independently from the domain. You will see the start date, the source and destination, the account that will be charged to a call and the duration of the call, if the call connected. The length of the log is set in Appearance section.
The start time for unconnected calls is the time when the call was initiated. For calls that actually connected, the connection time will be used.
The "To" and "From" headers are copied as they are. For calls that run over trunks that use registration, this might be annoying, because the PBX will use the identity of the trunk in the "From" field. However, for such calls it will display the account that initiated that call in the Charge column. Note that in the case of call redirect and transfer the PBX will charge the account that initiated there direction and transfer. In these cases you will see several CDR in the log; one for the initial call and another one for the transfer or redirect call.
For calls that were redirected to the mailbox, the PBX adds a "M" flag. For calls that were redirected to an external number, the PBX adds a "E".
Calls
In the calls menu, you will see which calls are currently active on the system.
You will see when the call started, the source and destination and the call state. The state may be early or connected.
If you enable the "Analyze audio levels" in the system administration Logging settings, the calls list also display the volume of the call legs (see Gain Adjustment).
