--- title: Call Recording Server Setup - SIP Trunk description: Learn here how to set up your Corti Call Recording Server and network --- [Skip to content](https://help-legacy.corti.ai/migration/call-recording-server-setup-sip-trunk#main-content) English Show submenu for translations ![Orb\_logotype\_horizontal\_white.png\]](https://help-legacy.corti.ai/hs-fs/hubfs/Orb_logotype_horizontal_white.png?height=40&name=Orb_logotype_horizontal_white.png) - [Default HubSpot Blog](https://3997889.hs-sites.com/blog) Open main navigation Close main navigation - [Default HubSpot Blog](https://3997889.hs-sites.com/blog) - English Show submenu for translations - [Go to corti.ai](https://corti.ai/) [Go to corti.ai](https://corti.ai/) Welcome to Corti's Help Center - There are no suggestions because the search field is empty. 1. [Help Center](https://help-legacy.corti.ai/migration?hsLang=en) 2. [New to Corti?](https://help-legacy.corti.ai/migration/new-to-corti?hsLang=en) 3. [Technical Set-Up](https://help-legacy.corti.ai/migration/new-to-corti?hsLang=en#technical-set-up) # Call Recording Server Setup - SIP Trunk ## Learn here how to set up your Corti Call Recording Server and network #### Integration Onboarding Implementation of the Corti-SIP Trunk call recording integration consists of three major steps: provisioning the call recording server, configuring the call recording server, configuring the call recording integration. **Provisioning of call recording server** This step is carried out by the customer technical team. A server with the following minimal requirements is needed: - Bare-metal or virtual server - Linux operating system (Preferably Ubuntu or RHEL) - Minimum 4 vCPUs - Minimum 16GB of RAM, 32+ recommended for large deployments in busy environments - Minimum 1TB local or network storage, at least enough to hold 72 hours worth of call data - We support Dual Homed Network Interfaces, for environments with segregated networks **Configuring the call recording server** These steps are carried out by the customer technical team. - Provide Corti technical staff direct access to the call recording server. During this process, establish terms on how the Corti technical team can access the call recording server. - Provide Corti technical staff with an admin account on the call recording server - Ensure that the docker application is installed on the call recording server - Configure firewall to allow outgoing traffic on 443/tcp from the call recording server to the Corti backend (FQDN and static public IP address will be provided) - Configure firewall to allow outgoing traffic on 443/tcp and 10516/tcp from the call recording server to the Datadog services (full list of IP ranges available at [https://ip-ranges.datadoghq.com](https://ip-ranges.datadoghq.com)) - Setup SIP Trunk to be terminated at the call recording server on port 5060 and RTP traffic on port ranges 16384 to 32767. The ports can be configured differently. **Configuring the call recording server and integration** This step is carried out by the Corti technical team. - Install the Datadog agent for log collection and monitoring. - Install the Azure command-line interface - Install the Corti call recording integration as a set of docker containers - Configure the call recording integration to terminate the incoming SIP Trunk - Configure the call recording integration to encrypt and send traffic to the Corti Cloud solution - Identify any necessary filtering from call recording side #### Network Traffic Settings Corti requires the following ports to be open for setup & ongoing functionality on a Linux server for our call-recording software to effectively function. **Inbound Traffic** - TCP 22 (SSH): We need SSH traffic allowed to the server to properly install our software, apply updates, and respond to incidents should they occur. This traffic should be open to the following three IP Address ranges: 152.115.138.2/32, 20.105.205.238/32, 52.188.210.50/32 - TCP 5060: This port should be open to the SIP Trunk server, to allow the SIP Trunk to establish and coordinate the SIP Trunk connection. - UDP 16384 - 32767: These ports should be open to the SIP Trunk Source to allow audio RTP packets to flow along the SIP Trunk to Corti’s Call Recording software. **Outbound Traffic** - TCP 80 (HTTP): HTTP traffic from the server should be allowed for updates to Ubuntu, its packages, and other server software can be installed as required. - TCP 443 (HTTPS): HTTPS traffic from the server should be allowed for some updates to Ubuntu, its packages, and other server software can be installed as required. Furthermore, this port is also used to send the audio packets onward to Corti’s Cloud and for metrics to be sent to Corti’s monitoring solution. - TCP 10516: This port is used by Corti’s monitoring solution to send application logs to the centralized resource, which we use for monitoring and debugging potential system issues. - [New to Corti?](https://help-legacy.corti.ai/migration/new-to-corti?hsLang=en#main-content) - [Technical Set-Up](https://help-legacy.corti.ai/migration/new-to-corti?hsLang=en#technical-set-up) - [Implementing Clear/Voyager AI - Call Recorder Integration](https://help-legacy.corti.ai/migration/new-to-corti?hsLang=en#implementing-clear-voyager-ai-call-recorder-integration) - [Implementing Clear/Voyager AI - CAD Integration](https://help-legacy.corti.ai/migration/new-to-corti?hsLang=en#implementing-clear-voyager-ai-cad-integration) - [How To's](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#main-content) - [Clear/Voyager AI Videos](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#clear-voyager-ai-videos) - [Clear/Voyager AI - Explore - Articles](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#clear-voyager-ai-explore-articles) - [Clear/Voyager AI - Call Review - Articles](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#clear-voyager-ai-call-review-articles) - [Clear/Voyager AI - Call Search - Articles](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#clear-voyager-ai-call-search-articles) - [Engage - Protocol Editor Videos](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#engage-protocol-editor-videos) - [Engage - Protocol Editor Articles](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#engage-protocol-editor-articles) - [Admin - Articles](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#admin-articles) - [Clear/Reviews](https://help-legacy.corti.ai/migration/how-tos?hsLang=en#clear-reviews) - [User Guide](https://help-legacy.corti.ai/migration/user-guide?hsLang=en#main-content) - [Engage](https://help-legacy.corti.ai/migration/user-guide?hsLang=en#engage) - [Clear](https://help-legacy.corti.ai/migration/user-guide?hsLang=en#clear) - [General Platform](https://help-legacy.corti.ai/migration/user-guide?hsLang=en#general-platform) - [Deep Dive Repository](https://help-legacy.corti.ai/migration/user-guide?hsLang=en#deep-dive-repository) - [What's new?](https://help-legacy.corti.ai/migration/whats-new?hsLang=en#main-content) - [Release Notes 2024](https://help-legacy.corti.ai/migration/whats-new?hsLang=en#release-notes-2024) - [Release notes 2023](https://help-legacy.corti.ai/migration/whats-new?hsLang=en#release-notes-2023) - [Corti Co-Pilot](https://help-legacy.corti.ai/migration/corti-co-pilot?hsLang=en) - [Default HubSpot Blog](https://3997889.hs-sites.com/blog) [![](https://help-legacy.corti.ai/hs-fs/hubfs/Corti%20Logo-1.png?width=617&height=200&name=Corti%20Logo-1.png)](https://help-legacy.corti.ai/?hsLang=en) Can't find what you need? Reach out through https://corti.zendesk.com/hc/en-us Copyright © 2026, Corti