{
  "cards": [
    {
      "front": "Transaction",
      "back": "A request and its matching responses.",
      "source": "RFC 3261, SIP",
      "room": "sip-transactions"
    },
    {
      "front": "Dialog",
      "back": "A peer relationship identified by Call-ID and tags.",
      "source": "RFC 3261, SIP",
      "room": "sip-transactions"
    },
    {
      "front": "SIP transactions and dialogs",
      "back": "A transaction pairs a request with its responses.",
      "source": "RFC 3261, SIP",
      "room": "sip-transactions"
    },
    {
      "front": "A 180 Ringing means the call was answered.",
      "back": "False. False. It means alerting. The 200 accepts the session.",
      "source": "RFC 3261, SIP",
      "room": "sip-transactions"
    },
    {
      "front": "ACK for a 2xx is optional.",
      "back": "False. False. Without ACK the far end retransmits the 200 and can drop the call.",
      "source": "RFC 3261, SIP",
      "room": "sip-transactions"
    },
    {
      "front": "Early offer",
      "back": "SDP in the INVITE.",
      "source": "RFC 3264, offer/answer",
      "room": "offer-answer"
    },
    {
      "front": "Delayed offer",
      "back": "SDP offered in the reliable response or the 200.",
      "source": "RFC 3264, offer/answer",
      "room": "offer-answer"
    },
    {
      "front": "Offer and answer",
      "back": "SDP is the offer or the answer, not a second signaling protocol you ignore.",
      "source": "RFC 3264, offer/answer",
      "room": "offer-answer"
    },
    {
      "front": "The answer may add a codec the offer did not list.",
      "back": "False. False. The answer narrows the offer.",
      "source": "RFC 3264, offer/answer",
      "room": "offer-answer"
    },
    {
      "front": "AOR",
      "back": "The address-of-record being registered.",
      "source": "RFC 3261, SIP",
      "room": "sip-registration"
    },
    {
      "front": "Contact",
      "back": "The device URI to try later.",
      "source": "RFC 3261, SIP",
      "room": "sip-registration"
    },
    {
      "front": "Registration",
      "back": "REGISTER publishes a Contact. It does not place a call.",
      "source": "RFC 3261, SIP",
      "room": "sip-registration"
    },
    {
      "front": "REGISTER creates a voice session.",
      "back": "False. False. It stores a Contact binding.",
      "source": "RFC 3261, SIP",
      "room": "sip-registration"
    },
    {
      "front": "PRACK",
      "back": "Acknowledgement of a reliable provisional response.",
      "source": "RFC 3262, PRACK",
      "room": "prack-early-media"
    },
    {
      "front": "100rel",
      "back": "The extension that makes selected 1xx responses reliable.",
      "source": "RFC 3262, PRACK",
      "room": "prack-early-media"
    },
    {
      "front": "Early media and PRACK",
      "back": "183 Session Progress can carry SDP before answer.",
      "source": "RFC 3262, PRACK",
      "room": "prack-early-media"
    },
    {
      "front": "Hearing ringback proves the called party answered.",
      "back": "False. False. Ringback can be early media.",
      "source": "RFC 3262, PRACK",
      "room": "prack-early-media"
    },
    {
      "front": "Partition",
      "back": "A group of patterns with the same reachability.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "partitions-css"
    },
    {
      "front": "CSS",
      "back": "An ordered list of partitions.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "partitions-css"
    },
    {
      "front": "Partitions and calling search spaces",
      "back": "A partition is a bucket of patterns.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "partitions-css"
    },
    {
      "front": "CUCM searches every partition and picks the longest match across all of them.",
      "back": "False. False. It walks the CSS in order.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "partitions-css"
    },
    {
      "front": "Route pattern",
      "back": "Digits in a partition that point at a gateway or route list.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "route-patterns"
    },
    {
      "front": "Route list",
      "back": "An ordered set of route groups.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "route-patterns"
    },
    {
      "front": "Route patterns, lists, and groups",
      "back": "A route pattern matches digits.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "route-patterns"
    },
    {
      "front": "A route group is a list of partitions.",
      "back": "False. False. It is a list of gateways or trunks.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "route-patterns"
    },
    {
      "front": "Translation pattern",
      "back": "A pattern that transforms digits and can continue routing.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "transformations"
    },
    {
      "front": "Mask",
      "back": "A digit rewrite applied to a number field.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "transformations"
    },
    {
      "front": "Transformations",
      "back": "Called, calling, and redirecting numbers are different fields.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "transformations"
    },
    {
      "front": "The calling number and the called number are the same field.",
      "back": "False. False.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "transformations"
    },
    {
      "front": "SIP trunk",
      "back": "CUCM's signaling peer toward a gateway or another call agent.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "sip-trunks"
    },
    {
      "front": "SIP profile",
      "back": "Timers, OPTIONS, and offer behavior for that trunk.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "sip-trunks"
    },
    {
      "front": "SIP trunks on CUCM",
      "back": "The trunk, the SIP profile, and the security profile are three objects.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "sip-trunks"
    },
    {
      "front": "A SIP trunk in service proves the route pattern points at it.",
      "back": "False. False. Routing and status are separate.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "sip-trunks"
    },
    {
      "front": "Dial peer",
      "back": "An IOS rule that matches a call and names a target.",
      "source": "Cisco Unified Border Element product support",
      "room": "dial-peers"
    },
    {
      "front": "Preference",
      "back": "A tie-break after match length.",
      "source": "Cisco Unified Border Element product support",
      "room": "dial-peers"
    },
    {
      "front": "Dial peers",
      "back": "A dial peer matches an incoming or outgoing call.",
      "source": "Cisco Unified Border Element product support",
      "room": "dial-peers"
    },
    {
      "front": "Outbound dial-peer preference is consulted before match length.",
      "back": "False. False. Longest match comes first when hunt is the default.",
      "source": "Cisco Unified Border Element product support",
      "room": "dial-peers"
    },
    {
      "front": "B2BUA",
      "back": "A user agent that sits between two dialogs.",
      "source": "Cisco Unified Border Element product support",
      "room": "cube-b2bua"
    },
    {
      "front": "Media anchor",
      "back": "RTP terminates on the SBC.",
      "source": "Cisco Unified Border Element product support",
      "room": "cube-b2bua"
    },
    {
      "front": "CUBE as a B2BUA",
      "back": "CUBE terminates one dialog and starts another.",
      "source": "Cisco Unified Border Element product support",
      "room": "cube-b2bua"
    },
    {
      "front": "CUBE forwards one SIP dialog unchanged, like a proxy.",
      "back": "False. False. It is a B2BUA.",
      "source": "Cisco Unified Border Element product support",
      "room": "cube-b2bua"
    },
    {
      "front": "SRST",
      "back": "Fallback call processing on the branch router.",
      "source": "Cisco Unified SRST product support",
      "room": "srst"
    },
    {
      "front": "Re-home",
      "back": "Phones returning to CUCM after the WAN recovers.",
      "source": "Cisco Unified SRST product support",
      "room": "srst"
    },
    {
      "front": "SRST",
      "back": "SRST is the fallback when phones cannot reach CUCM.",
      "source": "Cisco Unified SRST product support",
      "room": "srst"
    },
    {
      "front": "SRST automatically clones every CUCM hunt pilot.",
      "back": "False. False.",
      "source": "Cisco Unified SRST product support",
      "room": "srst"
    },
    {
      "front": "Local gateway",
      "back": "The premises SBC that connects Webex Calling to PSTN or a PBX.",
      "source": "Webex Help",
      "room": "local-gateway"
    },
    {
      "front": "Certificate trunk",
      "back": "A trunk that authenticates with a certificate instead of a registration.",
      "source": "Webex Help",
      "room": "local-gateway"
    },
    {
      "front": "Local gateway toward Webex Calling",
      "back": "The local gateway is how premises PSTN or a PBX meets Webex Calling.",
      "source": "Webex Help",
      "room": "local-gateway"
    },
    {
      "front": "A local gateway registration is the same object as a CUCM phone registration.",
      "back": "False. False. It is the trunk from CUBE toward Calling.",
      "source": "Webex Help",
      "room": "local-gateway"
    },
    {
      "front": "Traversal zone",
      "back": "The zone that joins Expressway-C and Expressway-E.",
      "source": "Cisco Expressway Series product support",
      "room": "expressway-pair"
    },
    {
      "front": "Expressway-E",
      "back": "The edge server.",
      "source": "Cisco Expressway Series product support",
      "room": "expressway-pair"
    },
    {
      "front": "Expressway-C and Expressway-E",
      "back": "Expressway-C lives on the inside, next to CUCM.",
      "source": "Cisco Expressway Series product support",
      "room": "expressway-pair"
    },
    {
      "front": "Every CUCM call must pass through Expressway.",
      "back": "False. False.",
      "source": "Cisco Expressway Series product support",
      "room": "expressway-pair"
    },
    {
      "front": "MRA",
      "back": "Mobile and Remote Access through Expressway.",
      "source": "Cisco Expressway Series product support",
      "room": "mra"
    },
    {
      "front": "SRV",
      "back": "A DNS record the client uses to find the edge.",
      "source": "Cisco Expressway Series product support",
      "room": "mra"
    },
    {
      "front": "Mobile and Remote Access",
      "back": "MRA lets a remote Cisco phone or Jabber register to CUCM through the Expressway pair.",
      "source": "Cisco Expressway Series product support",
      "room": "mra"
    },
    {
      "front": "MRA replaces CUCM as the registrar.",
      "back": "False. False. CUCM remains the registrar.",
      "source": "Cisco Expressway Series product support",
      "room": "mra"
    },
    {
      "front": "Traversal media",
      "back": "The UDP range Expressway uses for remote media.",
      "source": "Cisco Expressway Series product support",
      "room": "firewall-traversal"
    },
    {
      "front": "Signaling",
      "back": "SIP or the HTTPS path used to register.",
      "source": "Cisco Expressway Series product support",
      "room": "firewall-traversal"
    },
    {
      "front": "Firewall and traversal",
      "back": "Open the ports your version's guide lists.",
      "source": "Cisco Expressway Series product support",
      "room": "firewall-traversal"
    },
    {
      "front": "A completed INVITE proves the firewall allows RTP.",
      "back": "False. False.",
      "source": "Cisco Expressway Series product support",
      "room": "firewall-traversal"
    },
    {
      "front": "EF",
      "back": "Expedited Forwarding, DSCP 46.",
      "source": "RFC 3246, Expedited Forwarding",
      "room": "dscp-trust"
    },
    {
      "front": "Trust boundary",
      "back": "The place you decide to keep or rewrite a mark.",
      "source": "RFC 3246, Expedited Forwarding",
      "room": "dscp-trust"
    },
    {
      "front": "DSCP and the trust boundary",
      "back": "Voice RTP is commonly marked EF, DSCP 46.",
      "source": "RFC 3246, Expedited Forwarding",
      "room": "dscp-trust"
    },
    {
      "front": "EF and CS3 are the same mark.",
      "back": "False. False. EF is DSCP 46. CS3 is a different codepoint.",
      "source": "RFC 3246, Expedited Forwarding",
      "room": "dscp-trust"
    },
    {
      "front": "LLQ",
      "back": "A queue that serves a priority class up to a configured rate.",
      "source": "ITU-T G.114, one-way transmission time",
      "room": "llq-delay"
    },
    {
      "front": "Packetization",
      "back": "The time to fill one RTP payload.",
      "source": "ITU-T G.114, one-way transmission time",
      "room": "llq-delay"
    },
    {
      "front": "LLQ and the delay budget",
      "back": "Priority queue bandwidth is a limiter for the EF class.",
      "source": "ITU-T G.114, one-way transmission time",
      "room": "llq-delay"
    },
    {
      "front": "LLQ adds bandwidth to a circuit.",
      "back": "False. False. It schedules the bandwidth you already have.",
      "source": "ITU-T G.114, one-way transmission time",
      "room": "llq-delay"
    },
    {
      "front": "Location",
      "back": "A CUCM bandwidth domain for admission control.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "locations-cac"
    },
    {
      "front": "CAC",
      "back": "Call admission control, the decision to allow a call.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "locations-cac"
    },
    {
      "front": "Locations and call admission control",
      "back": "A CUCM location names a bandwidth budget between sites.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "locations-cac"
    },
    {
      "front": "CUCM locations mark RTP as EF.",
      "back": "False. False.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "locations-cac"
    },
    {
      "front": "CVP",
      "back": "Customer Voice Portal, the voice browser and call-control front in many designs.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "ucce-path"
    },
    {
      "front": "ICM",
      "back": "The routing brain in UCCE.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "ucce-path"
    },
    {
      "front": "UCCE from carrier to agent",
      "back": "Ingress, routing, queue treatment, and the agent are different stages.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "ucce-path"
    },
    {
      "front": "Queue music means an agent phone is ringing.",
      "back": "False. False. Treatment happens before delivery.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "ucce-path"
    },
    {
      "front": "Label",
      "back": "The destination the script returns.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "cucm-ucce-bridge"
    },
    {
      "front": "Peripheral gateway",
      "back": "The process that represents CUCM devices to ICM.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "cucm-ucce-bridge"
    },
    {
      "front": "The CUCM bridge into UCCE",
      "back": "Agents are CUCM endpoints.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "cucm-ucce-bridge"
    },
    {
      "front": "A successful ICM script guarantees CUCM can ring the phone.",
      "back": "False. False.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "cucm-ucce-bridge"
    },
    {
      "front": "Flow",
      "back": "The routing document in Webex Contact Center.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "wxcc-and-ucce"
    },
    {
      "front": "Script",
      "back": "The routing document in ICM.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "wxcc-and-ucce"
    },
    {
      "front": "Webex Contact Center beside UCCE",
      "back": "Webex Contact Center and UCCE are different products.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "wxcc-and-ucce"
    },
    {
      "front": "An ICM script runs unchanged inside Webex Contact Center.",
      "back": "False. False.",
      "source": "Cisco Unified Contact Center Enterprise product support",
      "room": "wxcc-and-ucce"
    },
    {
      "front": "Dedicated Instance",
      "back": "A hosted CUCM offer inside the Webex cloud contract.",
      "source": "Webex Help",
      "room": "calling-versus-di"
    },
    {
      "front": "Control Hub",
      "back": "The admin place for Webex Calling locations and numbers.",
      "source": "Webex Help",
      "room": "calling-versus-di"
    },
    {
      "front": "Webex Calling and Dedicated Instance",
      "back": "Multi-tenant Webex Calling and Dedicated Instance are different offers.",
      "source": "Webex Help",
      "room": "calling-versus-di"
    },
    {
      "front": "Dedicated Instance uses the same dial-plan objects as multi-tenant Calling.",
      "back": "False. False.",
      "source": "Webex Help",
      "room": "calling-versus-di"
    },
    {
      "front": "Dual-run",
      "back": "Old and new paths both available for a number during a test.",
      "source": "Webex Help",
      "room": "dual-run"
    },
    {
      "front": "Rollback",
      "back": "Returning the number to the path you saved.",
      "source": "Webex Help",
      "room": "dual-run"
    },
    {
      "front": "Dual-run and rollback",
      "back": "Move one number you can give back.",
      "source": "Webex Help",
      "room": "dual-run"
    },
    {
      "front": "A carrier port can always be undone in five minutes.",
      "back": "False. False. Confirm the porting rules.",
      "source": "Webex Help",
      "room": "dual-run"
    },
    {
      "front": "Survivability gateway",
      "back": "A local gateway mode that keeps selected Calling users up during a cloud outage.",
      "source": "Webex Help",
      "room": "cutover-survivability"
    },
    {
      "front": "Fallback test",
      "back": "A planned failure of the primary path.",
      "source": "Webex Help",
      "room": "cutover-survivability"
    },
    {
      "front": "Survivability during cutover",
      "back": "Cloud calling needs a plan for when the cloud path is down.",
      "source": "Webex Help",
      "room": "cutover-survivability"
    },
    {
      "front": "SRST protects Webex Calling apps with no extra design.",
      "back": "False. False.",
      "source": "Webex Help",
      "room": "cutover-survivability"
    },
    {
      "front": "Hypothesis",
      "back": "The single fault you are testing.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "one-change"
    },
    {
      "front": "Evidence pack",
      "back": "The traces and notes that show the test.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "one-change"
    },
    {
      "front": "One hypothesis, one change",
      "back": "Say what you think is broken, in one sentence.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "one-change"
    },
    {
      "front": "Changing the CSS, the codec, and the gateway in one window is a clean test.",
      "back": "False. False.",
      "source": "Cisco Unified Communications Manager product support",
      "room": "one-change"
    },
    {
      "front": "Ladder",
      "back": "A drawing of messages between named boxes.",
      "source": "RFC 3261, SIP",
      "room": "read-a-ladder"
    },
    {
      "front": "Cause",
      "back": "The reason phrase or Q.850 cause on a failure.",
      "source": "RFC 3261, SIP",
      "room": "read-a-ladder"
    },
    {
      "front": "Reading a ladder",
      "back": "One leg at a time.",
      "source": "RFC 3261, SIP",
      "room": "read-a-ladder"
    },
    {
      "front": "Two Call-IDs mean the trace is corrupt.",
      "back": "False. False. A B2BUA creates two dialogs.",
      "source": "RFC 3261, SIP",
      "room": "read-a-ladder"
    },
    {
      "front": "SDP c= line",
      "back": "The address where media should be sent.",
      "source": "RFC 3550, RTP",
      "room": "one-way-audio"
    },
    {
      "front": "One-way audio",
      "back": "Media in a single direction.",
      "source": "RFC 3550, RTP",
      "room": "one-way-audio"
    },
    {
      "front": "One-way audio",
      "back": "Signaling can be perfect while RTP fails in one direction.",
      "source": "RFC 3550, RTP",
      "room": "one-way-audio"
    },
    {
      "front": "A 200 OK with SDP proves two-way audio.",
      "back": "False. False.",
      "source": "RFC 3550, RTP",
      "room": "one-way-audio"
    },
    {
      "front": "MLTS",
      "back": "A multi-line telephone system, the term the FCC page uses for enterprise and hotel phone systems.",
      "source": "FCC, Kari's Law and RAY BAUM'S Act for multi-line telephone systems",
      "room": "emergency-direct"
    },
    {
      "front": "Dispatchable location",
      "back": "The FCC page's term for a validated street address plus detail needed to find the caller.",
      "source": "FCC, Kari's Law and RAY BAUM'S Act for multi-line telephone systems",
      "room": "emergency-direct"
    },
    {
      "front": "Direct dial, notification, and location",
      "back": "This page is study material, not legal advice and not an emergency plan.",
      "source": "FCC, Kari's Law and RAY BAUM'S Act for multi-line telephone systems",
      "room": "emergency-direct"
    },
    {
      "front": "Kari's Law, as the FCC page describes it, is satisfied by requiring users to dial 9 before 911.",
      "back": "False. False. The page says direct dialing means no prefix or access code such as 9.",
      "source": "FCC, Kari's Law and RAY BAUM'S Act for multi-line telephone systems",
      "room": "emergency-direct"
    },
    {
      "front": "This lab page is legal advice for every country.",
      "back": "False. False. It is a study note about pages that were opened. Confirm the rule where you operate.",
      "source": "FCC, Kari's Law and RAY BAUM'S Act for multi-line telephone systems",
      "room": "emergency-direct"
    },
    {
      "front": "ERL",
      "back": "Emergency response location. The zone Emergency Responder binds to a switch port.",
      "source": "Cisco Emergency Responder product support",
      "room": "cer-erl-elin"
    },
    {
      "front": "ELIN",
      "back": "Emergency location identification number. The callback number sent for that zone.",
      "source": "Cisco Emergency Responder product support",
      "room": "cer-erl-elin"
    },
    {
      "front": "Emergency Responder, ERL, and ELIN",
      "back": "Cisco Emergency Responder is a separate product. The support page opened here lists Release 15 as available, with a release date of 16 October 2023.",
      "source": "Cisco Emergency Responder product support",
      "room": "cer-erl-elin"
    },
    {
      "front": "An ELIN is the caller's directory number.",
      "back": "False. False. The CUCM chapter describes the ELIN as the number Emergency Responder uses for routing and PSAP callback, mapped back to the extension.",
      "source": "Cisco Emergency Responder product support",
      "room": "cer-erl-elin"
    },
    {
      "front": "A phone on a switch Emergency Responder does not know is still located.",
      "back": "False. False. The planning chapter calls those phones unlocated.",
      "source": "Cisco Emergency Responder product support",
      "room": "cer-erl-elin"
    },
    {
      "front": "PSAP",
      "back": "Public safety answering point. The Wikipedia article describes it as the call center that answers the emergency call.",
      "source": "Cisco Emergency Responder Administration Guide, Release 15",
      "room": "emergency-onsite"
    },
    {
      "front": "On-site alert",
      "back": "The Emergency Responder notification path named in the Release 15 administration guide.",
      "source": "Cisco Emergency Responder Administration Guide, Release 15",
      "room": "emergency-onsite"
    },
    {
      "front": "On-site alert, callback, and what this lab will not decide",
      "back": "The Release 15 administration guide contents include on-site alerts, off-premises users, and a national E911 service provider. Those are different chapters.",
      "source": "Cisco Emergency Responder Administration Guide, Release 15",
      "room": "emergency-onsite"
    },
    {
      "front": "An outbound 911 test proves PSAP callback.",
      "back": "False. False. Callback is a separate call toward the ELIN.",
      "source": "Cisco Emergency Responder Administration Guide, Release 15",
      "room": "emergency-onsite"
    },
    {
      "front": "Built-in bridge",
      "back": "The phone feature CUCM uses when the phone itself forks recording media.",
      "source": "Feature Configuration Guide for CUCM, Release 15, Recording",
      "room": "recording-phone"
    },
    {
      "front": "Fork",
      "back": "A copy of the media stream sent to a recorder.",
      "source": "Feature Configuration Guide for CUCM, Release 15, Recording",
      "room": "recording-phone"
    },
    {
      "front": "Phone fork and network fork",
      "back": "The CUCM 15 feature guide says phone-based recording takes media from the phone. The phone forks two streams to the recording server.",
      "source": "Feature Configuration Guide for CUCM, Release 15, Recording",
      "room": "recording-phone"
    },
    {
      "front": "A 200 OK proves the recorder received both audio directions.",
      "back": "False. False. The fork is a separate media path.",
      "source": "Feature Configuration Guide for CUCM, Release 15, Recording",
      "room": "recording-phone"
    },
    {
      "front": "The built-in bridge on one phone always follows the cluster-wide parameter.",
      "back": "False. False. The feature guide says the phone setting overrides the cluster default when default is not selected.",
      "source": "Feature Configuration Guide for CUCM, Release 15, Recording",
      "room": "recording-phone"
    },
    {
      "front": "SRC",
      "back": "Session recording client. The CUBE guide says CUBE takes this role when SIPREC is configured.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-siprec"
    },
    {
      "front": "SRS",
      "back": "Session recording server. RFC 7865 describes metadata from the server's point of view.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-siprec"
    },
    {
      "front": "SIPREC and CUBE as the recording client",
      "back": "RFC 7245 describes architectures for recording in a SIP environment by sending a copy of a media stream to a recording device.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-siprec"
    },
    {
      "front": "The recording INVITE is the same dialog as the call being recorded.",
      "back": "False. False. SIPREC is a separate recording session.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-siprec"
    },
    {
      "front": "Recording file",
      "back": "The stored copy of the media.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-compliance"
    },
    {
      "front": "Quality score",
      "back": "A review of a call. It is not the media file.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-compliance"
    },
    {
      "front": "Compliance is a reason, not a setting",
      "back": "RFC 7245 says some environments record every call for regulatory, compliance, and consumer-protection reasons.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-compliance"
    },
    {
      "front": "RFC 7245 chooses the retention period for your contact center.",
      "back": "False. False. It explains recording architectures. It does not set your policy.",
      "source": "RFC 7245, architecture for media recording using SIP",
      "room": "recording-compliance"
    },
    {
      "front": "SIP trunk",
      "back": "The signaling peer between two call agents or between a PBX and a provider.",
      "source": "SIP trunking (Wikipedia)",
      "room": "open-sip-trunk"
    },
    {
      "front": "SIPconnect",
      "back": "The SIP Forum's technical recommendation for IP peering with a VoIP provider.",
      "source": "SIP trunking (Wikipedia)",
      "room": "open-sip-trunk"
    },
    {
      "front": "A SIP trunk is a peer, not a brand",
      "back": "Wikipedia's SIP trunking article describes a SIP service between a provider and a customer's SIP PBX.",
      "source": "SIP trunking (Wikipedia)",
      "room": "open-sip-trunk"
    },
    {
      "front": "One SIP trunk means both PBXs share one dial plan.",
      "back": "False. False. Each side matches the digits with its own rules.",
      "source": "SIP trunking (Wikipedia)",
      "room": "open-sip-trunk"
    },
    {
      "front": "Dialplan",
      "back": "The Asterisk or FreeSWITCH rules that match a call. Not a CUCM CSS.",
      "source": "Asterisk (Wikipedia)",
      "room": "asterisk-freeswitch"
    },
    {
      "front": "res_pjsip",
      "back": "The Asterisk SIP channel stack named in the documentation opened for this lab.",
      "source": "Asterisk (Wikipedia)",
      "room": "asterisk-freeswitch"
    },
    {
      "front": "Asterisk and FreeSWITCH as the other PBX",
      "back": "Wikipedia describes Asterisk as a software PBX that connects phones, the PSTN, and VoIP endpoints.",
      "source": "Asterisk (Wikipedia)",
      "room": "asterisk-freeswitch"
    },
    {
      "front": "An Asterisk dialplan is a CUCM calling search space.",
      "back": "False. False. It is a different object on a different product.",
      "source": "Asterisk (Wikipedia)",
      "room": "asterisk-freeswitch"
    },
    {
      "front": "WebRTC",
      "back": "Browser real-time communication. The W3C recommendation is the API. RFC 8825 points at the protocol suite.",
      "source": "WebRTC (Wikipedia)",
      "room": "webrtc-bridge"
    },
    {
      "front": "JSEP",
      "back": "JavaScript Session Establishment Protocol, RFC 8829.",
      "source": "WebRTC (Wikipedia)",
      "room": "webrtc-bridge"
    },
    {
      "front": "WebRTC, SIP over WebSocket, and a hosted bridge",
      "back": "Wikipedia describes WebRTC as browser and mobile APIs for real-time audio and video without a plugin.",
      "source": "WebRTC (Wikipedia)",
      "room": "webrtc-bridge"
    },
    {
      "front": "A WebRTC page is a CUCM SIP phone.",
      "back": "False. False. Something has to translate, unless the far end also speaks WebRTC.",
      "source": "WebRTC (Wikipedia)",
      "room": "webrtc-bridge"
    },
    {
      "front": "RFC 8829 replaces SIP.",
      "back": "False. False. It describes JavaScript control of the signaling plane and how that relates to existing signaling.",
      "source": "WebRTC (Wikipedia)",
      "room": "webrtc-bridge"
    }
  ]
}