Viewing Statistics
Viewing
SIP Statistics
SNAPsolution comes with a number of diagnostic capabilities
for troubleshooting the system.
Using
the Statistics command in the Diagnostics
menu, you can
view the following statistics:
-
SIP statistics
-
Processing
statistics
-
Connection
statistics
-
Domain statistics
SIP
statistics show system-wide SIP processing information. To view SIP
statistics:
The
Offset and Resolution controls
at the bottom of the
page let you offset the starting time in hours and change the
statistics resolution from 1 minute up to 1 day.
Columns
in the Registration Statistics Area
|
Name
|
Type
|
Db
Field
|
Description
|
|
TIME
|
time
|
status_time
|
Time
of event.
|
|
#
Session
|
delta
|
session_count
|
Number
of SIP sessions in the observation interval.
|
|
#
Not Routed
|
delta
|
session_notrouted
|
Number
of no routes in the observation interval.
|
|
#
Routed
|
delta
|
<computed
from sesion_count - session_notrouted>
|
Number
of in calls routed in the observation interval.
|
|
#
Answered
|
delta
|
session_answered
|
Number
of calls answered in the observation interval.
|
|
%
Routed
|
ratio
|
<computed
from (session_count - session_notrouted)/session_count>
|
Percentage
of calls routed in the observation interval.
|
|
%
Answered
|
ratio
|
<computed
from session_answered/session_count>
|
Percentage
of calls answered in the observation interval
|
Columns
in the Registration Statistics Area
|
Name
|
Type
|
Db
Field
|
Description
|
|
#
Registration
|
delta
|
registration_count
|
Number
of REGISTERs received in the observation interval.
|
|
#
Authorized
|
delta
|
registration_authorized
|
Number
of REGISTERs authorized in the observation interval.
|
|
#
Not Authorized
|
delta
|
registration_notauthorized
|
Number
of REGISTERs not authorized in the observation interval.
|
|
Register
Sent
|
delta
|
register_sent
|
Number
of REGISTERs sent in the observation interval.
|
|
407
Rcv
|
delta
|
register_sent_challenged
|
Number
of outbound REGISTERs challenged in the observation interval.
|
|
200
Rcv
|
delta
|
register_sent_authorized
|
Number
of outbound REGISTERs authorized in the observation interval
|
|
SCRB
Rcv
|
delta
|
subscribe_received
|
Number
of SUBSCRIBEs received in the observation interval.
|
|
SCRB
OKed
|
delta
|
subscribe_ok
|
Number
of SUBSCRIBE acknowledged in the observation interval.
|
|
NTFY
Sent
|
delta
|
notify_sent
|
Number
of NOTIFYs sent in the observation interval.
|
Processing
Statistics
The
Processing Statistics page shows meaningful information about the
system’s operation. To view processing statistics:
The
Offset and Resolution controls
at the bottom of the
page let you offset the starting time in hours and change the
statistics resolution from 1 minute up to 1 day.
Columns
in the Processing Statistics Area
|
Name
|
Type
|
Db
Field
|
Description
|
|
TIME
|
time
|
status_time
|
Time
of event.
|
|
Packet
Rcv
|
delta
|
rxpkt_count
|
Number
of SIP packets received in the observation interval.
|
|
Packet
Dispatched
|
delta
|
pkt_dispatched
|
Number
of SIP packets dispatched in the observation interval.
|
|
Packet
Xmt
|
delta
|
txpkt_count
|
Number
of SIP packets transmitted in the observation interval.
|
|
Session
Connected
|
count
|
session_connected
|
Number
of instantaneous active SIP sessions.
|
|
UAS
Trans
|
delta
|
uas_count
|
Number
of UAS transactions in the observation interval.
|
|
UAC
Trans
|
delta
|
uac_count
|
Number
of UAC transactions in the observation interval.
|
|
Call
Leg
|
delta
|
leg_count
|
Number
of call legs in the observation interval.
|
|
VMail
Msg
|
delta
|
vmail_msg_count
|
Number
of voice mails recorded in the observation interval.
|
|
VMail
Packet
|
delta
|
vmail_pkt_count
|
Number
of RTP packets recorded during voice mail in the observation
interval.
|
|
VMail
Gap
|
delta
|
vmail_gap_count
|
Number
of RTP packet gaps during voice mail recording in the observation
interval.
|
|
VMail
% Gap
|
ratio
|
<computed
from vmail_gap_count/vmail_pkt_count>
|
Percentage
of RTP packet gaps during voice mail recording.
|
|
Relay
Rate
|
rate
|
<computed
from relay_byte_count>
|
RTP
bits rate transported by the RTP relay.
|
Columns
in the Memory Out of Pool Area
|
Name
|
Type
|
Db
Field
|
Description
|
|
TIME
|
time
|
status_time
|
Time
of event.
|
|
Rcv
Fifo
|
count
|
rxpkt_fifo
|
Height
of SIP receive FIFO.
|
|
Xmt
Fifo
|
count
|
txpkt_fifo
|
Height
of SIP transmit FIFO.
|
|
Out
of Pool Packet
|
count
|
pkt_oop
|
Number
of instantaneous active SIP packets.
|
|
Out
of Pool UAS Trans
|
count
|
uas_oop
|
Number
of instantaneous active UAS transactions.
|
|
Out
of Pool UAC Trans
|
count
|
uac_oop
|
Number
of instantaneous active UAC transactions.
|
|
Out
of Pool Call Leg
|
count
|
leg_oop
|
Number
of instantaneous active call legs.
|
|
Out
of Pool Media Process
|
count
|
mediaprocess_oop
|
Number
of instantaneous active media processes.
|
|
Out
of Pool Rate Request
|
count
|
raterequest_oop
|
Number
of instantaneous active rate requests.
|
|
Out
of Pool Rate Response
|
count
|
rateresponse_oop
|
Number
of instantaneous active rate responses.
|
Connection
Statistics
Connection
statistics show originate and terminate metrics for each of the SIP
peering connections provisioned in the system. To view connection
statistics:
The
Reseller field and Refresh
button at the bottom of the
page let you filter the statistics by reseller. There are also
buttons provided for:
-
Showing
hiding permission information about the connection
-
Showing/hiding
account information about the connection
-
Showing/hiding
registration information about the connection
-
Showing/hiding
policy information about the connection
A
Change button at the bottom-right side of the page
lets you
specify the start of the CDR window. If you click the Change
button, the button changes to a drop-down list and an Apply
button. You can then select the CDR window and click the Apply
button to have your selection take effect in the Connection
Statistics page.
Columns
in the Connection Statistics Page
|
Name
|
Description
|
|
Orig
CDR
|
Originate
CDR – Number of CDRs originated from this connection for the
configured time period.
|
|
Orig
% Ans
|
Originate
Percentage Answered – Percentage of originated calls answered on
this connection for the configured time period.
|
|
Orig
Avg (s)
|
Originate
Average, Seconds – Average seconds per originated call on this
connection for the configured time period.
|
|
Orig
Total (m)
|
Originate
Total, Minutes – Total originate minutes on this connection for
the configured time period
|
|
Term
CDR
|
Terminate
CDR – Number of CDRs terminated into this connection for the
configured time period.
|
|
Term
% Ans
|
Terminate
Percentage Answered – Percentage of calls terminated into this
connection for the configured time period.
|
|
Term
Avg (s)
|
Terminate
Average, Seconds – Average seconds per terminated call into this
connection for the configured time period.
|
|
Term
Total (m)
|
Terminate
Total, Minutes – Total terminate minutes on this connection for
the configured time period.
|
Domain Statistics
Domain
statistics show information about each domain in the system. To view
domain statistics:
-
On
the Diagnostics menu, point to Statistics
and click
Domain Statistics. This screen begins by showing
configuration information about each domain (essentially the same
information from the Domain configuration page). For each Domain,
the statistics in are then shown.
The
Reseller field and Refresh
button at the bottom of the
page let you filter the statistics by reseller.
A
Change button at the bottom-right side of the page
lets you
specify the start of the CDR window. If you click the Change
button, the button changes to a drop-down list and an Apply
button. You can then select the CDR window and click the Apply
button to have your selection take effect in the Connection
Statistics page.
|
Name
|
Description
|
|
#
User
|
Number
of users configured in this domain.
|
|
#
Device
|
Number
of devices configured in this domain.
|
|
#
Reg
|
Number
of devices registered in this domain.
|
|
#
CDR
|
Number
of CDRs for this domain during the configured period.
|
|
#
Ans
|
Number
of call answered for this domain during the configured period.
|
|
%
Ans
|
Percent
answered for this domain during the configured period.
|
|
Avg
(s)
|
Average
seconds per call for this domain during the configured period.
|
|
Total
Min
|
Total
minutes for this domain during the configured period.
|
|
Data
(MByte)
|
Total
space occupied by this domain.
|
|
#
Greeting File
|
Number
of greeting files for this domain’s auto attendant.
|
|
#
Music File
|
Number
of music files for the domain Music-On-Hold.
|
|
#
Word File
|
Number
of word files for this domain’s IVR.
|
Displaying
System
Information
Using
System Information in the Diagnostics
menu, you can
view meaningful information about the system’s base configuration
and health. The information displayed is divided into the following
sections:
-
System
-
HA
(High-Availability
-
Data
-
Database
A
Refresh button at the bottom of the dialog box lets
you update
the information shown in this page.
Sections
in the System Information Page
|
Name
|
Description
|
|
System
Section
|
|
System
Name
|
Configured
system name.
|
|
IP
and MAC address
|
Actual
IP and MAC addresses of the system.
|
|
Application
address
|
IP
and UDP of the application (floating address on HA system).
|
|
Running
time
|
System
uptime.
|
|
Last
update
|
Elapsed
time since the Real-Time code has updated its status in the System
Status page.
|
|
HA
Section
|
|
Resource
Group
|
Name
of HA resource group.
|
|
HA
Host (1-4)
|
Names
of HA hosts and whether they are active or standby.
|
|
HA
Management
|
Whether
or not HA management is currently on or off.
|
|
Data
Section
|
|
System
disk
|
Free
disk space/total disk space.
|
|
User
data
|
Space
used for user data.
|
|
Recordings
|
Space
used for recordings.
|
|
Database
Section
|
|
Database
uptime
|
Time
since last database restart.
|
|
Database
data receive rate
|
Rate
at which data is received by the database.
|
|
Database
data transmit rate
|
Rate
at which data is transmitted by the database.
|
|
Database
maximum used connections
|
Max
number of simultaneous database connections used since last
database restart.
|
|
Database
threads connected
|
Number
of database threads currently connected.
|
Displaying the
Audit Log
Using
the Audit Log command in the Diagnostics
menu, you can
view a trail of activities relevant for auditing configuration
changes. The audit log's main objective is to record all system adds,
updates, and deletions. User and Object
fields and a
Refresh button at the top of the page let you filter
the
information shown by system user and configuration object.
Viewing Events
Using
the Event page in the Diagnostics menu,
you can view
all system events. This is essentially the same page described in
section , except that this screen lets you access all system events
stored on the platform, rather than just the events for a particular
call. Using the check boxes, you can choose the event categories you
want to see.
The
main event traces that a system administrator needs are:
-
Responder
– Use the responder events to trace individual calls through the
platform. These traces are from an application perspective and show
the call as it traverses connections, dial translations, dial
policies, call routing, and ultimately the application. Here you can
also view the various translations that occur to the SIP URIs.
When
tracing individual calls, it usually is easier to access the
traces from the Call History page, where the filters are pre-set
for you when you click on the individual CDR in which you are
interested.
|
-
Info
– This is the SIP info event trace which shows all of the SIP
messaging in and out of the platform. By default, this tracing is
disabled as it can be a significant resource hog on a busy platform.
For more information and assistance with enabling this feature,
please contact NetSapiens support.
-
Media
– Media event tracing lets you view the system interactions with
the IVR media files. This is particularly useful when trying to
debug problems related to greetings or other system prompts.
-
All
– View all of the event traces.
Fields
are provided for entering an offset, start time, and end time, and
time margin (in seconds) shows an example of the Events page.
|
Name
|
Description
|
|
Offset
|
Number
of records to jump forward based on the index numbers. Index
numbers may not always appear contiguous. Every system event has
an index number based upon chronological order of the events. The
index numbers shown reflect those of the events you have chosen to
display.
|
|
Start
and End Time
|
Allow
you to specify the event window. Format is yyyy-mm-dd hh:mm:ss.
|
|
Margin
|
Useful
when you want to add time to the start and end of a trace window.
This is primarily used when accessing the traces from the Call
History page. In the Call History page, tracing is based on both
call ID and time window. It is worthwhile to know what was
occurring immediately before or after the call you are tracing.
|
When
event information is displayed, you can use the Filter
field
and Refresh button at the top of the page to filter
out
extraneous information and see only the data that is meaningful to
you. There is also a Call-ID check box that lets
you view or
hide Originate Call ID information in the traces.
For
more information, see section .
Using Ping and
Trace
Route Capabilities
Using
the Ping command in the Diagnostics
menu, you can test
a connection to a networked device by pinging the device’s target
name or IP address. The system’s ping command helps to verify
IP-level connectivity. With this capability, you use ping to send an
ICMP echo request to a target host name or IP address. Use ping
whenever you need to verify the status of a network device (that is,
whether or not the device is “alive”).
The
system also provides a trace route capability, where Trace Route
records the route followed in the network between the sender’s
computer and a specific destination computer.
To
use the system’s ping and trace route capabilities:
- In the Target field, enter the name or the IP address of
the device you want to ping or trace route.
- Click the Ping button to ping the device or click Trace
Route to trace the route to the device.
Performing System
Operations
