Home / Toll fraud, E911, recording, and QoS
Toll fraud, E911, recording, and QoS
Defensive operations: source restrictions, emergency location, disclosed SIPREC, and the EF PHB.
7 rooms42 quiz items
Rooms
- The toll-fraud class, stated defensively
Four exposure classes, source restrictions, and caller-identity as a separate control.
- Trusted addresses and source restrictions
The IP address trusted list is per product page. CME and SRST do not share one list size.
- Emergency calling, location, and the FCC page
Service URN, location conveyance, and the FCC MLTS page. State PSAP rules are not invented here.
- Disclosed recording with SIPREC
RFC 7866 is the recording protocol. RFC 7865 is the metadata. Notice and retention are legal questions.
- Voice, EF, and what the PHB does not design
RFC 3246 defines the EF PHB. RFC 4594 maps telephony to EF. This lesson does not design a LAN.
- Alarms that match the failure
Alarm on OPTIONS, TLS expiry, 503, recording-session failure, and trusted-list rejects. Each alarm names its document.
- One change in the window
Freeze the baseline, change one variable, verify, and keep the previous snippet ready.
Ecosystem
SIP does not replace workforce management, quality monitoring, CRM, emergency policy, or a messaging registry. It is the session seam those systems hang from. Compliance notes on this page are educational and are not legal advice.
Sources and go deeper
- Cisco CME toll-fraud prevention — last checked 2026-10
- RFC 3261 §22 — last checked 2026-10
- RFC 7616 — last checked 2026-10
- Cisco SRST trusted IP authentication — last checked 2026-10
- FCC call authentication — confirm
- RFC 8224 — last checked 2026-10
- RFC 3261 — last checked 2026-10