Configuring SIP Snooping SIP Snooping Use Case
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 14-14
-> show sip-snooping call-records ended-calls full
Legend: start date time duration media-type end-reason
call-id / from-tag / to-tag
IP address port DSCP (forward/reverse)
policy-rule (F/R)
Pkt count (F/R)
statistics min / max / avg %samples exceeding threshold (F/R)
--------------------------------------------------------------------------------
2002-04-06 01:06:10 UTC 0d 0h 4m 15s Audio -
0010CFC0-4A05-10DA-B960-F1A3FE87AA77-23025@ot380.aos.com / 0010CFE8-4A05-10DA-B960-
F1A3FE87AA77-258649 / 1668946822
IP/DSCP 10.20.0.2 6000 56/56 10.10.0.2 6000 46/46
Policy-Rule Voice_srcip_SIP1_rule Voice_srcip_SIP2_rule
Pkt-Count 12272 61385
Pkt-Loss 0 0 0.00 0% 0 0 0.00
0%
Jitter 0 0 0.00 0% 0 0 0.00
0%
Delay 0 0 0.00 0% 0 0 0.00
0%
R-factor 0 0 0.00 0% 96 96 96.00
0%
MOS 0 0 0.00 0% 44 44 44.00
-----------------------------------------------------------------------------------
Number of Call Records: 1
Similar to the above example, more conditions can be combined in a single SIP rule.
Advanced RTCP Control
For each RTP flow, RTCP monitoring can be enabled or disabled. When enabled, the DSCP marking can
also be controlled. Also Trap will be generated if RTCP parameters exceed the Threshold values
configured in SIP configuration.
In this example, specific QOS treatments are configured based on the Source IP subnet.
• Voice source IP subnet 10.10.0.0 = DSCP 56— RTCP packets for these RTP flows are trapped to CPU
and assigned with DSCP 56.
-> policy action DSCP56 dscp 56
• Video source IP subnet 10.10.0.0= RTCP—packets for these RTP flows are trapped to CPU and have
their DSCP unchanged.
-> policy action DSCP32 rtcp-monitoring enable trust-DSCP
• Voice source IP subnet 10.20.0.0 = DSCP 46 + No RTCP monitoring—RTCP packets for these RTP
flows are not trapped to CPU and assigned with DSCP 46.
-> policy action DSCP46 dscp 46 rtcp-monitoring disable
• Video source IP subnet 10.20.0.0 = DSCP 48 + RTCP monitoring and explicit DSCP 46—RTCP
packets for these RTP flows are trapped to CPU and assigned with DSCP 46.
-> policy action DSCP48 dscp 48 rtcp-monitoring enable rtcp-dscp 46
To Next Page
Loading...
