How ONVIF WS-Discovery Works
ONVIF auto-discovery is based on the WS-Discovery protocol. SmartRTSP sends a UDP multicast probe packet to the address 239.255.255.250 on port 3702. Every ONVIF-enabled camera on the same network segment that receives this probe responds with its device information and service URLs.
Because multicast packets do not cross subnet boundaries by default, both your iPhone and the camera must be on the same IP subnet for discovery to work. Several network configurations — VLANs, separate wired/wireless networks, firewall rules, AP isolation — can silently block discovery probes.
Common Causes & Fixes
Subnet mismatch — iPhone and camera on different subnets
The most common cause. Many routers separate wired devices (192.168.1.x) from wireless devices (192.168.2.x) into different subnets, or cameras connect to a NVR on a separate VLAN. UDP multicast does not cross subnets without special configuration.
Firewall blocking UDP port 3702 or multicast traffic
Some routers and managed switches block multicast traffic between client devices, or have explicit firewall rules preventing UDP port 3702. The block happens silently — SmartRTSP sends the probe but never receives a response.
ONVIF disabled in the camera settings
Many cameras ship with ONVIF disabled by default, or require a separate ONVIF user account to be created before WS-Discovery responses are sent. The camera is on the network but will not respond to discovery probes if ONVIF is off.
AP isolation on Wi-Fi networks
Some routers enable AP isolation (also called "client isolation") by default on the wireless network. This prevents Wi-Fi clients from communicating directly with each other, which blocks the multicast discovery packets that ONVIF depends on.
Network isolation behind NVR or PoE switch
Cameras connected to a standalone NVR or an isolated PoE switch may be on a private subnet (e.g., 192.168.254.x) that the NVR manages internally. These cameras are not visible on the main home network at all.
Where to Find ONVIF Settings
| Camera Brand | ONVIF Setting Location | Notes |
|---|---|---|
| Hikvision | Configuration → Network → Advanced → Integration Protocol | Must create a separate ONVIF user |
| Dahua | Setting → Network → ONVIF | Enable and add an ONVIF user |
| Reolink | Device Settings → Network → ONVIF Port | Enable ONVIF; default port 8000 |
| Amcrest | Setup → Network → ONVIF | Enable protocol; usually on by default |
| Axis | System → ONVIF | Enabled by default; create ONVIF account |
| TP-Link Tapo | Advanced → Camera → ONVIF (newer firmware) | Use RTSP URL directly on older firmware |
| Foscam | Settings → Network → ONVIF Settings | Enable and set ONVIF port |
Manual IP Entry — Always Works
ONVIF auto-discovery is a convenience — it is not required to use SmartRTSP with your cameras. If discovery continues to fail after trying the fixes above, adding cameras manually using their RTSP URL is a reliable alternative that works regardless of network configuration.
Find your camera's IP address
Check your router's device list, the camera's web interface, or the camera manufacturer app. The IP is typically in the 192.168.x.x range.
Find the RTSP URL for your camera
Look up your camera brand in the camera setup guides or check the manufacturer's documentation. The URL format is typically rtsp://username:password@192.168.x.x:554/stream.
Tap + → Manual Entry in SmartRTSP
Enter the full RTSP URL and tap Connect. The camera will be added to your list without needing ONVIF discovery to work.
Frequently Asked Questions
What port does ONVIF WS-Discovery use?
My camera is on the same Wi-Fi but still not found
Can I use SmartRTSP without ONVIF discovery?
Why does discovery work on Android but not iPhone?
Download SmartRTSP Free
ONVIF auto-discovery and manual RTSP entry — both available free for iPhone, iPad & Mac.