The call comes a week after the keys have been handed over. The cameras are showing pictures at the site, the recorder is still storing footage, and the customer’s phone now says the system is offline.
That situation is easy to treat as a camera fault. The remote-viewing path has more points of dependence than the image itself, though. The customer’s account, the recorder’s local network address, the site router, the internet connection, any access rules, and the platform used to reach the site all have to line up.
For a CCTV installer, that changes what a good handover looks like. The job is not finished when every camera appears on the monitor. It is finished when the customer can use the agreed remote path, recover access without calling you for every password problem, and explain what to check before reporting a fault.
Start with the route to the video
A camera can continue producing a picture while remote viewing fails elsewhere in the system. Local display, local recording and remote access are separate checks. They may share equipment, but they do not prove the same thing.
That gives the installer a useful first question: can the customer still see the site from inside the premises?
- If the local display works, the cameras and at least part of the recorder path are available.
- If local display fails as well, begin with power, cabling, the recorder and the local network before investigating remote access.
- If local viewing works but the mobile app fails, keep the camera hardware out of the first line of investigation. Check the account and the path between the customer’s device and the site.
This distinction also prevents a common handover problem: the customer describes the whole system as “down” when only one access path has failed. Ask what the customer can see locally, what the app displays, whether another authorised user can sign in, and whether the failure occurs on the site’s Wi-Fi, a mobile network, or both.
Once the failed path is isolated, the next check is the site’s network boundary.
Check the site address before changing the cameras
Remote access needs a way to find the site and reach the service or device that provides the video. The address visible inside the customer’s network is not automatically the address visible from the wider internet. The route can also be affected by the customer’s router, upstream network, firewall policy or remote-access platform.
Carrier-Grade NAT is one specific boundary to look for. RFC 6888 defines CGN as a NAT-based function that shares one IPv4 address among multiple subscribers. The customer does not manage that translation layer. As a result, a local router configuration cannot by itself give the installer control over every address or connection between the site and the internet.
Do not diagnose CGN from a vague “the IP changed” report. Record what the router shows as its internet-facing address and compare it with the public address observed from the site. If the two do not match, ask the internet provider whether another NAT layer sits upstream. A router address in the shared address space allocated for customer-to-CGN interfaces is another reason to investigate the provider path rather than repeatedly changing the recorder. The protocol side of this boundary is covered in NAT Traversal in WebRTC: Why the Call Connects on Wi-Fi but Not on 4G.
The handover record should state which remote method was configured. It might be a manufacturer platform, a site-to-site connection, a direct connection through the customer’s router, or another service. The recovery steps differ between them. A customer who only receives “check the internet” has no useful next action.
With the network boundary recorded, test the part of the path that the customer actually uses.
Test the customer’s phone on two networks
A remote-viewing test on the installer’s phone, connected to the site Wi-Fi, proves very little. It can succeed because the phone is already inside the local network. The customer normally needs the app to work away from the premises, so the handover test should include a second network.
- Sign in on the customer’s device using the account that will remain with the customer.
- Confirm that the intended cameras or recorder appear in the account.
- View live video while the phone is on the site Wi-Fi.
- Turn Wi-Fi off and repeat the test over the mobile network.
- Close and reopen the app, then confirm that the account still reaches the same site.
- Ask the customer to perform the test while you observe the result rather than doing every step for them.
The point of the second network is diagnostic. If local Wi-Fi works and mobile access fails, the problem is probably in the path beyond the local network or in the platform’s remote-access arrangement. If both fail, check the account, recorder connectivity and service status before looking for a fault in an individual camera.
Record the test date, the device used, the two connection types and the result. Avoid storing a customer’s password in the installation paperwork. Give the customer a recovery route and explain which account owns the site.
The app test exposes the route. The next handover task is making sure the customer can recover the human part of that route.
Make the account recoverable before leaving
A forgotten password is a support call with a simple technical cause and a potentially awkward resolution. The installer may be asked to “reset the CCTV,” even when the cameras and recorder are operating normally.
Before handover, identify the account used for remote viewing, the email address or phone number attached to it, and the person responsible for receiving recovery messages. Let the customer sign out and sign back in. Then show the recovery process without taking ownership of the account yourself.
- Use the customer’s email address or phone number where the platform requires one.
- Confirm that the recovery destination is accessible to the customer.
- Explain the difference between the app account password and any local recorder or administrator credential.
- Give the customer a written record of the account identifier, without leaving reusable passwords in an open handover sheet.
- State who should be contacted if the recovery email or phone number changes.
Keep the customer’s account separate from the installer’s test account. Shared credentials make later troubleshooting harder because nobody can tell which user changed a setting, removed a site, or triggered a security check.
That separation also makes the next call easier. You can ask the customer to describe the exact screen and account involved instead of beginning with a full system reset.
Show what a recorder-offline message means
Customers often use “the cameras are offline” to describe several different conditions. The app may have lost contact with the remote platform. The recorder may have lost its network connection. The recorder may have power but no route to the internet. A single camera may be unavailable while the rest of the site remains visible.
Give the customer a small vocabulary during handover:
| What the customer sees | First check | What to report |
|---|---|---|
| No cameras and no recorder in the app | Whether the site has power and internet access | Time of failure and whether local viewing works |
| Recorder appears offline | Recorder power, network cable and router status | Whether other devices at the site have internet access |
| One camera is missing | Camera power, cabling and the local recorder view | Camera name or channel and whether it is visible locally |
| Login fails | Account identifier and recovery route | The exact sign-in message, without sending a password |
The table is a triage aid; each platform words its messages differently. Ask the customer to send a screenshot of the message and the time it appeared. A timestamp helps you separate a current outage from a stale notification left on the phone.
Some systems support local or edge recording while contact with a remote service is lost. That behaviour belongs to the particular system and configuration, so explain it only after verifying it during commissioning. Do not promise that a remote-viewing outage means recording has continued unless the installed system has demonstrated that capability.
After the customer understands the symptoms, explain the boundaries that can sit outside the installer’s equipment.
Explain the parts of the route you do not control
A customer needs a clear owner for each dependency. The installer may control the camera configuration, recorder configuration and commissioning test. The customer may control the account and premises access. The internet provider controls the upstream connection. A remote-access platform may control the service that helps the app find or reach the site.
Write those boundaries into the handover sheet. Use plain language:
- “The cameras and recorder are visible locally.”
- “Remote viewing was tested from this phone over the site Wi-Fi and a mobile network.”
- “The site internet connection is supplied by the customer’s provider.”
- “If the router or internet service is replaced, remote viewing needs to be tested again.”
- “If the account recovery number changes, update it before the old number is disconnected.”
Do not turn this into a list of exclusions that leaves the customer stranded. Give the customer a first action and a useful escalation path. For example, check whether the site has power, check whether another device can use the internet, capture the app message, and then contact the named support person.
This is also where a service agreement can be precise. It can define whether the installer checks the remote path after a customer-router replacement, whether account recovery is included, and which network faults belong with the internet provider. Clear boundaries are easier to price than an undefined promise to keep remote viewing working forever.
Browser viewing is a separate request. If a customer later asks to watch the cameras in a web page instead of the app, the existing recorder and cameras shape that project. You’re Never Greenfield covers what it costs, Where to Tap the Stream covers where to take the feed, and Live Video in Surveillance explains why RTSP cameras cannot feed a browser directly.
Once those boundaries are documented, the installer can reduce repeat calls without pretending to control the whole route.
Leave a handover record that can be used later
The useful handover document is short enough to open during a support call. It should contain the information needed to reproduce the original test:
- Site name and address.
- Recorder identifier and the cameras or channels included in remote viewing.
- Remote-access method and account owner.
- Customer device used for the acceptance test.
- Result on site Wi-Fi and on a mobile network.
- Router or internet-provider details supplied by the customer.
- Recovery contact and the date it was verified.
- What the customer should check before calling.
Do not include secrets that the customer should change or that would let anyone reading the sheet take over the system. Store privileged credentials through the agreed secure process. The handover record describes the configuration and the recovery route. Passwords belong in the secure store.
When the next call arrives, start with the last known good test. Ask what changed: the phone, account, router, internet service, power, recorder or camera. That question narrows the search much faster than asking the customer to restart everything.
Bottom Line
Treat a post-handover remote-viewing call as a path problem until local viewing says otherwise. Test local viewing and off-site viewing separately, check the account and network boundary, and record exactly what worked at handover.
A clear handover cannot prevent every outage. It can show the customer what to check, show the installer which dependency changed, and keep a remote-access problem from becoming an unstructured call about the entire CCTV system.
What's Next
The technical path explains what can fail after handover. The commercial question is why the customer brings that failure to the installer in the first place. Read Why Your Client Calls You, Not the Camera Brand for the responsibilities and support expectations that sit behind the call.
FAQs
What are common CCTV installer support calls after handover?
Typical examples include remote viewing that no longer works, an account that cannot be accessed, a recorder that appears offline, or one camera missing from the app. Each one is worth testing and documenting at handover.
Why does CCTV remote viewing work on Wi-Fi but fail on mobile data?
The phone may be reaching the recorder through the local network on Wi-Fi while the off-site route is failing over mobile data. Test both networks separately and check the account, recorder connectivity, router path and remote-access platform before changing camera settings.
How can a CCTV installer check for Carrier-Grade NAT?
Compare the internet-facing address shown by the site router with the public address observed from the site, then ask the internet provider whether another NAT layer is upstream. RFC 6888 describes Carrier-Grade NAT as address sharing among multiple subscribers, so the customer cannot assume that the router controls the full path to the internet.
What should be included in a CCTV handover checklist?
Include the remote-access method, account owner, recovery contact, recorder and camera identifiers, the result of local and off-site tests, and the first checks for a future outage. Keep passwords and other privileged secrets out of an ordinary handover sheet.
Should an installer promise that recording continues when remote viewing fails?
Only if the installed system has a documented and tested local or edge-recording function. Remote access can fail independently of local recording in some configurations, but that behaviour is not universal across recorders and should not be promised without verification.
Who is responsible when a customer’s router is replaced?
The answer belongs in the service agreement and handover record. The installer can define whether post-replacement remote-access testing or reconfiguration is included, while the customer or internet provider may own the router and internet service themselves.
Should CCTV installers give customers their own remote-viewing account?
Yes. The customer should own the account used for normal remote viewing, with a recovery email address or phone number they control. Keep installer testing separate so support work does not depend on a shared credential or on the installer remaining the account owner.