Sony FR7 SRT setup: send SRT to Callaba Gateway
More live video workflow notes and product updates.
Sony ILME-FR7 contribution workflow
Send the FR7's cinematic PTZ feed to a visible SRT receiving operation
The Sony FR7 can originate or accept an SRT connection without an external encoder. That makes it practical for a remotely operated stage, studio, house of worship, or live production where the camera position must stay compact. Callaba can receive the contribution, show the decoded picture in Multiview, expose the incoming session to the operator, and attach recording or routing after the transport has been proved.
The clearest first connection
For a camera on a venue network reaching a stable cloud or data-centre endpoint, configure the FR7 as SRT Caller and Callaba as Listener. The camera initiates an outbound UDP session to the Callaba host and port. This usually avoids exposing the camera itself to inbound Internet traffic and gives the receiving team one known address to protect and monitor.
The reverse arrangement is also possible because Sony documents SRT Listener operation on the FR7. Use that only when Callaba can deliberately reach the camera's listening address through the firewall and NAT boundary. Connection mode describes who starts the session; it does not reverse the direction of the picture coming from the camera.
The moving frame represents one contribution session, not a measurement of bandwidth or latency. With reduced-motion enabled, the diagram remains static and fully legible.
Know what travels over each FR7 interface
The FR7 supports several ways to move video, but they are not interchangeable labels for the same path. For SRT streaming, the camera uses H.264. Do not select an H.265 camera profile and assume it will be carried by the SRT output. Sony documents H.264 and H.265 for RTSP, while the NDI option is NDI HX2. Those alternatives may suit a controlled local network, but they do not alter the codec constraint on the FR7's SRT stream.
The camera also has an SFP+ optical SDI interface. It is a professional baseband video connection, not a SMPTE ST 2110 network interface. If the production requires ST 2110, it needs the appropriate external conversion or facility gateway; an SFP+ connector by itself does not establish IP media interoperability.
Agree the connection contract before touching the camera
| Decision | FR7 | Callaba | What the operator verifies |
|---|---|---|---|
| Connection mode | Caller for the usual outbound venue connection; Listener for a deliberately reachable camera | The complementary Listener or Caller role | One side calls and exactly one side listens. |
| Destination | Callaba host and UDP port in Caller mode | Running SRT endpoint on the approved host and port | DNS, firewall and NAT resolve to the intended instance. |
| Video codec | H.264 for SRT | Receive and decode the stated H.264 profile | A real moving picture appears, not just a connected socket. |
| Encryption | AES-128 or AES-256 with the agreed passphrase | The same algorithm and passphrase | A mismatch fails cleanly; secrets are not placed in screenshots or public notes. |
| Latency | A supported value from 20 to 8000 ms, selected for the tested route | A compatible receiving policy | The setting covers route jitter without exceeding the production delay budget. |
| Media profile | Raster, frame rate, audio and H.264 settings chosen for the show | Downstream paths capable of handling that profile | Multiview, recording and final output preserve the required picture and sound. |
There is no honest universal bitrate for this camera-to-server path. Detail, motion, frame rate, available uplink, encoder settings, and the downstream platform all matter. Begin from the project's picture-quality requirement and a measured network budget, then validate the chosen profile with representative motion. Do not invent a low number merely to make the connection easy during setup.
Build the Caller-to-Listener workflow
- Record the production state. Note the FR7 firmware, camera format, selected lens/output path, network topology, and the Sony Help Guide revision used for the setup. Menu wording can change between software releases.
- Prove the camera image locally. Confirm exposure, colour, focus, motion, frame rate, and the intended audio before transport troubleshooting begins. A bad source remains bad after SRT recovery.
- Create the receiving endpoint. In Callaba, create and start an SRT server in Listener mode. Reserve a unique UDP port and restrict inbound access to the production networks wherever possible.
- Configure the FR7 stream. Select SRT, choose Caller, enter the Callaba destination, and keep the stream on H.264. Apply the agreed encryption and latency settings rather than carrying values from an unrelated camera profile.
- Start one clean path. Confirm that the camera reports an established session and that Callaba sees a sustained incoming publisher. Avoid changing codec, latency, mode, and firewall rules at the same time.
- Decode the result. Place the source in Callaba Multiview or create a short recording. Inspect motion, audio, sync, and image continuity. Transport status alone cannot prove that viewers will receive usable media.
- Add downstream work only after proof. Attach routing, recording, restreaming, or an alternate contribution path one change at a time, with an operator-visible result for each change.
Use the FR7 where a remotely operated camera changes the job
Remote stage and studio camera
Place the FR7 where a local camera operator is impractical, retain remote pan/tilt/zoom and cinematic framing, and send the program-ready contribution to a central operator. The transport and camera-control networks should be documented separately even when they share infrastructure.
House of worship or performance venue
Use a compact camera position for a lectern, stage, or balcony angle. Multiview lets the remote team verify composition and continuity while Callaba recording preserves a contribution copy for review or later delivery.
Distributed multi-camera production
Give each FR7 a distinct endpoint and operator-facing label. Prove every feed separately before arranging them into a wall or routing them toward a switcher. A shared naming convention matters more than decorative endpoint names during a live fault.
Controlled local-network production
When all systems are on a managed LAN, RTSP or NDI HX2 may be relevant alternatives. Choose the path because its codec, latency, control, and receiver model fit the production—not because multiple protocol names appear on the camera specification.
Run an acceptance test that resembles the event
- Operate pan, tilt, zoom, focus, and a scene with real motion while watching the decoded Callaba tile.
- Listen to the selected audio path and check lip-sync rather than treating picture alone as success.
- Observe session continuity and the incoming transport information for several minutes on the production network.
- Make a short recording and play it back. Confirm expected resolution, frame rate, audio, duration, and seek behaviour.
- Interrupt the camera network deliberately. Record how quickly the session disappears, what the operator sees, and what action restores it.
- If an alternate camera or route exists, exercise the actual switch procedure and verify every downstream destination after recovery.
Troubleshoot the layer that is actually failing
No SRT session appears
Check that Caller and Listener are complementary, the Callaba endpoint is running, and the host and UDP port are reachable from the camera VLAN. Test DNS from the production network rather than from an engineer's laptop on another path.
The connection is rejected
Compare AES mode and passphrase exactly. A reachable listener can still reject a session when the security contract differs. Retype the secret at both ends instead of copying it through a formatted document.
The session connects without a picture
Return the SRT output to H.264 and verify the source format. Do not infer SRT H.265 support from the FR7's RTSP capabilities. Prove the camera output locally, then inspect decoding on the receiving side.
Motion breaks up on the real venue link
Compare the chosen media rate, route capacity, jitter, loss, and SRT latency budget. Increase latency only when measurements show that recovery needs more time; it is not a cure for persistent congestion or an undersized uplink.
Local IP video works but SRT does not
NDI HX2 or RTSP success proves the camera and LAN path, not the external SRT firewall and role agreement. Trace the SRT connection separately from the local discovery/control network.
The team expects ST 2110 from SFP+
Stop and correct the architecture. The FR7's optical SFP+ SDI path is not a native ST 2110 endpoint. Specify the required gateway or use an interface that the receiving facility actually supports.
Official Sony references
Verify the installed camera against Sony's current documentation before a production change. The primary sources for this workflow are the official ILME-FR7 Help Guide streaming settings and ILME-FR7 Help Guide SRT settings. Use the guide that matches the deployed software and region; supported values are more reliable than remembered settings from another Sony camera.
Prove one FR7 contribution before the production grows
Build one identified SRT session, verify the decoded camera and audio in Multiview, and rehearse the network failure. Once that baseline is visible, recording, routing, and additional camera paths become deliberate additions rather than guesses.
Explore Callaba SRT Server
