Jump to: navigation, search

HTTP Monitoring Interface

Starting with version 8.1.102.13, SIP Server provides the ability to monitor various operational statistics for its internal modules and statistics relating to trunks.

Starting with version 8.1.103.25, SIP Server adds the ability to monitor statistics related to SIP Feature Server interactions.

Starting with version 8.1.103.35, SIP Server adds the ability to monitor statistics related to Extended Services (XS) components.

This section covers the following topics:

SIP Server Statistics

SIP Server collects statistics for the following internal modules:

Trunk Statistics

SIP Server collects the following statistics (sipTrunkStatistics) for each configured Trunk DN:

  • Current statistics (real-time)
    • Number of calls currently established via this trunk (sum of incoming and outgoing calls)
    • Current call rate (average number of calls per second, both incoming and outgoing). Averaging interval is specified by the Application-level option operational-stat-timeout (in seconds, default value is 10 seconds).
    • Capacity (maximum number of calls allowed on a trunk, both incoming and outgoing)
    • Capacity group (to which a trunk belongs)
    • In Service status
  • Summary statistics (over a period of time, such as an hour or a day)
    • Peak number of calls
    • Peak call rate
    • Call attempts (total number of new calls)
    • Total number of released calls
    • Summary period start time
    • Summary period end time

SIP Server collects the following statistics (sipTrunkStatistics) for each configured Capacity Group:

  • Current statistics
    • Current number of calls (combined number for all the trunks in a group)
    • Current call rate (combined rate for all the trunks in a group)
    • Capacity
  • Summary statistics
    • Peak number of calls
    • Peak call rate
    • Call attempts
    • Total number of released calls
    • Summary period start time
    • Summary period end time

The period of summary statistics calculation is configurable with the Application-level option summary-stat-timeout.

How to Monitor Statistics

There are two possible ways to monitor the collected statistics:

  • Using the HTTP interface
  • Using the dedicated SIP Server log file

Monitoring Statistics via HTTP interface

To enable the HTTP interface, set the http-port option to a valid and unoccupied port number in the range of 1024-65535 (values lower than 1024 are system reserved ports). Only the HTTP interface is available on the configured port (HTTPS is not available).

To get the statistics data, the following URL must be retrieved with the HTTP GET request:
http://<SIP Server IP address>:<configured HTTP port> (for example, http://192.168.0.1:8088)

Depending on the path used in the URL, the statistics page can be provided in the HTML or XML format:

  • To get the statistics in the HTML format, use an empty path ("" or "/") or path /server.
    For example: http://192.168.0.1:8088 or http://192.168.0.1:8088/server.
    The above URL returns a root statistics page with the list of statistics for SIP Server internal modules, with each list item being a link to the statistic data for that module.
  • To get the statistics in the XML format, use path /serverx.
    For example: http://192.168.0.1:8088/serverx.
    The above URL returns a root statistics page with the full statistics dump, including data for each SIP Server internal module.

To get the statistics page for one module, add the URL parameter with the module name. For example, to get the Trunk Statistics page in the HTML format, the following URL must be used: http://192.168.0.1:8088/server?sipTrunkStatistics.

Trunk Statistics Examples

  • In the HTML format:
[+] Show HTML source

The code above displays these results in a browser:

Trunk Statistics in HTML Format


  • This XML-format code displays the same results:
[+] Show XML source

Monitoring Statistics via Log File

SIP Server always creates a dedicated log file for a statistics output despite of the values set in the log options. The name of the file contains suffix 1536 (for example, server1-1536.20160201_195851_685.log).

Statistics are written to the log file periodically, with a period specified by the Application-level option operational-stat-timeout (default value is 10 seconds).

Statistics log format

A statistics log file uses the following line format for statistics output:

<Timestamp in ISO 8601 format> <Statistics module name> <Parameter>=<Value> [<Parameter>=<Value>]

For example, for the Call Manager module, the output for the "Number of devices" statistics is as follows:

2016-01-01T12:00:01.001 sipCallManager NDEVICES=150

For more sophisticated Trunk statistics, the output is as follows:

2016-01-01T12:00:01.001 sipTrunkStatistics TRUNK=21001 CURRENT_CALLS=100 CURRENT_CALL_RATE=15 PEAK_CALLS=150 PEAK_CALL_RATE=20 CALL_ATTEMPTS=5000 RELEASED_CALLS=4900 SUMMARY_START=2016-01-01T12:00:01 SUMMARY_END=2016-01-01T13:00:01 CAPACITY=500 CAPACITY_GROUP=MyTrunks IN_SERVICE=Yes

Configuration Options

http-port

Section: [TServer]
Default Value: 0
Valid Values: 0, 1024-65535
Changes Take Effect: After SIP Server restart

Specifies the HTTP interface port number. When set to 0, the HTTP server is disabled. The port numbers in the range of 1 through 1023 are the system ports and must not be used.

operational-stat-timeout

Section: [TServer]
Default Value: 10
Valid Values: 3-65535
Changes Take Effect: After SIP Server restart

Specifies how often, in seconds, a local LCA is queried for system information such as CPU and memory usage. This information is then written into the SIP Server Operational Information log as defined in the SIP Server configuration.

summary-stat-timeout

Section: [TServer]
Default Value: 60
Valid Values: Integer value 1-65535
Changes Take Effect: After SIP Server restart

Specifies how often, in minutes, the summary statistics are calculated.

Statistics Details

Each SIP Server internal module has its own statistics section. Each section has the identifier that is used in the log and XML output to distinguish one section from another. This identifier is also used as a URL parameter if a user wishes to get an HTML/XML page with only one statistics section.

The statistics for each SIP Server module is described below. Each statistic record is described in a table that has the following columns:

  • ID—The ID that is used in the log and XML output.
  • Description—The general description of the statistic record. It is also used in the HTML output.
  • Comments—Additional information if the description of the record is not self-explanatory.

General SIP Server Statistics

Section ID: sipServer

ID

Description

Comments

SIPS_PROCESS_ID

Process identifier

Identifier that is assigned by an Operating System to a SIP Server process

SIPS_MEMORY_USAGE

Memory usage

In bytes

SIPS_CPU_USAGE

CPU usage

In percent

PROCESS_INFO_TIME

Process info time

Time range on which statistics are gathered

NAME

Name

Name of the SIP Server Application in the Configuration Layer

BIT

Bit data model

32 or 64 bit

PLATFORM

Platform

 

SERVER_VERSION

Server version

 

COMPILED_DATE

Compiled date

 

XS_CPU_USAGE CPU usage Extended Service CPU usage on a singe CPU core. Applies only to SIP Cluster deployments starting with SIP Server release 8.1.103.29.
XS_REQUESTS_RATE Requests rate Rate of requests processed by the Extended Services component. Applies only to SIP Cluster deployments starting with SIP Server release 8.1.103.29.

SIP Stack Statistics

Section ID: sipStackObjects

ID Description Comments
DIALOG_CREATED SIP Dialogs created
DIALOG_DELETED SIP Dialogs deleted
MESSAGES_CREATED SIP Messages created
MESSAGES_DELETED SIP Messages deleted
CLIENT_TRANSACTION_CREATED SIP Client transactions created
CLIENT_TRANSACTION_DELETED SIP Client transactions deleted
SERVER_TRANSACTION_CREATED SIP Server transactions created
SERVER_TRANSACTION_DELETED SIP Server transactions deleted
TRANSPORT_CREATED Transports created
TRANSPORT_DELETED Transports deleted
DATASENT Data sent In bytes. If a value is not increased, it might be used as indication of the backup mode of SIP Server.
DATARECEIVED Data received In bytes. If a value is not increased, it might be used as indication of the backup mode of SIP Server.
RESPONSE_TIME_LESS20 Response time less than 20 ms Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_20TO50 Response time 20 to 50 ms Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_50TO100 Response time 50 to 100 ms Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_100TO200 Response time 100 to 200 ms Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_200TO500 Response time 200 to 500 ms Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_500TO1SEC Response time 500 ms to 1 sec Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_1TO5SEC Response time 1 to 5 sec Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_5TO10SEC Response time 5 to 10 sec Response time to SIP messages sent by SIP Server.
RESPONSE_TIME_MORE10SEC Response time more than 10 sec Significant increase of the value might indicate network problems or a SIP Server overload condition.

Call and Client Statistics

Section ID: sipCallManager

ID

Description

Comments

CM_THREAD_ID

Thread ID

CM_CPU_USAGE

CPU usage of call manager thread

In percent.

NCALLSCREATED

Number of calls created

 

NDIALOGS

Number of dialogs

Current active SIP dialogs.

NCALLS

Number of calls

Current active calls.

NPARTIES

Number of parties

Current active parties. If the number of calls is zero, a nonzero value of the number of parties might indicate a leak of resources which might lead to an abnormal behavior of SIP Server.

HADATASENT

HA sync data sent

In bytes.

HADATARECEIVED

HA sync data received

In bytes.

NROUTINGTIMEOUTS

Number of routing timeouts

Increases when the routing timer expires (specified by the option router-timeout). Significant increase of the value might indicate issues in the routing strategies or router overload.

NLOGGEDAGENTS

Number of logged on agents

 

NREGISTEREDDNS

Number of registered DNs

Number of registered DNs by using a TRegisterAddress request.

NTLIBCLIENTS

Number of T-Library clients

Number of T-Library clients currently connected to SIP Server.

NCALLSABANDONED

Number of abandoned calls

Number of calls released by a caller before the call was answered.

NCALLRECORDINGFAILED

Number of failed call recording sessions

Significant increase of the value might indicate problems with the recording services.

NSIPREGISTEREDEP

Number of active SIP registrations

 

NSIPEXPIREDREGS

Number of expired SIP registrations

Number of SIP registrations that were expired since SIP Server startup. Significant increase of the value might indicate problems with the network.

NCALLSOVRLREJECTED

Number of rejected calls due to overload control

Related to the static overload control feature.

NMSMLLOCATIONFAILED

Number of MSML location resolution failed

Significant increase of the value might indicate problems with configuration of geo-location of MSML services.

ISCC Statistics

Section ID: sipTSCP

ID

Description

Comments

ISCC_ACTIVE_ORIG_TRANSACTIONS

ISCC active orig transactions

 

ISCC_ACTIVE_DEST_TRANSACTIONS

ISCC active destination transactions

 

ISCC_SUCCEEDED_ORIG_TRANSACTIONS

ISCC succeeded origination transactions

 

ISCC_SUCCEEDED_DEST_TRANSACTIONS

ISCC succeeded destination transactions

 

ISCC_FAILED_ORIG_TRANSACTIONS

ISCC failed origination transactions

Significant increase of the value might indicate issues in the communication between sites in a multisite environment.

ISCC_FAILED_DEST_TRANSACTIONS

ISCC failed destination transactions

Significant increase of the value might indicate issues in the communication between sites in a multisite environment.

T-Library Statistics

Section ID: sipSessionController

ID

Description

Comments

MAIN_THREAD_ID

Thread ID

 

MAIN_CPU_USAGE

CPU usage

In percent.

NAPPLY_TREATMENTS

Number of Apply Treatments

Number of processed TApplyTreatment requests.

URS_RESPONSE_LESS50

URS Response less than 50 ms

URS response time means the time passed between the moment the call is queued on a Routing Point (indicated by EventQueued) and the moment the call is routed to a destination, including the default destination in case of URS failure/timeout (indicated by EventRouteUsed). Long response times might indicate problems with the network or URS overload. Response times corresponding to the router-timeout option value most likely indicate a URS failure/timeout (e.g. as a result of incorrect routing strategy).

URS_RESPONSE_50TO100

URS Response 50 to 100 ms

 

URS_RESPONSE_100TO200

URS Response 100 to 200 ms

 

URS_RESPONSE_200TO500

URS Response 200 to 500 ms

 

URS_RESPONSE_500TO1SEC

URS Response 500 ms to 1sec

 

URS_RESPONSE_1TO5SEC

URS Response 1 to 5 sec

 

URS_RESPONSE_MORE5SEC

URS Response more than 5 sec

NUSER_DATA_UPDATES

Number of User Data updates

Number of processed requests related to UserData (TAttachUserData, TUpdateUserData, TDeletePair, TDeleteUserData).

NTREQUESTS

Number of T-Requests

Number of all processed T-Library requests (of any type).

Out-Of-Service Detection Statistics

Section ID: sipServiceChecker

ID

Description

Comments

SRVC_THREAD_ID

Thread ID

 

SRVC_CPU_USAGE

CPU usage

 

SRVC_NOOS_DEVICES

Number Out Of Service devices

Significant increase of the value might indicate problems with the network

SIP Feature Server Statistics

SIP Server collects the following statistics related to SIP Feature Server (sipFeatureServer) interactions:

ID Description
FS_STATE Current service state. Values: 0 is out of service, 1 is in service.
FS_QUEUE_SIZE Current number of XS requests in a queue (requests that have not been sent to Feature Server).
FS_AVERAGE_QUEUE_TIME Average request in queue time in milliseconds during the period of statistic's summary.
FS_CONNECTIONS Number of connections for each URL.
Statistics for each configured URL
FS_URL URL of Feature Server.
FS_ACTIVE_CONNECTIONS Current number of active connections.
FS_REQUEST_RATE Requests rate during the period of statistic's summary (request/sec).
FS_TIMEOUTS Number of timeouts for requests (sent or in queue) during the period of statistic's summary.
FS_400_ERRORS Number of 400 error responses during the period of statistic's summary.
FS_404_ERRORS Number of 404 error responses during the period of statistic's summary.
FS_4XX_ERRORS Number of 4xx error responses during the period of statistic's summary.
FS_500_ERRORS Number of 500 error responses during the period of statistic's summary.
FS_501_ERRORS Number of 501 error responses during the period of statistic's summary.
FS_5XX_ERRORS Number of 5xx error responses during the period of statistic's summary.
FS_AVERAGE_RESPONSE_LATENCY Average response latency during the period of statistic's summary (in milliseconds).

SIP Feature Server Statistics Examples

  • In the HTML format:
[+] Show HTML source

The code above displays these results in a browser:

Sips-httpmonitor-fs.png
  • The URL-related statistic in the HTML format:
[+] Show HTML source

The code above displays these results in a browser:

Sips-httpmonitor-fs-url.png
  • The URL-related statistic in the XML format:
[+] Show XML source

Feature Limitations

The CSS style for the HTML statistics page is hardcoded.

This page was last modified on February 5, 2019, at 13:11.

Feedback

Comment on this article:

blog comments powered by Disqus