Products & Services

Security architecture

Cisco Call Recording Security With a Small Network Footprint

The recorder needs two kinds of access: internal paths to your Cisco voice infrastructure, and outbound HTTPS to call-recording.com.

Cisco Voice

customer network

Recorder

headless runtime

call-recording.com

outbound HTTPS

the recorder initiates every connection; nothing inbound

INSIDE THE CUSTOMER NETWORK

Access only to the voice systems it serves.

The recorder talks to the relevant Cisco voice nodes for signaling and media, and adds no local administration stack.

outbound to call-recording.com

A single encrypted management and delivery path.

Control traffic, CDR delivery, and recording uploads all use outbound HTTPS to the call-recording.com backend.

ALIGNED WITH ZTNA PRINCIPLES

Expose less, and trust only the paths you need.

No inbound internet access

The recorder accepts no management connections from the internet. It opens its cloud connection itself, so there is nothing to publish, proxy, or expose.

No local management portal

You administer the recorder from the SaaS dashboard. It runs headless, with no local web interface to patch, protect, or audit.

AES-256 encryption at rest

Uploads are protected in transit. Once stored, recording audio and its associated metadata are encrypted at rest with AES-256. Encryption is applied automatically across the storage layer, which supports common encryption-at-rest control requirements, and access stays authenticated and scoped to your organization.

attack-surface audit — recorder
inbound internet ports open 0
management portals exposed 0
UDP ranges required 0
port-forwarding rules 0
outbound TLS paths 1

That is the whole list.

FOR THE FIREWALL CHANGE REQUEST

Every protocol, port, and direction on one page.

Outbound HTTPS and secure WebSocket on TCP 443; AXL SOAP, SIP/SIPREC, and forked RTP inside the voice network; nothing inbound from the internet. Attach the PDF or Visio file to your security review.

Solution topology: technical view with protocol flows Open full size
call-recording.com technical topology: recorder appliances in the customer recording tier connect outbound-only over TCP 443 to the call-recording.com cloud, use AXL SOAP and SIP/SIPREC with the Cisco Unified CM cluster, and receive forked RTP media from phones with Built-in Bridge.
Download for your review: PDF Visio (.vsdx) SVG

SECURITY ARCHITECTURE

Test the network model in your own environment.

Deploy a recorder and confirm the Cisco voice and outbound HTTPS paths it needs.

Start Your Trial