Configuring SIP Snooping SIP Snooping Configuration Guidelines
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 14-10
Configuring RTCP Thresholds
When RTCP monitoring is enabled, the SIP snooping feature also inspects the RTCP packet that carries
performance metric for the RTP flow.
Depending on the RTCP capabilities of the SIP user agent endpoints, the following metrics can be
determined by software:
• Packet loss
• Round Trip Time
• R Factor Only supported with RTCP-XR
• MOS factor – Only supported with RTCP-XR
The SIP snooping feature offers configurable thresholds for each performance metric and each media
types.
-> sip-snooping threshold audio jitter 30
-> sip-snooping threshold video jitter 50
-> sip-snooping threshold audio packet-lost 40
-> sip-snooping threshold video packet-lost 30
-> sip-snooping threshold audio round-trip-delay 180
-> sip-snooping threshold video round-trip-delay 180
-> sip-snooping threshold audio R-factor 30
-> sip-snooping threshold video R-factor 30
-> sip-snooping threshold audio MOS 1
-> sip-snooping threshold video MOS 2
Configuring the Logging Threshold for the Number of Calls
To configure the threshold for the number of call records to be logged on to the flash file, use the sip-
snooping logging-threshold num-of-calls command as follows
-> sip-snooping logging-threshold num-of-calls 300
Configuring Policy Rules for SIP Snooping
Unlike regular policy rule, a SIP policy rule is not programmed in the hardware when it is configured. The
ACL is only programmed when the SIP snooping module detects a new RTP flow and parses the SIP
policy rules to determine the QOS policy actions required for this RTP flow.
Policy Condition
All other policy conditions are still supported for the SIP policy rules. This allows specific QOS
treatments (policy actions) for media streams based on the origin of the call. For instance, a SIP policy
condition can be combined with:
• Source port
• Source IP address/subnet
To configure the policy condition, use the commands as follows.
-> policy condition <condition_name> sip {audio | video | other}
-> policy condition <condition_name> sip {audio | video | other}source port 1/2