Help sales, the integrator and the customer get one outcome. In the channel model that means making the partner look good, not going around them.
Study guide · Axis Communications
Axis bet that security belongs on the network.
Everything else they make follows from that bet. This page puts the whole picture in one place: the company, its products, the technology from all 45 Academy videos, and the networking you need to explain it.
If someone asks “So what does Axis do?”
Axis makes network devices for security and operations: cameras first, then speakers, door controllers, intercoms, radar and environmental sensors. Every one of them is a node on an IP network.
Its sales pitch is better evidence for less bandwidth and storage (Zipstream, AV1, differentiated streams), image quality where light is scarce (Lightfinder, larger sensors, Forensic WDR, thermal), and video that can be trusted (Axis Edge Vault, Signed Video). It sells through partners rather than direct, and it pushes open standards (VAPIX, ONVIF, SIP) so integrators can build on it.
- PoE reach
- 100 mStandard twisted pair
- PoE over coax
- 500 mReuse old analog cable
- PoE over 2-wire
- 220 mElevator traveling cables
- Modular camera
- 30 m · 4Sensor-to-main-unit run, sensors per unit
- Storage profile
- ≈50%Extra saving from Zipstream B-frames
- Thermal
- <0.1 °CTemperature difference it can see
- Air sensor
- 0.1 µgSmallest particle measure quoted
- Panoramic
- 180–360°Coverage from one camera
- Sizing rule
- 10.8 GB1 Mbps recorded for 24 h
- Jitter
- 50 vs 60 HzMatch the monitor to the stream
Interview prep
What they're testing, and how to show it
A sales engineer interview at Axis checks three things: can you put a camera on a network and explain why the stream works, can you turn a customer's problem into a design, and will you tell the truth while doing it. Everything else on this page supports one of those.
The job
- The technical half of the sale. You back the sales team on deals, credible enough for integrators and system architects. You sell, you don't code.
- Problem → products. Translate what the customer needs to prove into an Axis design (see system design).
- Demos, technical proposals, RFQ scoping. Answer “how does it work?” and “can it do X?” without a datasheet in your hand.
- Success = technical credibility + commercial awareness + plain language.
- Interviewer named in your notes: Filip Johansson.
How Axis interviews
- Real examples, not theory dumps. Be specific and stay on the role.
- After the first conversation there's often a case, a panel, or a manager's-manager round.
- Technical rounds test DHCP, NAT, VLANs, port forwarding through customer scenarios. A reported question: “You can open a link at work but not from home. What's wrong?” (answer).
- “I don't know. Here's how I'd find out” is a strong answer here. Never bluff a model suffix or a bitrate.
Values: say them, then show them
Vision: “Innovating for a smarter, safer world.”
Axis co-founded ONVIF and works with any VMS. In a person, the same value means telling the truth: “Axis isn't the cheapest box,” “I was wrong,” “I'd check the datasheet.”
First network camera (1996), its own ARTPEC chip, Zipstream, radar-video fusion, first in the industry with AV1. Use it to answer “why Axis?” in two sentences.
The values and vision are Axis's own wording. The “show it with” suggestions are interpretation.
Study map: the Axis Certified Professional exam
Axis's own certification for designers and technical sales is a better guide to what matters than any generic interview list. Each bar links to where that area is covered.
Night-before plan
| Block | Time | What | Where |
|---|---|---|---|
| 1 | 40 min | Product lines, naming, the five inputs | Decoder · Five inputs |
| 2 | 50 min | TCP/IP, subnets, NAT, ports, TCP vs UDP | Networking |
| 3 | 30 min | Image physics, Zipstream numbers, pixel density | Library · Zipstream · Density |
| 4 | 20 min | ONVIF, RTSP, VMS, competitors | ONVIF · VMS · Company |
| 5 | 25 min | Say the sales engineer answers out loud | Practice questions |
| 6 | 15 min | Fill in the STAR stories below | STAR |
| 7 | – | Read the cheat sheet. Sleep. | Cheat sheet |
Short on time? Product lines → TCP/IP → pixel density and the Zipstream night number → say the answers out loud.
Your STAR stories
Situation, Task, Action, Result, then one sentence on what you learned. These have to be your stories. Notes save in this browser only.
A tough customer, where you protected the outcome rather than the invoice
Use for: “Tell me about a time you turned down a deal.”
You worked with sales and someone else to close
Use for: “How did you work with a team to win a deal?” Shows Act as One.
You were wrong and said so
Shows Always Open. Keep the mistake real and the fix concrete.
A network problem you diagnosed
DHCP, NAT, VLAN, “works at work but not at home.” Proves the technical half.
Morning cheat sheet
- Handshake: SYN → SYN-ACK → ACK
- Ports: 80, 443, 554, 3702, 1900, 5353
- Same subnet = switch · other subnet = gateway · internet = NAT / VPN / cloud
- Live = UDP/RTP · config and recording = TCP/HTTP
- P workhorse · Q premium / PTZ · M indoor density · F modular
- -LVE = LED illumination · vandal-resistant · outdoor-ready. Last digit = resolution (5 = 1080p)
- Identify = 250 px/m · recognize 125 · detect 25
- Night: H.264 ~5.4 Mbps → Zipstream ~0.9 Mbps
- Blur = shutter, not FPS
- ONVIF S streaming/PTZ · T advanced streaming · M metadata
- 1 Mbps × 24 h ≈ 10.8 GB
- PoE++ for Q / PTZ · cameras on their own VLAN
- Edge Vault · Hardening Guide · NDAA · own ARTPEC chip
- Act as One · Always Open · Think Big
- “I don't know. Here's how I'd look it up.”
The company
Who Axis is and how it makes money
The Academy videos teach technology and say almost nothing about the company itself. This section fills the gap with widely reported background, so check the figures on axis.com before quoting them.
Background, not from the videosFounded in Lund, Sweden. Its first products were print servers and protocol converters, so it knew networking before it made a single camera.
Launches what is widely credited as the world's first network camera. That product is the start of the whole IP-video industry.
Designs its own chip, ARTPEC, and keeps doing so. ARTPEC-9 is the current generation and is what enables AV1 (see topic 07).
Co-founds ONVIF with Bosch and Sony, the vendor-neutral standard that lets different brands' cameras and software work together.
Acquired by Canon and later delisted from Nasdaq Stockholm. It still runs as a separate company from its Lund HQ. Canon also owns Milestone (VMS software), which makes Milestone a sister company to Axis.
Buys 2N (Czech intercom and access maker), plus the analytics firms Citilog and Cognimatics.
The sales channel
Axis doesn't sell to end users directly. The Academy exists to train other companies' staff until they know Axis well enough to specify it in the next tender. That's why the cybersecurity video ends with “help our partners.” A sales engineer's job sits in the middle of this chain, supporting integrators and end-customer design meetings. The real output isn't a shipped camera; it's a partner who can win a tender without you in the room.
Software and platform names
- AXIS OS: the firmware running on the devices
- AXIS Camera Station: Axis's own VMS (video management software)
- ACAP: Axis Camera Application Platform, for third-party apps that run on the camera
- VAPIX: Axis's open HTTP API
- Axis Cloud Connect: hybrid cloud platform (topic 10)
Who they compete with
| Competitor | Where they sit | How Axis usually argues against them |
|---|---|---|
| Hikvision, Dahua | High-volume, low-price Chinese makers | Cybersecurity, supply-chain trust, and in the US, NDAA Section 889 restrictions that bar them from federally funded projects |
| Hanwha Vision | Korean; broad range, strong on price and performance | Breadth of the ecosystem (audio, access, radar), Edge Vault, product lifecycle |
| Bosch | European; strong in enterprise and critical infrastructure | Similar positioning, so it comes down to features, partner support and image quality |
| Motorola Solutions (Avigilon, Pelco) | Sells end-to-end systems with its own software | Openness: Axis works with any VMS rather than locking customers into one |
| i-PRO (ex-Panasonic) | Japanese; quality-focused | Portfolio breadth, partner network |
Product naming tip: Axis model names start with a letter that tells you the line. For cameras, M is the value range, P is the mid-range professional line, and Q is premium. The videos name the P13 (popular fixed line), Q6034E / Q6155E (PTZ), and Q29 (thermometric). The full model-name decoder is under What they sell. Check any model number before using it with a customer.
How Axis thinks
Six ideas that explain most of the catalogue
These ideas come up in video after video. If you understand them, you can predict what Axis will say about almost any product.
A camera is a one-off purchase, but it records forever. The bytes it produces are a permanent cost, so compression gets more airtime than any camera line.
Zipstream keeps detail where people and motion are and compresses the background harder. The storage profile adds B-frames for roughly another 50%. Average bitrate keeps storage predictable. AV1 is the next codec. And for 4K you don't need a new network, just differentiated streams.
A sensor only receives so many photons, and every optics video is about how to spend them. Notice that Axis doesn't chase megapixels: packing more pixels onto the same sensor means each one catches less light, which means more amplification and more noise. The answer is a bigger sensor.
Motion blur comes from shutter speed, never frame rate. A constant aperture stops the picture getting darker as you zoom. Forensic WDR deliberately looks a little unnatural so it keeps detail in both highlights and shadows.
Once footage is used as evidence, the hard question is whether it's authentic, not how good it looks. Axis Edge Vault stores a factory-issued identity and keys in hardware and will only boot Axis-signed firmware. Signed Video uses those keys to sign every frame. The video isn't encrypted, so any player still opens it, but software that understands the signature can prove nothing was edited.
Radar, thermal, thermometric, acoustic and air-quality sensors either produce no video or aren't built for identifying people. The common thread is putting sensors on the network and turning what they detect into events. The camera is now one sensor among many.
The acoustic sensor never streams or stores audio; only metadata leaves the device. Radar can go where cameras aren't allowed. For schools, hospitals and city spaces, these limits are presented as selling points.
VAPIX, ONVIF, SIP and free SDKs keep the platform open. Cloud Connect is hybrid so existing on-premises customers aren't left behind. Analytics run in the device (object classification, deep learning in intercoms, sound recognition), which saves bandwidth, keeps working through network outages, and makes the hardware worth paying for.
Commercial angle
How the technology turns into deals
The previous section explains what Axis believes. This one explains why those beliefs make money, which is the conversation a sales engineer actually has. It's interpretation, not something Axis states, so test it in the interview rather than presenting it as fact.
The cameras aren't the moat. The channel is, and Axis holds it with education rather than margin.
Audio, access control, radar, air quality and intercoms all run on network infrastructure the customer has already paid for, sold by an integrator Axis already works with. The expensive part of the sale happened with the first camera.
The installed base is also unusually sticky: it's physical infrastructure that lasts about ten years.
Zipstream gets three videos, more than any single camera line. The reason: the camera is bought once, but storage is paid for every year. At 4 Mbps, 100 cameras kept for 30 days need about 130 TB. Halving that is worth more than a hardware discount, and the saving comes back every year.
Zone/Division 1 and 2, Arctic Temperature Control and onboard vehicle cameras all have the same barrier to entry: certification and liability, not clever engineering. Buyers choose on compliance, not price. A scratch on a Zone 1 flame path ruins the protection, so even installation needs certified staff.
Sensors that record no footage can be sold to buyers who can't or won't buy surveillance: facilities, health and safety, and sustainability teams. Those are different decision-makers with different budgets.
What they sell
The product families
Click a topic number to jump to its notes in the library.
Network cameras
Fixed, PTZ, panoramic (180–360°), modular (small sensor heads up to 30 m from the main unit), onboard for vehicles, and hazardous-area models.
Network audio
All-in-one IP speakers with the amplifier and DSP built in. Used for security talk-down, public address and background music. Each speaker tests itself with a built-in microphone.
Access control & intercoms
Network door controllers, readers, I/O modules and video intercoms. Credentials include RFID cards, phones over Bluetooth, vehicles and QR codes. Controllers keep working offline.
Radar & fusion
Radar measures range and direction regardless of light, weather or insects. Radar-video fusion adds a camera, so radar detects early and video classifies up close.
Thermal & thermometric
Thermal sees heat, not light, and detects people in total darkness. Thermometric models are calibrated to measure temperature, for fire prevention and machine monitoring.
Environmental sensors
Air quality sensors (CO₂, VOCs, NOx, particles, vaping) and acoustic sensors that recognise screams, shouts and glass break without ever recording audio.
Storage, cloud & developer tools
Recorders with RAID, industrial-grade SD cards, and cloud storage, planned as three layers: primary, redundancy, backup. Cloud Connect for managed services, plus free SDKs.
Security built in
Axis Edge Vault (hardware keystore and secure boot), Signed Video, a public Hardening Guide and Vulnerability Policy, and firmware fixes as issues are found.
Reading a model name
Every network camera name follows the same pattern, according to Axis's product naming structure guide. Take AXIS P3265-LVE:
The digits
- 1st, product type: 1–2 box, bullet or thermal · 3–4 dome · 5–6 PTZ · 8–9 corner, specialised dome or intercom.
- 2nd, series: letter + first two digits is the series name, so P32 is a family of P-line domes.
- 3rd, running number within the series.
- 4th, resolution: 4 = 720p · 5 = 1080p · 6 = 3–5 MP · 7 = 5–8 MP · 8 = 8–15 MP (4K) · 9 = over 15 MP. Thermal models use their own scale.
- Mk II etc. on the end is a hardware revision.
So P3265-LVE reads: P-line dome, series 32, 1080p, with LED illumination, vandal-resistant and outdoor-ready. Modular (F/FA), Zone 1 explosion-protected and some other ranges use their own patterns.
Camera extensions
- -E outdoor-ready · -V vandal-resistant · -L LED illumination (the built-in IR)
- -P panoramic · -R rugged · -S stainless steel
- -T temperature measurement (thermometric) · -C climate-controlled
- -B barebone · -H recessed · -D detector · -G gateway · -W wireless
- -X Zone/Division 2 explosion-protected certification
Your study files read LVE as “Lightfinder + varifocal + outdoor”. That's wrong: L is LED illumination and V is vandal-resistant. Lightfinder and varifocal lenses aren't in the name at all; check the datasheet for those.
Camera lines, in Axis's own words and in practice:
| Line | Job | Default sites | Examples to recognise |
|---|---|---|---|
| Q | “Most advanced video products for mission-critical systems.” Evidence-grade image, PTZ, thermal, toughest builds. | Transit, public safety, critical infrastructure, city surveillance | Q6155-E PTZ (laser focus), Q19-series thermal, Q29 thermometric |
| P | “Versatile and advanced video products.” The workhorse and the default answer. | Parking, warehouse, retail, hospital, outdoor perimeter | P13 bullets, P32 domes such as P3265-LVE |
| M | “Affordable, intuitive video products.” Compact and cost-first, for high camera counts. | Classrooms, offices, multi-tenant buildings | M30 mini domes, M3057-PLVE (P = panoramic) |
| V | “Live-streaming cameras for professional use.” | Broadcast, events, lecture capture | – |
| F | Modular: tiny sensor head on a cable, main unit hidden away. | ATMs, kiosks, vehicles, tight spaces | F41 / F44 main units with F-series sensors |
| T | Accessories: mounts, illuminators, midspans, media converters. | Every job. The mount decides whether a camera drifts. | – |
Other line letters
- C network audio: speakers, horns, sound projectors, paging consoles, audio bridges
- D system devices: radar, decoders, I/O and audio devices, strobes and sirens, environmental sensors, analytics devices, switches
- I network intercoms · A access control (door controllers, readers, I/O relay modules)
- S recorders, servers and workstations · W body-worn
- X as a prefix marks Zone/Division 1 explosion-protected products (XPQ1785, XC1311). As a -X suffix it marks Zone/Division 2. A handy way to remember the difference.
- T accessories; the second letter names the parent line (TQ6501-E is a parapet mount for the Q line)
The tier rule of thumb ballpark
| Tier | Chip | Impact rating | Power | Best for |
|---|---|---|---|---|
| M | Often cost-optimised; varies by model | IK08 typical: accidental bumps | Low draw (PoE Class 2–3), so more cameras per switch | Indoor density |
| P | ARTPEC (ARTPEC-9 on the newest) | IK10 typical: expected hammer blows | PoE Class 3 or 4 once IR and heaters are on | Outdoor lots, perimeters |
| Q | ARTPEC-9 on current models | IK10, metal housings | Class 4 or PoE++ (802.3bt) for PTZ and heaters | Evidence, PTZ, compliance |
Why the chip matters: a “smart” camera on a weak chip becomes a dumb encoder, and the analytics move to the VMS, which costs GPU, licences and support. ARTPEC-9 runs edge AI (object classes, plate reading, privacy masking) and is where AV1 lives. Exact chip, IK and PoE class differ by model, so check the datasheet.
Names that earn credibility
- ACAP apps: AXIS Object Analytics (people and vehicles), AXIS License Plate Verifier, AXIS Live Privacy Shield, plus third-party apps. Analytics on the camera mean fewer VMS licences.
- OptimizedIR: IR matched to the field of view. On PTZ it widens and narrows with zoom.
- Scene Metadata: object data from the camera (class, colour, position, speed from radar) as a separate stream over RTSP, MQTT or ONVIF Profile M. Search “red car, 14:00–16:00” instead of scrubbing 30 days.
- AXIS OS LTS tracks: long-term-support firmware for fleets that must stay stable for years. Active track for sites that want new features.
Price ballpark verify
- Installed, all-in: often ~$500–$4,500 per camera. Most of the spread is labour and cabling, not the camera.
- Q-series PTZ: $5k–$15k+ installed.
- Hikvision and Dahua win on sticker price. Axis wins on compliance, lifecycle, open VMS and edge analytics. That's the total-cost argument.
These figures come from your study notes, not Axis. Use them to show you think about cost, never as a quote.
Topic library
All 45 Academy videos, cleaned up
Each card gives you the main point, the details worth remembering, and a link to the original video. Tick “Learned” as you go. Your progress is saved in this browser only.
Networking fundamentals
TCP, UDP and IP in a camera system
Every Axis product runs on the network, so expect networking questions. This is a condensed version of your TCP/UDP/IP primer, focused on video.
IP
Layer 3 · 20-byte header · best-effort
Addressing and routing. It gets a packet toward the right network but promises nothing about whether it arrives, arrives once, or arrives in order.
TCP
Layer 4 · protocol 6 · 20+ bytes · connection
Handshake, sequence numbers, acknowledgements and retransmission. Data arrives complete and in order, but slower and with variable delay.
UDP
Layer 4 · protocol 17 · 8 bytes · no connection
Ports and a checksum, nothing more. No retransmission and no ordering. Lowest delay, and the only option for multicast.
The one-line answer
Reliability only helps if late data is still useful. A retransmitted live-video packet arrives after its moment has passed, so live view prefers UDP. A recording is evidence and late data is still fine, so recording prefers TCP.
They won't ask you to recite the TCP spec. They'll ask you to get video from a camera to a VMS, or why it works at the office and not from home. Study for that.
Where each layer bites in a camera system
| Layer | What you care about | Typical failure |
|---|---|---|
| 1 Physical | Cat6 on new pulls, 100 m Ethernet limit, PoE budget | A 4K camera on old Cat5e or a 110 m run, or a switch out of power |
| 2 Data link | Switches, MAC addresses, VLANs, IGMP snooping, 802.1X | Camera on the wrong VLAN; multicast flooding every port |
| 3 Network | IP address, subnet mask, gateway, NAT, routing, QoS | Missing default gateway; NAT blocking remote access |
| 4 Transport | TCP vs UDP, ports | RTP UDP ports blocked by a firewall |
| 7 Application | HTTP/HTTPS (web UI, VAPIX, ONVIF), RTSP, SIP, discovery | Wrong credentials, wrong stream profile, HTTPS certificate issues |
Same subnet or not?
A switch (layer 2) moves traffic inside one subnet. A router (layer 3) is needed to leave it: another VLAN, another building, the internet, a VPN. Putting a router where a switch belongs is a classic installer mistake.
- Camera
192.168.1.50/24, VMS192.168.1.10/24: same network, no router needed. - Camera
192.168.1.50/24, VMS192.168.2.10/24: different networks. The camera needs a default gateway and something has to route between them. This is the classic “camera is up but the other VLAN sees nothing.” - Private ranges (RFC 1918), where cameras almost always live:
10.0.0.0/8,172.16.0.0/12,192.168.0.0/16. - Static address or DHCP reservation in production. A camera on a plain DHCP lease can change address and vanish from the VMS, firewall rules and DNS.
| CIDR | Mask | Usable hosts |
|---|---|---|
| /16 | 255.255.0.0 | 65,534 |
| /24 | 255.255.255.0 | 254 · the usual camera LAN |
| /25 | 255.255.255.128 | 126 |
| /26 | 255.255.255.192 | 62 |
| /32 | 255.255.255.255 | 1 · a single host |
Shortcut: usable hosts = 2(32 − prefix) − 2. Drills are in practice questions.
Head to head
| Property | TCP | UDP |
|---|---|---|
| Connection | 3-way handshake first | None, just send |
| Reliability / order | Guaranteed, retransmits | Neither |
| Header | 20+ bytes | 8 bytes |
| Latency | Higher, variable | Lowest, predictable |
| Head-of-line blocking | Yes: one lost packet stalls everything behind it | No: a loss affects one frame |
| Multicast | Impossible | Supported |
| Firewall / NAT | Easy | Often blocked |
| In an Axis system | Web UI, VAPIX, ONVIF calls, RTSP control, firmware, recording | RTP live media, multicast, WS-Discovery, DHCP, DNS, NTP |
Handshake: SYN → SYN-ACK → ACK. It takes three messages because each side must have its starting sequence number acknowledged. Closing a connection takes four (FIN, ACK, FIN, ACK). RTSP (TCP 554) is only the control channel; the media travels over RTP, usually on UDP. If UDP is blocked, RTSP interleaved sends the media over the TCP connection instead. It gets through firewalls, but loses multicast and adds delay.
Axis's own latency guidance, paraphrased: on a LAN you control, RTP/RTSP over TCP (or HTTP) is fine. Over a WAN with hops you don't control, use RTP over UDP, unicast or multicast. In a browser, WebRTC. The line to say: “Live operators would rather skip a frame than freeze. Recording still wants reliability.”
Multicast: when it's needed, and what breaks it
With unicast, ten viewers means the camera sends ten copies. With multicast, it sends one stream to a group address (224.0.0.0–239.255.255.255), and the network copies packets only where the paths split (topic 22). TCP can't do this because it only ever connects two endpoints.
| Piece | What it does | What goes wrong without it |
|---|---|---|
| IGMP | How viewers join and leave a group | Nothing can subscribe |
| IGMP snooping | Switch sends the stream only to ports that asked for it | The stream floods every port and the whole network slows |
| IGMP querier | Regularly checks who's still subscribed | Streams stop after a minute or two |
| Multicast routing (PIM) | Carries groups between VLANs and subnets | “Works on this switch, not across the site” |
Multicast is a LAN tool. It doesn't cross the public internet.
“It works at work but not from home”
At work you're on the same LAN (or VPN) as the camera. From home you arrive at the site's single public IP, and the camera only has a private address behind NAT. Nothing tells the router which inside device your request is for, so it never arrives.
| Option | How it works | Verdict |
|---|---|---|
| VPN | Puts the remote user on the site network | Preferred where IT runs one |
| Axis Cloud Connect / secure remote access | The device connects outward to an Axis-hosted service, so no inbound ports are opened | Preferred for multi-site and mobile viewing |
| Port forwarding (DNAT) | A public port is mapped to one inside device | Last resort. HTTPS only, non-default ports, no default credentials, current firmware |
| RTSP straight to the internet | Port 554 forwarded with nothing in front of it | Never. That's how cameras end up in botnets |
Also worth knowing: source NAT is many inside hosts sharing one public IP on the way out. STUN, TURN and ICE are how SIP intercoms and speakers get through NAT. And if video is fine on the LAN but breaks up over a VPN, suspect MTU: big 4K frames, a smaller tunnel MTU, fragmentation and TCP stalls.
How a frame gets to the VMS
| Protocol | Job |
|---|---|
| RTSP | The remote control: DESCRIBE, SETUP, PLAY, TEARDOWN |
| RTP | Carries the audio and video |
| RTCP | Reports loss and jitter alongside RTP |
| HTTP/HTTPS | Web UI, VAPIX and ONVIF calls |
| ONVIF | Multi-vendor standard for discovery, streaming, PTZ, events |
| VAPIX | Axis's own API, for Axis-only features (Zipstream settings, Edge Vault, some analytics) |
| ONVIF profile | Covers |
|---|---|
| S | Basic streaming, PTZ, audio. Almost every Axis camera. |
| T | Advanced streaming: H.264/H.265, imaging settings, events, metadata, HTTPS |
| G | Edge storage: search and play back recordings on the camera's SD card |
| M | Analytics metadata, such as object classification |
| A / C | Access control: configuration (A) and door control (C) |
Watch out: one of your study files lists Profile T as “PTZ”. It isn't. PTZ is in Profile S. A good VMS uses ONVIF for discovery and the standard profiles, and VAPIX for Axis extras. The customer line: “ONVIF is a common language, so your VMS can see Axis without custom code. You're not locked to our recorder.”
Ports worth knowing
| Port | Transport | Service | Why it matters |
|---|---|---|---|
| 80 / 443 | TCP | HTTP / HTTPS | Web interface, VAPIX, ONVIF. Recommend 443. |
| 554 | TCP | RTSP | Stream control. If this is blocked, cameras are found but video won't play. |
| 3702 | UDP | WS-Discovery | How ONVIF devices are found, via multicast to 239.255.255.250. If discovery finds nothing, this is filtered. |
| 1900 | UDP | SSDP / UPnP | Discovery on Windows networks |
| 5353 | UDP | mDNS / Bonjour | Discovery on Apple and Linux tools |
| 67 / 68 | UDP | DHCP | Address assignment |
| 53 | UDP | DNS | Name resolution |
| 123 | UDP | NTP | Time sync. Clocks that drift weaken timestamps as evidence. |
| 5060 / 5061 | UDP TCP | SIP | Intercoms, door stations, horn speakers (topic 33) |
| 161 / 162 | UDP | SNMP | Device health monitoring and traps |
Don't mix camera ports with server ports. AXIS Camera Station's server uses its own range; your notes give 55752 (media), 55754 (TLS app) and 55757 (RTSP over HTTP for mobile) verify. And don't call port 8000 “the Axis port”. That's a generic NVR myth.
Network hygiene to recommend
- Cameras on their own VLAN, routed to the VMS through a firewall rather than sitting on the office network.
- QoS (DSCP marking) so video ranks above best-effort traffic like file copies.
- 802.1X: the camera proves its identity to the switch before the port opens. Edge Vault's factory ID makes this practical.
- No factory default login. On current AXIS OS the installer creates the admin account at first boot.
- Follow the Hardening Guide: HTTPS only, unused services off, firmware current. Cameras are always-on computers that get exploited (botnets, a pivot into the VMS), not just stolen.
- Shared responsibility: Axis, the integrator and the customer each own part of the security. It's a process, not a sticker.
Symptom → likely cause
Camera pings, but there's no video
Layer 3 is fine. Work up the stack: credentials, RTSP 554 blocked, VMS on another subnet with no gateway on the camera, wrong stream profile.
Discovery finds no cameras
UDP 3702 (WS-Discovery multicast) is filtered between the client and the cameras, or they're on another VLAN. Add the camera by IP address to confirm.
Works on site, not from home
Private address behind NAT. Use a VPN or Cloud Connect, not a bare RTSP port forward (see above).
Fine on the LAN, choppy over the VPN
MTU and fragmentation. Large 4K frames are split to fit the tunnel, and losses stall TCP. Lower the bitrate for remote viewers or use the low-resolution stream.
Camera is found, but video won't play
RTSP 554 or the RTP UDP ports are blocked. Discovery and streaming use different ports.
Try RTSP over TCP. If video starts, it's a UDP path problem, not a faulty camera.
Camera shows a 169.254.x.x address
DHCP failed and the camera assigned itself a link-local (APIPA) address. Check for a missing DHCP server, the wrong VLAN, or a relay problem.
Live view is choppy, recordings are fine
Packet loss on the UDP live stream. Recording over TCP retransmits and recovers. Also check duplex mismatch, overloaded uplinks and missing QoS.
Cars freeze, then jump ahead
Jitter: a 50 Hz stream shown on a 60 Hz monitor. It's not a camera fault. Use a 50 Hz-capable screen (topic 20).
Moving objects are blurry
Shutter speed is too slow. Raising the frame rate won't help (topic 16). If the objects look slanted rather than blurred, that's rolling shutter (topic 17).
Multicast dies after about 60 seconds
There's no IGMP querier, so memberships expire. If multicast fails only across VLANs, multicast routing is missing.
Bitrate spikes whenever the PTZ moves
Standard Zipstream switches off while the whole scene is moving. Zipstream for PTZ fixes this on supported models (topic 42).
PTZ won't move after a winter power cut
This is expected. Arctic Temperature Control runs only the heater until it's safe to move (topic 04).
Sizing math
Bandwidth and storage, worked live
Sales engineers get asked to size a system on the spot. Change the inputs to see the effect, but learn the rule of thumb so you can do it on a whiteboard.
- Recording bandwidth
- –
- Per camera / day
- –
- Total storage
- –
- Live, unicast
- –
- Live, multicast
- –
unicast per camera = Mbps × viewers · multicast per camera = Mbps (once per link)
Memorise this: 1 Mbps for 24 hours ≈ 10.8 GB. So 4 Mbps ≈ 43 GB per camera per day, and 100 cameras × 30 days ≈ 130 TB. Bitrate is measured in Mb (bits), storage in MB (bytes); divide by 8. In practice Zipstream keeps real bitrates well below the cap, and average bitrate (topic 08) is what makes the storage figure predictable.
What Zipstream saves: night is the story
| Scene | Plain H.264 | Zipstream high | Zipstream extreme | Saving |
|---|---|---|---|---|
| Day | 1,931 kbps | 1,019 kbps | 1,095 kbps | ~47% |
| Night | 5,398 kbps | 896 kbps | 876 kbps | ~84% |
Why night: low-light noise changes pixels in every frame, so a plain encoder spends bits on grain. Zipstream treats the static, noisy background as background. The line to say: “At night it went from about 5.4 Mbps to 0.9.” And note that extreme isn't always lower: in daylight it came out above “high”. Figures are from Axis's interactive Zipstream demo (dynamic GOP and dynamic FPS on); real sites vary.
System design
From a customer's problem to a bill of materials
This is 30% of Axis's own certification and most of a sales engineer's week. The rule: don't start with a model number. Start with what the footage has to prove.
The five inputs that pick a camera
1 · Lighting
Lightfinder for colour in low light, OptimizedIR for darkness, Forensic WDR for backlit doors. Thermal when there's no light at all.
2 · Distance and field of view
Short and wide for coverage. Long lens or PTZ for perimeters and plates.
3 · Pixel density
Match resolution to what must be proved, not the spec ceiling. 2 MP covers many detection jobs. Plates and faces need more.
4 · Weather and abuse
IP66 minimum outdoors, IK10 where people can hit it, NEMA 4X for wash-down, heaters for arctic sites.
5 · VMS
What records it? Camera Station Pro, Genetec or Milestone changes licensing and which features carry through (below).
Pixel density (IEC 62676-4)
Pixels on the target, not sensor resolution. Density falls with distance, so a 4K camera too far away fails the same way a 1080p one does.
| Goal | px / m | px / ft | What it lets you say |
|---|---|---|---|
| Detect | 25 | ~8 | “Something, probably a person, is there” |
| Observe | 62.5 | ~19 | Clothing and actions |
| Recognize | 125 | ~38 | “That's someone I know” |
| Identify | 250 | ~76 | A stranger can be identified beyond reasonable doubt |
| Inspect | 1,000 | ~305 | Fine detail: banknotes, cards, small print |
The angle matters too: identification needs a camera looking down at no more than about 20°. A camera mounted high over a car park can't identify faces even in 4K. Design a capture line at face height instead. Intercoms already sit there. The line to say: “I don't start with a model. Detect, recognize or identify → pixels per metre → Site Designer.”
Scoping a site, step by step
- Purpose per camera: detect, recognize or identify, which sets the px/m.
- Placement: height, backlight (WDR at doors), IR range, angle for ID.
- Form factor: dome, bullet, PTZ, panoramic, modular, thermal, radar, speaker.
- Bandwidth: from Site Designer, not a guess. Zipstream, dual streams and average bitrate.
- Storage: days × cameras × average bitrate (calculator).
- Network: camera VLAN, PoE budget including IR, heaters and PTZ motors, Cat6, IGMP if multicast.
- Cybersecurity: HTTPS, 802.1X, Hardening Guide, Edge Vault, no bare RTSP on the internet.
- VMS: Camera Station Pro, Genetec or Milestone.
- Environment: outdoor rating, arctic heaters, Zone 1 vs Zone 2.
Worked: 50 cameras, PTZ and analytics
- Walk the five inputs per zone; don't spec one model.
- P series domes and bullets for general coverage. Q-series PTZ where zoom and endurance matter (gates, large open areas). M series for dense indoor counts.
- Analytics on the camera (ACAP: Object Analytics, License Plate Verifier, Live Privacy Shield) so the recorder stays lean.
- Size switch PoE for PTZs at Class 4 or PoE++, run Cat6, size bitrate and storage in Site Designer.
- Hand back a per-zone breakdown, not one number.
Worked: a parking lot
- First question: plates, overview, or both?
- Overview: panoramic or multi-sensor cameras.
- Plates: bullets with IR at a capture point, angled for the plate, running License Plate Verifier.
- Fence line: radar or thermal for detection, with fusion if they want classification.
- Horn speakers for talk-down. WDR at the gate where headlights shine in.
PoE: the standards and why installs fail
| Standard | At the switch | At the device |
|---|---|---|
| 802.3af (PoE, Class 0–3) | 15.4 W | 12.95 W |
| 802.3at (PoE+, Class 4) | 30 W | 25.5 W |
| 802.3bt Type 3 (PoE++) | 60 W | 51 W |
| 802.3bt Type 4 (PoE++) | 90 W | 71 W |
Why PoE fails in the field
- Switch budget exceeded, often at night when IR switches on, or in winter when heaters run.
- Runs over 100 m. Use an extender, fibre, or PoE over coax.
- Midspan and switch don't agree on the standard.
- 60 W and up needs all four pairs of the cable.
- After a winter outage, heaters draw first and the PTZ waits (topic 04).
The commercial point: PoE usually means no electrician at each camera, and one UPS at the switch keeps every camera up. That's a cost argument, not trivia.
Axis design tools
| Tool | Job |
|---|---|
| AXIS Site Designer | Site map, coverage, px/m, bitrate, storage, PoE and the bill of materials. Use it rather than inventing a Mbps. |
| Product Selector | Filter the catalogue by requirement |
| Accessory Selector | The right mount for a camera and surface. Mounts aren't optional. |
| Lens Calculator | Coverage vs distance vs image quality |
| CAD plug-ins | Coverage shapes for Revit, Bluebeam and similar tools |
Which VMS, and when Axis isn't the answer
| Platform | Where it fits | With Axis |
|---|---|---|
| AXIS Camera Station Pro | Axis end to end, small to mid-size sites | Full feature set |
| Genetec Security Center | Unified video, access control and plate recognition | Strong integration |
| Milestone XProtect | Video-heavy enterprise. Also Canon-owned, so a sister company. | Strong integration |
| Eagle Eye Networks | Multi-site cloud | Via ONVIF bridge |
| Avigilon Unity | Motorola's on-prem platform | Via ONVIF, analytics often reduced |
| Verkada, Avigilon Alta | Closed cloud systems | Don't run Axis cameras |
Say the honest answer: Axis isn't right for a lean-IT customer who wants cloud-only (Verkada, Alta), or for the lowest-budget schools and retail, where Hanwha often wins on price. Saying so builds trust, and you can still win where Axis fits. Integration depth changes by release, so check before promising a feature through a third-party VMS.
Practice questions
Questions you're likely to get
Answer out loud first, then open the card to check. Give the answer and stop; over-explaining a correct answer is the most common mistake.
Questions to ask them
Does the channel actually follow you to the cloud?
Subscriptions change the integrator's economics: margin they'd get on the hardware today becomes slow recurring revenue. Is partner appetite, rather than customer demand, what's holding Cloud Connect back?
Where do audio and access sales stall?
Do partners sell them, or are most still camera specialists who leave speakers and doors to someone else? Is the cause training, how partners are paid, or who the partner knows at the customer?
What's holding AV1 back: Axis, or the ecosystem?
The bitrate saving only counts if the VMS on the other end supports it. If the software is the bottleneck, that's a partner-management problem more than a product one.
How often is a tender lost before you get to talk?
Where a spec is written around certification, total cost or cybersecurity, Axis can win on merit. But how often is it written on unit price by someone who never calls you? If that's common, it's a case for reaching the specifier earlier.
Practical questions about the role
- What does a typical sales engineer day look like: demos, proposals or travel?
- Which product areas is this team pushing right now?
- How do you support channel partners day to day?
- What does good look like at six months?
- How many of your sites run Camera Station versus Genetec or Milestone?
Gaps to prepare for
These are the honest answers to “Where would you need to grow?” Name the gap, say what you've already done about it, and say how you'd close it.
- The VMS and integration ecosystem. You know the Axis side of the stack better than the software it connects to, and in a real deal that's where the friction is. Prep: learn the VMS table (Camera Station Pro, Genetec, Milestone, and which platforms won't run Axis) and how ONVIF and VAPIX connect them.
- Hands-on experience with the product. You can explain how autofocus or WDR works, but configuring a camera in difficult lighting is a different skill. Prep: know topics 40, 16 and 37 well enough to describe what you'd adjust and why.
- What really happens on installs. What goes wrong, what an integrator quietly worries about, which promises are hard to keep. That only comes from site visits. Prep: the symptom → cause cases and why PoE fails are the closest stand-in. Say you'd ask to shadow partners on site early on.
- The competitive picture in the field. You know competitors on paper, not how deals are actually won and lost. Prep: know the competitor table, and ask which competitor they meet most often.
Sales engineer questions
Explain how a video surveillance system works, in simple terms.
Light hits the sensor. WDR and shutter settings tame the scene. The encoder compresses it, and Zipstream keeps the quality cheap. It travels over Ethernet, where PoE carries power on the same cable. A recorder stores it and an operator watches or reviews. The modern twist is edge analytics: the camera decides what's worth attention.
Close with: “A camera that understands what it's seeing, and only bothers you with what matters.”
A customer wants 50 cameras with PTZ and analytics. How do you scope it?
Walk the five inputs per zone. Mix P series for coverage, Q-series PTZ where zoom and endurance matter, M series for dense indoor counts. Run analytics on the camera with ACAP so the recorder stays lean. Size the switches for Class 4 or PoE++ on the PTZs, and get bitrate and storage from Site Designer. Hand back a per-zone breakdown, not one number. Full version under system design.
What is ONVIF, and why does the customer care?
It's a common language for security devices: discovery, streaming and PTZ (Profile S), advanced codecs and events (T), analytics metadata (M). The customer isn't locked to Axis's recorder; they can choose the VMS that fits. Axis co-founded it in 2008. Without it, every camera brand would be an island.
How would you demo a camera to someone non-technical?
Start with their problem, not the camera. Then show three things: a backlit door where WDR keeps both sides visible; a person walking through while the face stays usable; analytics flagging a person or car with no settings to touch. Stop there. Then ask: “What would this have caught for you last month?” Credibility comes from the setup, not the gadgets.
“Axis is too expensive.”
Move from unit price to total cost and risk. Edge analytics mean fewer servers and licences. IK10 housings and LTS firmware mean fewer truck rolls over a 7–10 year life. Zipstream cuts the storage bill every year. And for government or enterprise, a system that fails an audit costs far more than the sticker gap. Then ask what the footage has to prove, and let that drive the design.
“We already use Hikvision.”
Acknowledge it: they're cheaper and ship fast. Then the three reasons: NDAA Section 889 and the FCC Covered List for anything federally funded; firmware provenance (own chip, signed firmware, Edge Vault); and an open platform that works with their VMS. Be honest: if they only want the cheapest boxes, Axis isn't the answer. For anything that has to survive an audit, it is.
“Will it work with our VMS?”
Almost certainly through ONVIF, and with the major platforms through deeper integrations that use VAPIX for Axis-specific features. Ask which VMS and version, then check how deep the integration goes before promising a specific analytic. See the VMS table.
What is PoE, and why is it valuable?
One cable for power and data. Installs are faster and usually need no electrician at each camera, and a UPS at the switch keeps every camera up in a power cut. The catch: Q-series and PTZ cameras need PoE+ or PoE++, so size the switch or cameras drop out at night when IR comes on.
Tell me about a time you turned down a deal, or handled a tough customer.
Use STAR #1. The shape of a good answer: you put the customer's outcome ahead of the biggest invoice, you explained the trade-off plainly, and the honesty paid off later (a referral, a follow-on deal, or simply trust). Finish with what you learned.
How do you split time between technical prep and selling?
For a sales engineer, prep is the selling. Block focused time on the customer's use case, then demo with it fresh. Skip prep and you sound like a salesman; only prep and you never close.
Give an example of working with a team to close a deal.
Use STAR #2. Show that each person owned a piece (technical credibility, the relationship, the commercial close) and that the deal was won because they lined up. That's Act as One.
Axis & products
Give me the 30-second version of what Axis does.
Axis invented the network camera in 1996 and has built on it ever since. It now makes cameras, audio, access control, intercoms, radar and environmental sensors, all as network devices, and sells them through integrators. It competes on image quality in poor light, lower bandwidth and storage, cybersecurity, and open standards, so its products fit into whatever system the customer already runs.
What is Zipstream, and how would you explain it to a customer?
Zipstream runs inside the camera. For each frame it finds what matters (people, objects, motion) and compresses that area lightly, and it compresses the empty background heavily. You keep the forensic detail and stop paying to store detailed images of a blank wall. Dynamic GOP sends fewer full frames when nothing is happening, and the storage profile adds B-frames for about another 50%. It stays standard H.264, so no special player is needed.
“We want 4K, but our network can't handle it.”
You don't need to rebuild the network. Axis cameras send several streams at once: record 4K to local storage for forensics and send a low-resolution live stream to the remote operator. Add Zipstream, average bitrate for a predictable budget, and AV1 on ARTPEC-9 cameras. It's also worth asking whether they need more pixels or better low-light performance, since a larger sensor often helps more.
How can a customer prove footage hasn't been tampered with?
Signed Video. The camera calculates a checksum for every frame, signs groups of checksums with a private key created at the factory and stored in Axis Edge Vault, and embeds the signatures and public key in the H.264/H.265 stream. At playback, the checksums are recalculated and compared, so any changed pixel is caught. The video isn't encrypted, so any player can still open it.
A site needs night-time perimeter detection. What are the options?
It depends on what they need to know. Lightfinder gives colour video in low light, which helps identify clothing and vehicles. Thermal needs no light at all and detects people who fill only a few pixels, even partly hidden by bushes or mist, with few false alarms. It's for detection, not identification. Radar gives exact position, ignores weather and insects, and can steer a PTZ. Radar-video fusion combines early detection with classification up close.
A customer is upgrading an old analog site. How do you avoid new cabling?
PoE over coax reuses the existing coaxial cable for power and data, up to 500 m depending on cable quality. For elevators, PoE over 2-wire uses spare wires in the traveling cable, up to 220 m. Standard PoE reaches 100 m. Pulling new cable is often the most expensive part of an upgrade quote.
What's the difference between Zone 1 and Zone 2 cameras?
Zone/Division 1 is the higher-risk area, where explosive gas or dust is likely. The camera sits in a heavy stainless-steel enclosure designed to contain an internal explosion, and only certified staff can install it, because a scratch on the flame path ruins the protection. Zone/Division 2 covers the larger, lower-risk area around it. The electronics are designed never to spark or overheat, so there's no heavy enclosure. These cameras are lighter, cheaper and easier to fit.
Operators say motion is blurry. Should they raise the frame rate?
No. Blur comes from shutter speed. Frame rate only sets how many still images you get per second. A faster shutter reduces blur but lets in less light. If anything, lowering the frame rate saves bandwidth without making each image blurrier.
How does Axis handle privacy-sensitive places like schools?
With sensors that produce data but no footage or recordings. The acoustic sensor recognises screams, shouts and breaking glass but never streams or stores audio, only metadata. Air quality sensors detect vaping and smoking. Radar can be used where cameras aren't allowed. Network audio covers announcements and emergency messages.
Why choose Axis over a cheaper brand?
Point to total cost and risk, not the unit price. Storage costs more over time than cameras, and Zipstream reduces it. Cybersecurity: Edge Vault, signed firmware, a public hardening guide and vulnerability policy. Evidence that can be proven with Signed Video. Openness: ONVIF, VAPIX and SIP mean no lock-in. In the US, NDAA compliance matters for any federally funded project. And one partner can supply video, audio, access and sensors on the same network.
What does an Axis network speaker replace?
The mixer, amplifier, equaliser and the sound engineer needed to set them up. The speaker, amplifier and DSP are one pre-tuned unit, and the signal stays digital all the way, so there's no noise from long cable runs. It also tests itself: a built-in microphone listens for a calibrated test tone.
Networking
Why use UDP when TCP is more reliable?
Reliability costs delay, and it only pays off if late data is still useful. A retransmitted live-video packet arrives after its moment has passed. UDP also supports multicast, which TCP can't, so any one-to-many streaming setup needs it.
What is head-of-line blocking?
TCP delivers data in order, so one lost packet makes everything behind it wait for the retransmission. On live video you see a freeze, then a jump, and the delay doesn't recover.
IT will only allow TCP. What do you tell them?
It works: RTSP interleaved sends media over the TCP control connection and gets through firewalls cleanly. But they lose multicast, so bandwidth grows with every viewer, and live delay becomes less predictable. That's fine for a few operators. For a big control room, show them the bandwidth numbers first.
How much storage for 100 cameras at 4 Mbps for 30 days?
About 130 TB. 1 Mbps for a day ≈ 10.8 GB, so 4 Mbps ≈ 43 GB per camera per day; × 100 = 4.3 TB/day; × 30 ≈ 130 TB. Then say that Zipstream means real bitrates usually run well below the cap, and the storage profile can roughly halve it again.
Why does NTP matter in a camera system?
Footage is evidence, and evidence needs trustworthy timestamps. If cameras' clocks drift apart, piecing an incident together across several cameras becomes unreliable. NTP runs over UDP, so it fails silently: nothing visibly breaks, the clocks just drift.
The camera pings, but there's no video. What do you check?
Ping proves layer 3 works, so move up the stack: credentials; RTSP 554 or the RTP ports blocked; the VMS on another subnet with no gateway set on the camera; UDP 3702 filtered if discovery is the problem; the wrong stream profile. Try RTSP over TCP: if video starts, it's a UDP path issue.
“I can open it at work but not from home.” What's wrong?
At work you're on the LAN. From home you hit the site's public IP, and the camera only has a private address behind NAT, so the request never reaches it. Fix: a VPN or Axis Cloud Connect. Port forwarding is a last resort (HTTPS, non-default port, no default credentials). Never forward bare RTSP to the internet. More.
Switch or router?
Same subnet: switch. Anything else (another VLAN, building, the internet): router, and the camera needs a default gateway.
How do you save bandwidth without losing forensic quality?
In order: Zipstream (night is where it pays: about 5.4 → 0.9 Mbps in Axis's demo), average bitrate for a fixed budget, dual streams (full resolution to disk, low resolution to remote viewers), don't run 30 fps where 15 will do, and AV1 on ARTPEC-9 cameras if the VMS supports it.
Drill: camera 10.20.30.40, mask 255.255.255.0. Network, broadcast, usable range?
Network 10.20.30.0, broadcast 10.20.30.255, usable hosts .1 to .254.
Drill: can 192.168.10.5/24 talk to 192.168.11.5/24 without a router?
No. With a /24 the third number is part of the network, so .10 and .11 are different networks.
Drill: how many usable hosts in a /26 on 172.16.4.0?
62. 32 − 26 = 6 host bits, 2⁶ = 64, minus network and broadcast.
Drill: why give cameras DHCP reservations?
The address has to stay stable for the VMS, firewall rules and DNS. A camera that gets a new lease effectively disappears.
Self-test: close the page and answer in a minute each
The five inputs that pick a camera?
Lighting · distance and field of view · pixel density · weather and abuse · VMS. Check.
P vs Q vs M, one sentence each?
Q premium: evidence-grade image, PTZ, thermal. P the professional workhorse for most commercial sites. M compact and cost-first for dense indoor counts. Check.
Can 10.0.1.20/24 reach 10.0.2.20/24? What's missing?
Not directly; they're different /24 networks. It needs a router between them and a default gateway on each device, and any firewall in between has to allow the traffic.
Name five camera ports.
80 HTTP · 443 HTTPS · 554 RTSP · 3702 WS-Discovery · 5060/5061 SIP. Bonus: 1900 SSDP, 5353 mDNS, 123 NTP.
Why UDP for live view?
A lost UDP packet costs one frame; a lost TCP packet stalls everything behind it while it's resent. Live operators would rather skip a frame than freeze. UDP also enables multicast.
Detect, recognize, identify in px/m?
25 · 125 · 250 px/m (observe is 62.5, inspect 1,000). Check.
Why does Zipstream win most at night?
Low-light noise makes every frame look different, so a plain encoder spends bits on grain. Zipstream compresses the static background hard. About 5.4 → 0.9 Mbps in Axis's demo.
ONVIF S vs T vs M?
S basic streaming and PTZ · T advanced streaming (H.265, events, HTTPS) · M analytics metadata.
Axis vs Hikvision in three reasons?
NDAA/FCC compliance · firmware and supply-chain trust (own chip, signed firmware, Edge Vault) · open platform with any VMS.
Scope 50 cameras out loud in 60 seconds.
Five inputs → P for coverage, Q-PTZ where zoom matters, M indoors → ACAP analytics on the camera → PoE Class 4/PoE++ for PTZ → Site Designer for bitrate and storage → per-zone breakdown.
“Why Axis?” in two sentences, using a core value.
An example in Always Open: “Axis co-founded ONVIF and works with whatever VMS the customer already runs, so nobody's locked in. That's the kind of honesty I want to sell with.” Then say it in your own words.
Glossary
Terms to know
Sources & caveats
Before you quote any of this
The transcripts were produced automatically (faster-whisper large-v3), not by Axis. They're accurate on ordinary speech but regularly get the company name and PTZ wrong. The topic cards above use the corrected versions. If you search the raw transcript files, search for the mistakes too:
| Transcript says | Actually |
|---|---|
| Access / ASUS / “Access Cloud Connect” | Axis / Axis Cloud Connect |
| PDZ / PDC | PTZ |
| OPEC 9 | ARTPEC-9 (Axis's own chip) |
| “Compare with ASUS X5” | Compared with H.265 |
| “Amphilogy Billings” | Alternatively, buildings |
| “for both and train” | for both bus and train |
| “AccessControl combined with video” | Access control combined with video |
Three kinds of content are mixed on this page. Topic cards and figures come from the Academy videos. The company section (history, Canon, competitors, product-line letters, NDAA) is general background, so check it against axis.com and Axis's annual reporting. The “how Axis thinks” and “commercial angle” sections are interpretation of the videos, not something Axis says itself.
Interview prep, system design, the model decoder and the expanded networking material come from three of your own study guides (AXIS.pdf, the interview study guide and the Ultimate Study Guide). Where they disagreed, the corrected version is used here: ONVIF Profile T is advanced streaming, not PTZ; port 8000 isn't an Axis port; Axis thermal cameras are Q-series, not F-series; and -LVE means LED illumination, vandal-resistant, outdoor-ready (confirmed against Axis's product naming structure guide), not “Lightfinder, varifocal, outdoor”. The PDF's pre-written STAR stories were left out on purpose, since yours need to be real. Items tagged verify or ballpark are notes, not Axis facts: tier chips and PoE classes, price ranges, and the Camera Station server ports. The modular sensor cable length also varies between sources (about 15–30 m); check the specific model.