QoS-based routing towards a terminating gateway/subscriber is configurable from both a signaling and a media perspective. For Media QoS KPI Profile, see "Media QoS KPI Profile".
The Signaling Quality of Service (QoS) Key Performance Indicator (KPI) Profile provides a mechanism to calculate the various signaling KPIs to measure signaling QoS-related routing parameters, and use the results to make informed decisions when routing calls.
Since these constraints are very dynamic, a utilization factor for each route is configurable on PSX/ERE for the route. This utilization factor is then provided to SBC as part of the route attributes, and is used by SBC to filter out any route/trunk group failing the criteria.
CLI syntax to configure a Signaling QoS KPI Profile:
CLI syntax to assign Signaling QoS KPI Profile to IP Signaling Profile:
The Signaling Qos KPI Profile Parameters are shown below:
QoS KPI profile name.
Use this flag to enable Answer Seizure Ratio (ASR) KPI.
ASR threshold (default = 70).
Use this flag to enable Call Limit Utilization (CLU) KPI.
CLU threshold (default = 70)
Enter the expression defining this KPI. The default value is "
Other configurable examples:
Use flag to enable Post-Gateway Ringing Delay (PGRD) KPI.
PGRD threshold in milliseconds. (default =1000).
Use flag to enable this profile.
Use flag to enable SCRU KPI.
Sustained Call Rate Utilization (default = 70)
This example creates and enables a QoS KPI profile named "MyQosProfile", and enables ASR and CLI KPIs. The ASR threshold is set to "55" while CLU thresholds is left at default value of "70". With the next two commands, "MyQosProfile" is associated with "DEFAULT_SIP" IP Signaling Profile and QoS-based routing is enabled.