• TCP is used for two way communication and UDP will be used for broadcasting protocols.
• HTTP is used for the ONVIF protocol as transport mechanism for SOAP calls.
• FTP can be used to push alarm buffer video clips to a specified remote FTP server. The camera can use
anonymous FTP or a specified username and password. There is no incoming FTP service.
IP multicast RFC 1112 level 1 support for sending but not receiving multicast IP datagrams to a group of
interested receivers in single transmissions is supported for audio, video and metadata stream types. The
streams can be controlled using the two methods described below:
1
A client can request a multicast stream using RTSP. When the client requests a stream the server will
respond with a multicast address in the ‘c=’ field of the describe response (RFC 4566). The client will
then respond with a Setup request with the Transport Type set to multicast, the device shall stop sending
packets for a multicast configuration when no more RTSP sessions are using the same multicast con-
figuration.
2
An RTP multicast UDP stream can be started by an ONVIF ‘StartMulticastStreaming’ request with a
specified media profile. Streaming continues until ‘StopMulticastStreaming’ is called for the same profile
Multicast RTSP sessions support the same authentication methods as unicast RTSP sessions.
Network Address Configuration
•
Dynamic Host Configuration Protocol (DHCP)
is enabled by default on the camera on initial camera
startup, and after a hardware factory reset, and remains enabled until the camera receives either a
DHCP address or is assigned a Static IP address. If no connection is made to a DHCP server within
two minutes, the camera goes to the default IP address 192.168.1.168, but continues to search for a
DHCP address. If the camera is assigned a Static IP address prior to DHCP being enabled, the camera
first reboots for approximately 30 seconds and then remains accessible at its Static IP until a
connection is made to a DHCP server.
•
Static IP
can be used if the camera cannot be found on the network using DHCP. In this mode, a static
IP address, subnet mask, default router and a primary and secondary DNS server can be configured.
This will be used by the camera when turned on. It is possible to assign a static IPv4 address while still
allowing the IPv6 addressing to be Link Local (automatically assigned).
•
Dynamic DNS or DDNS Dynamic Domain Name System
is supported for updating, in real time a
changing IP address on the Internet to provide a persistent domain name for a resource that may change
location on the network. RFC 2136 Dynamic Updates in the Domain Name System. In this situation the
camera talks only to the DHCP server and the DHCP server is responsible for updating the DNS server.
The camera sends its hostname to the DHCP server when requesting a new lease and the DHCP
server updates the DNS records accordingly. This is suitable for an intranet style configuration where
there is an internal DHCP and DNS service and the user wants only to access their camera within their
own network.
By default, when making a DHCP request the camera will transmit its hostname as part of the DHCP request.
This option is not user configurable. The cameras hostname matches the configurable parameter “camera name”
on the Web User Interface. Any DHCP request will contain the cameras hostname for use of the DHCP server to
forward to an appropriate DNS server.
Network Name Resolution
The camera uses DNS protocol to resolve network names. DNS server address will be acquired via DHCP or
manually set for static IP configuration. Camera configuration supports symbolic names for all remote end-points
(except DNS servers) but in this mode will depend on a working and correctly configured remote DNS server.
114
