Separate G-Cam generation from G-Core services
The E5 connection documentation distinguishes the camera’s control connection from RTSP video. Other G-Cam families have their own manuals and supported stream settings. Match the complete product code instead of borrowing an address from a similarly named camera.
G-Core also offers server-side streaming services. If your supplied address belongs to a server, ask which camera channel it represents and which server account is authorized. Do not replace that endpoint with a camera example or assume that a camera password authenticates to the server.
Prepare a direct G-Cam viewing connection
- Identify the camera model, firmware and local IP address. Confirm that you are connecting to the camera itself rather than a G-Core host.
- Use the matching camera instructions to sign in and check the current local account. Replace historical default credentials as required by the installation.
- Inspect the enabled media profiles, video compression and configured RTSP port. Port 554 is documented for the cited E5 integration, but verify the actual device setting.
- Obtain the exact stream URI from the model documentation, camera interface or supported ONVIF media profile. Do not guess a path from the port number alone.
- Add the URI and authorized viewing credentials to SmartRTSP. Confirm a moving image, close and reopen the view, and then test any separately required control or audio function.
Check model-specific profiles and compression
The HFD-1430 datasheet lists multiple configurable streams and ONVIF profiles for that particular camera. Those specifications are useful when selecting a stream, but they do not turn every older G-Cam generation into the same device.
For a camera grid, inspect an already enabled lower-bandwidth encoder before changing the main recording stream. Note whether the selected profile uses H.264, H.265 or MJPEG, and confirm that the actual picture appears correctly in the installed viewer.
Troubleshoot the correct endpoint
| Situation | Next check |
|---|---|
| Camera web interface works but RTSP is unauthorized | Verify local viewing rights and the account accepted by the camera’s stream service. |
| G-Core address fails with a camera password | Check the server’s own authentication and channel mapping. |
| Connection succeeds without the expected image | Check the requested media profile, encoder and physical sensor. |
| PTZ or analytics is missing | Verify each function separately; video transport does not establish control or metadata compatibility. |
Check each feature independently
Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.
Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.
Frequently Asked Questions
Is port 554 enough to construct a G-Cam URI?
No. The port identifies a service, while the resource path identifies a stream. Obtain the latter from the matching camera documentation or profile.
Can I use a G-Core server URL directly on the camera?
No such substitution is established. Server output and direct camera output are different endpoints with separate settings.
Does this guide certify every G-Cam model?
No. Sources were checked on 2026-10-18. Physical operation and optional features remain model-specific checks.
Official sources and scope
Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.