Study Plan
2110 Topo
SAP stands for Session Announcement Protocol (RFC 2974). It is a simple multicast-based protocol that periodically announces the availability of streams on the network by sending out the SDP file for each stream.
224.2.127.254 (port 9875)| Aspect | Importance | Notes |
|---|---|---|
| Basic Understanding | Medium | You should know what it is and what it does |
| Deep Configuration | Low | Only needed with legacy equipment |
| Modern Facilities | Low | Mostly replaced by NMOS IS-04 |
| Troubleshooting | Medium | Still useful when devices rely on SAP discovery |
Without SAP (Centralized): A control system (like NMOS or a proprietary broadcast controller) must manually tell every receiver exactly where to look.
With SAP (Decentralized): Senders "push" their identity and configuration out to the network. They periodically broadcast an SDP (Session Description Protocol) file to a well-known multicast address (typically 239.255.255.255 on port 9875). Receivers listen to this address, "read" the advertisements, and populate their own internal list of available sources.
Automatic Discovery
The key operational benefit of SAP is discovery. When you plug a new device into a network that supports SAP, it immediately starts announcing itself. This allows users to see new cameras, microphones, or audio consoles in their software interface without having to manually type in IP addresses or upload configuration files.
SAP as the "Wrapper" for SDPIt is important to remember that SAP is just the transport vehicle. The actual "content" being sent inside a SAP packet is the SDP file. * SAP is the delivery truck (the protocol that gets the information to everyone).SDP is the package (the actual technical details like IP addresses, codecs, and clock references).
While SAP is highly effective for smaller, simpler networks (like AES67 audio islands), it is increasingly being replaced or augmented by NMOS (Networked Media Open Specifications) in large-scale ST 2110 facilities.
Why? SAP is "noisy" (it broadcasts to everything) and lacks the advanced features of modern control systems, such as security, resource management, and complex API-based routing.
Today NMOS provides a centralized, registry-based approach to discovery and connection management, which is far more scalable and secure than the decentralized "broadcast" nature of SAP.
