Professional Documents
Culture Documents
3v01
Table of Contents
1 Service Configurations
This section contains the best practices for configuring nG1 for Voice environments and use cases.
The power of NG1 is that service monitors are launched with the context of the service definition and
behave accordingly. For example, when the media monitor is launched with a multi-hop service the
Voice analytics will be done for each hop defined in the service.
• A single-hop service allows users to perform analysis on a specific interface such as S1U.
Regional vs local end to end service differentiation may be needed in case of operators serving
large geographical areas or large number of tapping points to preserve efficiency and speed while
still providing end-to-end visibility to the user. A local end to end service definition will provide end
to end visibility within a single location (city, area, market, …) whereas a regional or national service
definition will provide end to end visibility across multiple locations ( e.g. end to end visibility for
calls made between New York and Los Angeles)
A regional service definition will require feeds from multiple locations be included in the service (e.g. S1-
U feeds (Monitored Elements) from New York SGWs plus S1-U feeds from Los Angeles SGWs, etc). For
large operators with 10s of millions of subscribers and serving large geographic areas, this may mean a
lot of monitored elements within a single service definition, which in turn means nG1 engine will search
through all the monitored elements included in the service definition which will increase response
times.
In such cases, as a best practice, local end to end services can be created for each location. Local service
definitions will include monitored elements only from that location, hence reducing the number of
monitored elements nG1 engine needs to search through. Each local end to end service will provide
visibility to the side of the calls that fall into the given location. So to get regional end to end visibility,
users will need a 2 step process which will use 2 local service definitions, one for each side of the intra
location calls:
1st step: Analyze originating side using local service definition corresponding to originating side of the
call. If the problem is found in the originating side (isolated to originating side), then troubleshoot the
problem on the originating side
2nd Step: If the problem is not on the originating side, or cannot be isolated to the originating side,
determine the local service definition corresponding to the terminating side. The terminating location
can be identified from the media stream, i.e. by destination MGW/MRFP, IP address pool of the
terminating end user, or destination SBC/TrGW.
Once terminating side service definition is determined, use this service definition to do the
troubleshooting (monitoring KPIs, session analysis, streams analysis, …)
(e.g. to track the media for a call from New York to Los Angeles, the user can use New York end to end
service to analyze the originating side of the call, then use Los Angeles service definition to analyze the
terminating side of the call, hence getting full end to end visibility, but with improved efficiency and
responsiveness
Naming Conventions:
It is important to establish a service naming convention that uniquely identifies each service and is
meaningful to the end users.
For example, in the U.S. service providers routinely use CLLI codes to
represent a location (“BTSNMA” CLLI code represents Boston, MA)
E2E We recommend that all multi-hop services contain the “E2E” prefix (meaning
end-to-end) in the service name so that it is obvious when selecting services
for multi-hop Voice analytics.
<3GPP/NGN S1U, S5, SGi, …
Interface>
The following table contains the Services that are used in the Voice Best Practices Dashboard Over Time
Views (see next section for Dashboard settings).
<location> - E2E Adv Voice This service is used to launch Service Definition:
Statistics the Advanced Voice Statistics SIP, SIP-TCP, RTCP, RTP, Audio,
monitor to view key Voice SIP Video
Call Control signaling KPIs S1u, S5, SGi, IMS interfaces
Default Monitor:
Advanced Voice Statistics
<location> - E2E Media Quality This service is used to Service Definition:
troubleshoot voice quality SIP, SIP-TCP, RTCP, RTP, Audio,
issues using the Media Monitor Video
S1u, S5, Mb, Izi
Default Monitor:
Media Monitor
<location> - E2E Registration SIP Registration Service Definition:
SIP: Register, RE- Register, DE-
Register
SIP_TCP: Register, RE- Register,
DE-Register
S1u, S5, SGi, Mw, ISC, NGN
Default Monitor:
Universal Monitor
<location> - E2E Call Setup SIP Call Setup Service Definition:
SIP: Call Setup
SIP_TCP: Call Setup
S1u, S5, SGi, IMS, NGN
interfaces
Default Monitor:
Universal Monitor
<location> - E2E Call Teardown SIP Call Teardown Service Definition:
SIP: Call Teardown
SIP_TCP: Call Teardown
S1u, S5, SGi, IMS, NGN
interfaces
Default Monitor:
Universal Monitor
Within each local Market, split by Call Model and Device View
Signaling and Media views for all phases of the VoLTE call from eUTRAN to IMS Edge
Figure 1: Call Model Over Time View – EPC Registration at S1U, Gm/SGi, and Mw
1.2.2.1. Registration
Dashboard Settings
VoLTE/EPC/North_EPC/BOSMAUS/Call_Model/Registration
VoLTE/EPC/North_EPC/BOSMAUS/Call_Model/Call_Setup
Service Configuration
VoLTE/EPC/North_EPC/BOSMAUS/Call_Model/Call_Teardown
1.2.2.4. Media
Dashboard Settings
VoLTE/EPC/North_EPC/BOSMAUS/Call_Model/Media
Service Configuration
VoLTE/EPC/North_EPC/BOSMAUS/Call_Model/
Advanced_Voice_Statistics
View Type Service Service Member
Service Configuration
Dashboard Settings
Service Configurations
• EPC_S1-MME_Attach:
o EMM:EMM-ATTACH, EMM:EMM-DETACH
o A Network Domain which includes all S1-MME Monitored Elements in the market or
region using the Interface Type s1.
• EPC_S1-MME_Mobility:
o Diameter-SCTP: UpdateLoc, EMM:S1_CSFB_HO, EMM:S1_INTRA_LTE_X2_HO,
EMM:S1_INTRA_LTE_S1_HO, EMM:S1_LTE_2_UTRAN_HO, EMM:S1-LTE_2_GERAN_HO
o A Network Domain which includes all S1-MME Monitored Elements in the market or
region using the Interface Type s1.
• EPC_S1-MME_Paging:
o EMM:S1_PAGING_CS, EMM:S1_PAGING_PS, SGsAP:SGsAP-Paging
o A Network Domain which includes all S1-MME Monitored Elements in the market or
region using the Interface Type s1.
• EPC_S1-MME_RAB_Procedures:
o S1-AP:S1-AP-E-RAB-MOD, S1-AP:S1-AP-E-RAB-REL, S1-AP:S1-AP-E-RAB-SET,
X2AP:X2AP_E_RAB_ADMISS
o A Network Domain which includes all S1-MME Monitored Elements in the market or
region using the Interface Type s1.
• EPC_S1-MME_Service_Request:
o EMM:EMM-SERVICE, EMM:EMM_CSSERICENTIF, EMM:EMM_EXT_SERVICE
o A Network Domain which includes all S1-MME Monitored Elements in the market or
region using the Interface Type s1.
• EPC_S11_Bearer_Control:
o ESM:ESM-ACT-DED-BEAR, ESM:ESM-ACT-DEF-BEAR, ESM:ESM-BEAR-RES_ALLOC,
ESM:ESM-BEAR-RES_MOD, ESM:ESM-DEACT-BEAR-CTXT, EMS:ESM-MOD-BEAR-CTXT,
GTP_V2C:V2_Bearer_Res_Cmd, GTP_V2C:V2_Create_Bearer,
GTP_V2C:V2_Delete_Bearer, , GTP_V2C:V2_Delete_Bearer_Cmd,
GTP_V2C:V2_Modify_Bearer, GTP_V2C:V2_Modify_bearer_cmd,
GTP_V2C:V2_Rel_Access_Bear, GTP_V2C:V2_Update_Bearer, V2_Bear_Res_Cmd_Fail,
V2_Del_Bear_Cmd_Fail, V2_Dwnlnk_Data_Failure, V2_Mod_Bear_Cmd_Fail
o All S1-MME and S11/S1-U Monitored Elements in the market or region.
• EPC_ S1-MME_UE-Context
o S1-AP:S1-AP-UE-CTX-MOD , S1-AP:S1-AP-UE-CTX-REL, S1-AP:S1-AP-UE-CTX-SET
o A Network Domain which includes all S1-MME Monitored Elements in the market or
region.
• EPC_Session-Bearer
o GTP_V0:V0_Create_PDP, GTP_V0:V0_Update_PDP, MIPV6:PMIPv6_INIT_ATTACH,
MIPV6:PMIPv6_RE_REG, MOBILE IP:MIP_Registration, MOBILE IP:MIP_ReRegistration
o A Network Domain which includes all S11/S1-U Monitored Elements in the market or
region.
Hierarchy of VoLTE-critical devices in the EPC from eUTRAN to the IMS edge (P-CSCF/AGW), within each
Market…
1.2.3.1. MME
Dashboard Settings
VoLTE/EPC/North_EPC/BOSMAUS/Device_View/MME
Service Configuration
Monitor: Universal
Members: Service Template message types for the S1-MME and S11 Interfaces, and Network Services
with Interfaces to the MME.
1.2.3.2. S/P-GW
Dashboard Settings
VoLTE/EPC/North_EPC/BOSMAUS/Device_View/SP-GW
Service Configuration
1.2.3.3. HSS
Dashboard Settings
VoLTE/EPC/North_EPC/BOSMAUS/Device_View/HSS
Service Configuration
Monitor: Diameter
Service Members: Use the S6a Service Template – all message types
1.2.3.4. PCRF
Dashboard Settings
VoLTE/EPC/North_EPC/BOSMAUS/Device_View/PCRF
Service Configuration
1.2.4.1. Registration
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Call_Model/Registration
Service Configuration
Monitor: Universal
Service Names: BOSMAUS_IMS_Gm-SGi_Registration, BOSMAUS_IMS_Mw_Registration, and
BOSMAUS_IMS_ISC_Registration
Members: Use SIP registration service template for message types (also see sec 1.2.2.1).
ME Feeds can use VLAN or IP Addr location keys to classify Gm-SGi, Mw, and ISC traffic.
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Call_Model/Call_Setup
Service Configuration
Monitor: Universal
Service Names: BOSMAUS_IMS_Gm-SGi_Call_Setup, BOSMAUS_IMS_Mw_Call_Setup, and
BOSMAUS_IMS_ISC_Call_Setup
Members: Use SIP and SIP_TCP Setup message types (also see sec 1.2.2.2).
ME Feeds can use VLAN or IP Addr location keys to classify Gm-SGi, Mw, and ISC traffic.
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Call_Model/Call_Teardown
Service Configuration
Monitor: Universal
Service Names: BOSMAUS_IMS_Gm-SGi_Call_Teardown, BOSMAUS_IMS_Mw_Call_Teardown, and
BOSMAUS_IMS_ISC_Call_Teardown
Members: Use SIP and SIP_TCP Teardown message types (also see sec 1.2.2.3).
ME Feeds can use VLAN or IP Addr location keys to classify Gm-SGi, Mw, and ISC traffic.
1.2.4.4. Media
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Call_Model/Media
Service Configuration
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Call_Model/Advanced_Voice
_Statistics
View Type Service Service Member
Service Configuration
1.2.5.1. P-CSCF/AGW
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Device_View/P-CSCF_AGW
Service Configuration
Monitor: Universal
Service Members: BOSMAUS_IMS_Gm-SGi_Signaling, and BOSMAUS_IMS_Mw-Mb_Signaling includes
SIP, and SIP_TCP Parent Application
Monitor: Media
Service Members: BOSMAUS_IMS_Mb-SGi_Media includes SIP, SIP_TCP, RTP, RTCP, Audio, using Media
Monitor
1.2.5.2. S-CSCF
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Device_View/S-CSCF
Service Configuration
Monitor: Universal
Monitor: Advanced Voice Statistics
Service Names: BOSMAUS_IMS_Mw_Signaling
Members: Use SIP and SIP_TCP Parent Applications
ME Feeds can use VLAN or IP Addr location keys to classify Mw traffic.
1.2.5.3. TAS
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Device_View/TAS
Service Configuration
Monitor: Universal
Monitor: Advanced Voice Statistics
Service Names: BOSMAUS_IMS_ISC_Signaling
Members: Use SIP and SIP_TCP Parent Applications
ME Feeds can use VLAN or IP Addr location keys to classify ISC traffic.
1.2.5.4. MRF
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Device_View/MRF
Service Configuration
Monitor: Universal
Monitor: Advanced Voice Statistics
Service Names: BOSMAUS_IMS_Mr_Signaling
Members: Use SIP and SIP_TCP Parent Applications
ME Feeds can use VLAN or IP Addr location keys to classify Mr traffic.
1.2.5.5. HSS
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Device_View/HSS
Service Configuration
Monitor: Diameter
Service Names: BOSMAUS_IMS_Cx
Members: Use Diameter and Diameter_SCTP Parent Applications
ME Feeds can use VLAN or IP Addr location keys to classify Mw traffic.
1.2.5.6. MGCF
Dashboard Settings
VoLTE/IMS/North_IMS/BOSMAUS/Device_View/MGCF
Service Configuration
Monitor: Universal
Monitor: Advanced Voice Statistics
Service Names: BOSMAUS_IMS_Mg-Mj
Members: Use SIP and SIP_TCP Parent Applications
ME Feeds can use VLAN or IP Addr location keys to classify Mg and Mj traffic.
Below are the best practice Service Domain definitions for monitoring SRVCC. Recommendation is to
add a service container (SRVCC) under call model service tree and add the services shown below under
SRVCC service container. Moreover these services should be added to Interface model (S1-MME, Sv) and
Device Model (MME).
Default Monitor:
Universal
location> - S1-MME SRVCC This service is used to Service Definition:
CS-PS launch the Universal S1AP:
monitor to view key S1_LTE_2_GERAN_SRVCC_HO_PS_CS
SRVCC signaling KPIs S1_LTE_2_UTRAN_SRVCC_HO_PS_CS
for CS-PS handovers
S1-MME interface
Default Monitor:
Universal
Default Monitor:
Universal
<location> - Sv SRVCC This service is used to Service Definition:
launch the Universal GTP_V2C:
monitor to view key SRVCC_PS_CS_REQ
SRVCC signaling KPIs SRVCC_PS_CS_CMPLT
on Sv interface SRVCC_PS_CS_CANCEL
Sv interface
Default Monitor:
Universal
Below are the best practice Service definitions for monitoring RCS. Recommendation is to add a new
service container at the top level (RCS) and add the services shown below under RCS service container.
These services can also be created separately for different locations in case of distributed IMS
architecture.
Since RCS runs over IMS, and uses SIP signaling, recommended point to monitor RCS service health is ISC
and or Mw interface. If there are more than 1 P-CSCF nodes in the network, monitoring at Mw interface
will give per P-CSCF performance visibility.
<location> - ISC RCS Video Call This service is used to launch Service Definition:
Universal monitor to view key SIP RCS VIDEO CALL
RCS Video Call service KPIs on SIP-TCP RCS VIDEO CALL
ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS IMAGE <location> - ISC RCS IMAGE Service Definition:
SHARE SHARE This service is used to SIP RCS IMAGE SHARE
launch Universal monitor to
view key RCS Image share ISC interface
service KPIs on ISC interface
Default Monitor:
Universal
<location> - ISC RCS CHAT This service is used to launch Service Definition:
Universal monitor to view key SIP RCS CHAT
RCS Chat service KPIs on ISC SIP-TCP RCS CHAT
interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS FILE This service is used to launch Service Definition:
TRANSFER Universal monitor to view key SIP RCS FILE TRANSFER
RCS File Transfer service KPIs SIP-TCP RCS FILE TRANSFER
on ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS MESSAGE This service is used to launch Service Definition:
Universal monitor to view key SIP RCS MESSAGE
RCS Messaging service KPIs on SIP-TCP RCS MESSAGE
ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS PRESENCE This service is used to launch Service Definition:
Universal monitor to view key SIP RCS PRESENCE
Default Monitor:
Universal
<location> - ISC RCS VIDEO This service is used to launch Service Definition:
SHARE Universal monitor to view key SIP RCS VIDEO SHARE
RCS Video Sharing service KPIs SIP-TCP RCS VIDEO SHARE
on ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS VOICE This service is used to launch Service Definition:
CALL Universal monitor to view key SIP RCS VOICE CALL
RCS Voice Call service KPIs on SIP-TCP RCS VOICE CALL
ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS VOICE This service is used to launch Service Definition:
SHARE Universal monitor to view key SIP RCS VOICE SHARE
RCS Voice Sharing service KPIs SIP-TCP RCS VOICE SHARE
on ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS VOLTE This service is used to launch Service Definition:
VIDEO CALL Universal monitor to view key SIP RCS VOLTE VIDEO CALL
RCS VoLTE Voice Call service SIP-TCP RCS VOLTE VIDEO CALL
KPIs on ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC RCS VOLTE This service is used to launch Service Definition:
VOICE CALL Universal monitor to view key SIP RCS VOLTE VOICE CALL
RCS VoLTE Voice Call service SIP-TCP RCS VOLTE VOICE CALL
KPIs on ISC interface
ISC interface
Default Monitor:
Universal
<location> - ISC MSRP This service is used to launch Service Definition:
Universal monitor to view key MSRP:
MSRP signaling KPIs on ISC SEND
interface AUTH
NICKNAME
ISC interface
Default Monitor:
Universal
Successful/Failed Transactions ISC RCS Video Call Make no selection (implies all)
Successful/Failed Transactions ISC RCS IMAGE SHARE Make no selection (implies all)
Successful/Failed Transactions ISC RCS FILE TRANSFER Make no selection (implies all)
Successful/Failed Transactions ISC RCS VIDEO SHARE Make no selection (implies all)
Successful/Failed Transactions ISC RCS VOICE CALL Make no selection (implies all)
Successful/Failed Transactions ISC RCS VOICE SHARE Make no selection (implies all)
Successful/Failed Transactions ISC RCS VOLTE VIDEO CALL Make no selection (implies all)
Successful/Failed Transactions ISC RCS VOLTE VOICE CALL Make no selection (implies all)
Error Code Distribution ISC RCS Video Call Make no selection (implies all)
Error Code Distribution ISC RCS IMAGE SHARE Make no selection (implies all)
Error Code Distribution ISC RCS CHAT Make no selection (implies all)
Error Code Distribution ISC RCS FILE TRANSFER Make no selection (implies all)
Error Code Distribution ISC RCS MESSAGE Make no selection (implies all)
Error Code Distribution ISC RCS PRESENCE Make no selection (implies all)
Error Code Distribution ISC RCS VIDEO SHARE Make no selection (implies all)
Error Code Distribution ISC RCS VOICE CALL Make no selection (implies all)
Error Code Distribution ISC RCS VOICE SHARE Make no selection (implies all)
Error Code Distribution ISC RCS VOLTE VIDEO CALL Make no selection (implies all)
Error Code Distribution ISC RCS VOLTE VOICE CALL Make no selection (implies all)
Average Response Time ISC RCS Video Call Make no selection (implies all)
Average Response Time ISC RCS IMAGE SHARE Make no selection (implies all)
Average Response Time ISC RCS CHAT Make no selection (implies all)
Average Response Time ISC RCS FILE TRANSFER Make no selection (implies all)
Average Response Time ISC RCS MESSAGE Make no selection (implies all)
Average Response Time ISC RCS PRESENCE Make no selection (implies all)
Average Response Time ISC RCS VIDEO SHARE Make no selection (implies all)
Average Response Time ISC RCS VOICE CALL Make no selection (implies all)
Average Response Time ISC RCS VOICE SHARE Make no selection (implies all)
Average Response Time ISC RCS VOLTE VIDEO CALL Make no selection (implies all)
Average Response Time ISC RCS VOLTE VOICE CALL Make no selection (implies all)
The follow is an example of the Call Model view applied to 3G and 2G signaling.
3G Call Model
MSS interface
Default Monitor:
Universal
<location> - E2E IuCS MT CALL IuCS Mobile Terminated Call Service Definition:
Setup message dialog IuCS: MT Call Setup
MSS interface
Default Monitor:
Universal
<location> - E2E IuCS MO CALL IuCS Mobile Originating Call Service Definition:
Setup message dialog. IuCS: MO Call Setup
MSS interface
Default Monitor:
Universal
2G Call Model
MSS interface
Default Monitor:
Universal
<location> - E2E GSMA MT GSMA Mobile Terminated Call Service Definition:
CALL Setup message dialog. GSMA: MT Call Setup
MSS interface
Default Monitor:
Universal
<location> - E2E GSMA MO GSMA Mobile Originating Call Service Definition:
CALL Setup message dialog. GSMA: MO Call Setup
MSS interface
Default Monitor:
Universal
QoS groups allow operators to differentiate traffic by DSCP markings. This allows monitoring
applications running on different DSCP markings and isolate applications with wrong QoS assignments.
In VoLTE, at least 2 QoS levels are used, where one (or more) DiffServ codes is for signaling (LTE default
bearer QCI 5) and one (or more) DiffServ codes is for media (LTE dedicated bearer QCI 1).
The following worksheet can be used to define QoS 1 Groups. The first two columns can be used to
create an import file (See on-line help article, “Creating a File to Import Quality of Service Groups” and
“Importing Quality of Service Groups”. 2).
1 For a general discussion about the different kinds of QoS, please refer to
http://en.wikipedia.org/wiki/Type_of_service.
2 For additional guidance on configuring QoS Groups, please refer to NetScout’s on-line help in the following
articles: “Quality of Service Overview”, “Differentiated Service”, “Differentiated Service Code Points”, “QoS
Groups Data Collection and Monitoring in nGeniusONE”, “Enabling the Device to Monitor QoS”, “Adding Quality of
Service Groups”, “Modifying Quality of Service Groups”, “Deleting Quality of Service Groups”.
Note: Before creating QoS groups, get the DSCP markings for QCI-1 and QCI-5 that the customer is using
in their networks.
1.6. Dashboards
nGeniusONE Dashboards are used for real time trend visibility, early warning, and actionable alert
management in a NOC environment.
Dashboards show Service Assurance metrics in real time for millions of subscribers, with end-to-end
views and with customized views into specific markets, domains, or service areas.
Below are recommended best practice dashboard views for voice analytics.
Over Time Views show critical KPI trends for Best Practice scenarios such as Executive KPIs, the Call
Model, End-to-End Media Quality, and VoLTE 4G EPC KPIs.
Executive KPIs
Executive KPIs dashboard view provide a summary for signaling and media health for voice service. This
view is designed for executives to monitor the health of their voice service in a single dashboard.
Call Model
The Call Model is a proactive monitoring approach focusing on the phases of the voice service life cycle:
registration, call setup, and call teardown, and media quality.
The End-to-End view enables real-time problem isolation of media quality issues from edge to core, or
across voice domains. Hop-by-Hop visibility makes the location of packet loss, stream gaps, or MOS
degradation immediately visible.
EPC KPIs are used to assure the underlying 4G RAN and Core Signaling and Mobility. These KPIs are not
voice-specific, but are critical enabling procedures for VoLTE-based services.
For details of how to configure these dashboard examples and the underlying nGeniusONE Services, see
https://thescout.sharepoint.com/sites/microsites/sabo-service-provider/Pages/SPBU-SBO.aspx
2 Alarming
Metrics used for alarming are generally based on Protocols and message types.
Deployment considerations should include the use of location keys to further qualify alerts. VoLTE keys
might include eUTRAN Cell IDs or TACs, or IP Sites such as eNodeBs, S- and P-GWs, or IMS core nodes.
Wireline location keys include VLAN, and IP sites such as SIP proxies, IMS nodes, media gateways, and
SBCs.
• The Dashboard Over Time View can be used to detect SIP call control accessibility
Call Setup PDD (Post Dial Delay) problems by looking for by looking for incidences
above a certain threshold (e.g., 1 sec).
Call Setup Latency Call setup time above a certain SIP:Call Setup
threshold
3 In VoLTE or IMS, SIP on Gm and Mw, RTP on Mb. In Wireline, at SBC public or private side ports.
Dropped Calls Dropped Call problems by looking for incidences above a certain
threshold (e.g., 3%).
Call Tear-down SCR (Session Completion Rate) problems by looking for incidences below
a certain threshold (e.g.,97%).
• Service Monitors4
4Error Code Distribution views have a “Choose Distribution Type” icon in the top right of the view. When the
monitor type is “Advanced Voice Statistics” the “Choose Distribution Type” icons lists BYE and CANCEL Reason
Codes Distribution choices.
In addition to the Voice Alarm Framework recommendations above, the following VoLTE-specific items
are recommended for Alarming.
5 TCP-based Diameter can also use the Availability Alerts to detect a series or un-responded TCP SYNs.
Name
6 One Network Domain for each S-GW, using the S-GW IP Addr as a Site Location Key
7 One aggregated Network Domain for all S-GWs, using the Network Domains for each S-GW above
Using the Network Services above, the following Application Services are recommended.
A Service is recommended for each specific SIP Message Type, with (a) a Service for each S-GW S1-U
feed, and an Aggregated Service with all S1-U feeds from all S-GWs.
Alarm configuration details for each Service are then shown in the next table.
For the Application Services above, the following Alarm settings are recommended.
Numeric values are examples, only. Each deployment should consider optimizing these.
% Failure 60%
Disabled Baseline 12,000 Fast: 700
Avg Expected: 701
S1-U_SIP_REGISTER Response 45% Degraded: 1000
Time Service Level: 1001
Availability: 60,000
Baseline % Timeout 0.2% 0.4% 100.0%
Enabled 15,000
Threshold % Failure 1.5% 2.0%
% Failure 50%
Disabled 600 Fast: 500
Baseline Avg Expected: 501
S1-U_SIP_INVITE Response 50% Degraded: 1000
Time Service Level: 1001
Availability: 60,000
% Timeout 1.5% 2.0%
Enabled Threshold 1000
% Failure 4.5% 6.0%
In section Error! Reference source not found. a number of 2/3G metrics are listed, which are supported
by Alarming. The following recommendation attempts to minimize the number of Alarm types.
Deployment considerations should include the use of Location Keys to further qualify alerts. 2G/3G keys
might include RAN Cell IDs or LA-RA, OPC and/or DPC, or IP Sites such as the MSS, RNCs, BSCs, etc.
• The Dashboard Over Time View can be used to detect SIP call control accessibility
User Condition
Experience
Metric
CS MO and MT Call NER (Session Establishment Efficiency Ratio) problems by looking for
Setup incidences below a certain threshold (e.g., 97%).
CS MO and MT Call PDD (Post Dial Delay) problems by looking for by looking for incidences
Setup above a certain threshold (e.g., 1 sec).
MO and MT Call Drops 102 Recovery on Timer Expiry above a certain threshold (e.g.,3%).
3 Reporting
This chapter will discuss the recommended best practices reports for voice monitoring, and will provide
general guidelines for VoLTE, Wireline/Cable, and 2G3G.
Creating a report is done in Report Configuration. Below are the configuration templates used for voice
reporting.
The following are general guidelines for use of pre-designed Report Templates in voice deployments
Voice SIP Signal and Media – Top N Flows for UC Summary Report
Best/Worst SIP ASR and Media Active Streams
For reports focusing on a single community, use the “. . . per Client Community” variant of the UC Call
Signaling Summary & UC Media Stream Summary templates.
The following set of services and reports are in use today in a major VoLTE deployment.
Interface Network
Service (Domain) Service Member Location Keys
Name
ND_all_S1-U ND1_S1-U,ND2_S1-U, …
NDx_S1-U
ND1_S11 S11 feed IF
ND2_S11 S11 feed IF SGW1
… … SGW2
S11 NDx_S11 S11 feed IF …
SGWx
ND_all_S11 ND1_S11,ND2_S11, …
NDx_S11
Gx ND_Gx Gx feed IF
Using the Network Services above, the following Application Services are recommended.
SIP, SIP_TCP
S1-U S1-U_SIP AVS10 ND_all_S1-U
Parent Only
DIAMETER-SCTP
S6a S6A_AAR_AAA Universal ND_S6A
S6a AA Messages
Universal DIAMETER-SCTP
S6b S6B_ AAR_AAA ND_S6B
S6b AA Messages
Universal DIAMETER-SCTP
Gx Gx_RAR_RAA ND_Gx
Gx RAR Messages
These must then be placed into the Hierarchy. As a Best Practice, a dedicated Reports Domain can be set
up, enabling the Reports to be configured independently of services used in the Dashboard.
After configuring the Application Services and Hierarchy above, the following Reports can be created in
the nGeniusONE Console Reports Configuration tab.
• S1-U SIP Procedures - SIP Registration, Call Setup, and Call Teardown Messages
• S1-U Voice Signaling KPIs - SEER, PDD, Dropped %, Failed %
• S1-U Voice Quality KPIs DOWNLINK – Packet Loss, Jitter, MOS for the downlink side
• S1-U Voice Quality KPIs UPLINK - Packet Loss, Jitter, MOS for the uplink side
• VoLTE Access – S6 and Gx Diameter messages -- Success, Failure
User Defined
S1-U_SIP_REGISTRATION View 1 / Response Time, Successes, Failures/Over Time
Report
User Defined
S1-U_SIP_CALL_SETUP View 1 / Response Time, Successes, Failures/Over Time
Report
User Defined
S1-U_SIP_CALL_TEARDOWN View 1 / Response Time, Successes, Failures/Over Time
Report
Advance Voice
S1-U_SIP Advanced Voice Statistics / SEER / Over Time
Statistics
S1-U_SIP Advance Voice Advanced Voice Statistics / Post Dial Delay / Over Time
Statistics
S1-U_SIP Advance Voice Advanced Voice Statistics / % Failed Calls / Over Time
Statistics
Media Stream
S1-U_VOICE_QUAL Packet Loss Distribution / Packet Loss In / Chart
Summary
Media Stream
S1-U_VOICE_QUAL MOS Distribution / Degraded MOS In /Chart
Summary
Media Stream
S1-U_VOICE_QUAL Packet Loss Distribution / Packet Loss Out / Chart
Summary
Media Stream
S1-U_VOICE_QUAL MOS Distribution / Degraded MOS Out /Chart
Summary
Data Report
View/Metrics/Mode
Source Template
User Defined
S11_GTP_CREATE_SESSION View 1 / Successes, Failures, % Failures
Report
User Defined
S6A_AAR_AAA View 1 / Successes, Failures, % Failures
Report
User Defined
S6B_ AAR_AAA View 1 / Successes, Failures, % Failures
Report
User Defined
Gx_RAR_RAA View 1 / Successes, Failures, % Failures
Report
• SIP Procedures - SIP Registration, Call Setup, and Call Teardown Messages
• Voice Signaling KPIs - SEER, PDD, Dropped %, Failed %
• Voice Quality KPIs for Untrusted Side– Packet Loss, Jitter, MOS for the Untrusted side
• Voice Quality KPIs for Trusted Side– Packet Loss, Jitter, MOS for the Trusted side
User Defined
SIP_REGISTRATION View 1 / Response Time, Successes, Failures/Over Time
Report
User Defined
SIP_CALL_SETUP View 1 / Response Time, Successes, Failures/Over Time
Report
User Defined
SIP_CALL_TEARDOWN View 1 / Response Time, Successes, Failures/Over Time
Report
Advance Voice
SIP Advanced Voice Statistics / SEER / Over Time
Statistics
SIP Advance Voice Advanced Voice Statistics / Post Dial Delay / Over Time
Statistics
SIP Advance Voice Advanced Voice Statistics / % Failed Calls / Over Time
Statistics
Media Stream
SBC_Untrusted_VOICE_QUAL Packet Loss Distribution / Packet Loss In / Chart
Summary
Media Stream
SBC_Untrusted_VOICE_QUAL MOS Distribution / Degraded MOS In /Chart
Summary
Media Stream
SBC_Trusted_VOICE_QUAL Packet Loss Distribution / Packet Loss Out / Chart
Summary
Media Stream
SBC_Trusted_VOICE_QUAL MOS Distribution / Degraded MOS Out /Chart
Summary