Freeze one failed video path
Record the exact manufacturer, model, hardware label, package, installed firmware and Android state. Identify whether the camera is built in, an optional USB accessory or absent from the SKU. Capture the calling application, SIP account, peer, direction, timestamp and whether the failure is no self-view, no transmitted video, no received video, frozen video, wrong camera or an audio-only answer.
Do not begin with a codec reset. A missing optional camera, closed privacy shutter, Android permission, application choice, SIP offer, remote answer and RTP path are different failure layers.
Prove the camera and visible privacy controls
Inspect the physical camera and its state with the user present. The Grandstream GXV3480 and Fanvil V67 document built-in cameras with privacy shutters. Yealink documents CAM50 as a USB accessory for the T58W series, with an indicator and privacy shutter; a T58W Pro base phone, camera-capable firmware or product-family photograph does not prove that CAM50 is installed or part of the exact package.
Confirm the approved camera is connected to the documented port, powered, enumerated and available in local self-view. Check shutter, tilt and indicator without bypassing a privacy control. A working self-view proves local capture only, not that an application may use it or a call transmits it.
Identify the application that owns video
State whether the call uses the native SIP phone application, a permitted Android application, a door-phone preview, HDMI path or another workflow. Capture the selected application version, account, camera permission and foreground state. Stop or remove an unapproved application only through the deployment owner; do not grant broad camera, microphone, storage or administrator access as a diagnostic shortcut.
Grandstream documents Android 14 on current GXV34x0 material, while Fanvil V67 and Yealink T58W Pro material identify Android 9.0. An application that worked on one device family or earlier build is not proof of compatibility on another. Preserve the exact package and permission state.
Trace SIP offer and answer separately
For native SIP video, correlate one sanitized INVITE transaction and inspect the video media description on both legs. Record whether a video m= line exists, its port, direction attributes, payload types, H.264 profile or packetization details where present, the selected codec and the answer. An audio-only answer can be a negotiated result rather than a camera fault.
Grandstream's user flow offers separate Video and Audio answer choices, and Yealink publishes H.264 and VP8 for CAM50 workflows. Do not force a codec merely because both datasheets list it; the PBX, peer, application and each call leg must agree on the effective offer and policy.
Follow the negotiated media to both endpoints
After a video stream is accepted, compare signaled media addresses and ports with observed packets in each direction. Check VLAN, firewall, NAT, SBC anchoring, bandwidth and packet loss without conflating video with the working audio stream. One-way video means at least one capture or decoding path worked; it does not prove the reverse address, authorization or decoder state.
Use the narrowest authorized capture and protect images, names, room views, contact data and signaling identifiers. A TLS control on SIP does not prove SRTP on video, and SRTP on one leg does not prove end-to-end protection beyond a PBX or SBC.
Check provisioning and firmware ownership
Compare the running camera, video, application and codec settings with the authoritative provisioning profile. Determine whether a recent firmware or application change reset permissions, removed an allowed package, changed defaults or requires reprovisioning. Use manufacturer release notes and the deployment's change-control process before changing branches.
Grandstream's current GXV34xx firmware page documents a factory reset when moving from 1.0.3.x to 1.0.5.x and blocks some downgrades. That boundary makes a blind upgrade or downgrade an unsafe diagnostic step. Preserve configuration, pilot one representative device and keep the accepted image and rollback procedure explicit.
Verify one correction on and off target
Correct only the demonstrated owner: install or reconnect the approved camera, open an authorized shutter, restore one application permission, select the intended native or Android client, correct one provisioned setting, allow one negotiated video format or repair one media route. Repeat local preview, outbound video, inbound video, audio-only fallback and an unrelated call that must remain unchanged.
Remove temporary logging and captures, restore privacy state, and record the final model, firmware, package, account, offer/answer and media result. Follow the provider-approved emergency testing procedure separately; a video result does not validate emergency calling. No phone, application, camera, PBX, provider, signaling exchange, media stream or call was tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Grandstream GXV3480 product page ↗
- Grandstream GXV34x0 user guide ↗
- Grandstream GXV3480 quick user guide ↗
- Grandstream GXV34xx official firmware ↗
- Fanvil V67 product page ↗
- Fanvil V67 April 2025 datasheet ↗
- Fanvil V67 user manual ↗
- Fanvil V67 firmware index ↗
- Yealink SIP-T58W Pro with Camera datasheet ↗
- Yealink CAM50 datasheet ↗
- Yealink SIP-T58W Pro with Camera product page ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.