Skip to content
+90 850 885 27 43 info@argeict.com

Business applications

IP PBX and contact center infrastructure

ARGE ICT builds and operates the cloud server, network, firewall, call recording storage, and backups behind the IP PBX and contact center software you choose, in a virtual private cloud (VPC) dedicated to you on ARGE Cloud or in your own environment.

An IP PBX is software that manages telephone calls over the internet protocol. It defines extensions, routes each incoming call to the right person or queue, and records the conversation. Contact center software adds agent queues, reporting, and a link to your CRM. If the PBX server stops, no outside calls come in and recording stops with it.

We do not provide phone numbers, SIP trunks, call minutes, or voice carriage; those are carrier services, and you buy them from your own carrier. We also do not sell PBX or contact center software licenses or IP phones. You choose the software; we build and operate the server it runs on, the network, call recording storage, backups, and monitoring.

A carrier's cloud PBX service versus a PBX on a cloud server

Anyone searching for what a cloud PBX is will mostly find a package from a carrier. In that package the PBX runs on the carrier's server, and numbers and minutes are bundled in. The carrier decides where the server and the recordings are kept.

Our model is different. The PBX software runs under your own license on a cloud server in a VPC set aside for you. The SIP trunk comes from any carrier you like. Call recordings stay in your own area, on infrastructure we run in a data center in Istanbul. Changing carriers does not mean moving the PBX; the new trunk details are simply entered into it.

When you need it

  • The PBX runs on an old server in a server room, and there is no ready replacement if it fails.
  • Your contact center is growing and the server no longer keeps up as agents are added.
  • Agents work from home and need a secure connection to the PBX.
  • You cannot show where call recordings are kept or who can listen to them.
  • Branches will connect to a single PBX.
  • You want to link the PBX to your CRM so that a customer record opens from the caller's number.

PBX software we install

We build the server for the software below. For each one, you get installation and configuration support from the vendor or the firms it works with; we prepare and operate the server and the network. Before installation we confirm the system requirements in the vendor's documentation.

  • 3CX. 3CX V20 was rebuilt on Debian and can be installed on your own server.
  • FreePBX. FreePBX 17 is officially supported on Debian 12 and uses Asterisk as its engine; the default is Asterisk 22.
  • Asterisk. Asterisk is the PBX engine that runs underneath FreePBX and Issabel. If you install Asterisk directly, without an interface, we prepare the server the same way.
  • Issabel. Issabel 5, announced in April 2024, is based on Rocky Linux 8.8; Asterisk 16 or 18 is chosen at installation.
  • Yeastar. Yeastar P-Series Software Edition is the version installed on your own server or a virtual machine; VMware, Hyper-V, KVM, and Proxmox VE are supported. We confirm which one fits your environment before installation.

If you think of the PBX as a SIP server or a VoIP server, the logic is the same: we prepare the server, and the software itself runs under the vendor's rules.

The network for call quality and security

Calls are set up with SIP (Session Initiation Protocol), and the voice itself is carried with RTP (Real-time Transport Protocol). The registered ports for SIP signaling are 5060 (UDP and TCP) and 5061 (TLS). The RTP port range depends on the software, and we confirm it in the vendor's documentation.

  • Firewall. We allow SIP traffic only from the addresses your carrier gives us. Because SIP traffic arrives over the internet, this rule is the most important protection.
  • Encryption. If the PBX supports it, we encrypt SIP signaling with TLS and voice with SRTP. SRTP adds confidentiality, message authentication, and replay protection to the RTP stream (RFC 3711).
  • Scans and password attempts. We write rules against SIP scans and password guessing from outside; repeated attempts are blocked.
  • Voice priority (QoS). On the branch and head office network, we set rules that give voice traffic priority. According to ITU-T G.114, most applications are not noticeably affected while one-way delay stays under 150 ms, so we keep the network path short.

Call recordings and KVKK

Call recordings contain personal data. Under Law No. 6698 on the Protection of Personal Data (KVKK), you are the data controller. You decide which recordings to keep, for how long, and what notice to give callers. We do not make those decisions and we do not give legal advice.

We build the infrastructure measures for storing call recordings:

  • Recordings stay in the Istanbul data center, in a VPC dedicated to you.
  • Encrypted storage.
  • Role-based access: an auditor can listen to recordings, while a system administrator reaches the server, not the recording.
  • Access logs that show who listened to which recording and when, collected in a central log system (SIEM).
  • Backups of the recordings kept in the isolated backup area.
  • A scheduled task that deletes recordings once the period you set has passed.

Infrastructure measures alone do not meet your KVKK obligations; for the legal side, consult your legal counsel.

Scope

  • Server. We build the Linux or Windows server in the version the PBX requires and apply patches on a schedule.
  • Recording storage. We set up the area where recordings are written, its size, and its access rules.
  • Backup. We back up PBX settings and recordings to the isolated backup area. We test restores and report the result in writing.
  • High availability. If the PBX supports it, we can optionally build a second server that takes over when the first fails.
  • Monitoring. We monitor the server, disks, the PBX service, and backup results, and the infrastructure is monitored 24/7. Response scope is written in the contract.
  • Access. The management interface is reached over SSL VPN or ARGE ZTNA; PBX administration is not exposed to the internet.

Head office, branches, and agents working from home

Head office and branches reach the PBX in one of three ways. The right one depends on the type of line and the number of branches.

  1. Your carrier's MPLS line. Your internet service provider's MPLS line links head office and branches. MPLS is a private line that carries traffic without crossing the internet.
  2. MPLS with a private link to ARGE Cloud. The same line is extended to ARGE Cloud. Even when the PBX is in the cloud and the phones are at a branch, voice does not cross the internet.
  3. IPsec when there is no MPLS. Over the existing internet line, we set up an encrypted IPsec tunnel with SD-WAN capable routers and firewalls. SD-WAN manages several lines and steers traffic to the better one.

Agents working from home connect to the PBX over SSL VPN or ZTNA. A telephone application on the computer is called a softphone; the agent makes and takes calls with it through a headset. We describe the options in the head office and branch connectivity section.

CRM, ERP, and agent desktops

If the PBX and the CRM run in the same VPC, integration traffic such as opening a customer record from the caller's number does not cross the internet. Configuring the integration and supporting its functions rest with the software vendors; we provide the network the two servers use to reach each other. The CRM module of Canias includes a PBX integration. How we prepare the CRM server is covered on the CRM infrastructure page.

If you would rather keep agent desktops in a central place than install them on every computer, you can use virtual desktops (VDI).

Out of scope and limits

We do not provide numbers, SIP trunks, call minutes, or voice carriage. We do not sell PBX or contact center software licenses or IP phones, and we do not provide functional support for the software; we are not an authorized partner of PBX vendors. For legal matters such as call recording, privacy notices, and retention periods, consult your legal counsel.

How we work

  1. We map where the PBX runs today, the software in use, the number of agents and branches, and the line details.
  2. We confirm the vendor's server and network requirements in its documentation and propose the design to you in writing.
  3. Before the move we back up the PBX settings and test the restore. We do the cutover outside working hours. You or your carrier redirect the SIP trunk to the new address; we handle the network side.
  4. We report backup results and capacity trends; the frequency of the report is written in the contract.

Service models

  1. On ARGE Cloud: The PBX runs as a cloud server in a VPC dedicated to you, on infrastructure we run in a data center in Istanbul. Data stays in Turkey. We size the design to how long your contact center can afford to be down, and if needed we keep a second server ready at a disaster recovery site.
  2. In your own environment (on-prem): We design and manage the server setup the PBX runs on in your building. We work out the hardware you need for your agent count, help you with hardware purchasing and licensing, and after installation we keep managing, maintaining, and monitoring the environment.
  3. Together: The PBX runs at your site, and recording backups go to the isolated area on ARGE Cloud.

Technologies we use: Linux · Windows Server · SIP · RTP · SRTP · TLS · VLAN · IPsec · SD-WAN · MPLS · SIEM

For server options, see our cloud server page.

Frequently asked questions

Do you provide numbers or SIP trunks? No. Numbers, SIP trunks, and call minutes are carrier services, and you buy them from your own carrier. We build and operate the server and network the PBX software runs on.

How is this different from a carrier's cloud PBX service? In a carrier's service, the PBX runs on the carrier's server, and numbers and minutes are bundled in. With us, the PBX software runs under your own license on a cloud server in a VPC dedicated to you, and you buy the SIP trunk from any carrier you like.

Do call recordings leave Turkey? Recordings of a PBX running on ARGE Cloud are kept in the Istanbul data center, in a VPC dedicated to you. If we build the server in your own environment, recordings do not leave your building. If the software sends data to a vendor cloud, we ask the vendor about it before installation.

Does this service make us KVKK compliant? No. As the data controller, you decide which recordings to keep and for how long. We only build the infrastructure measures: data staying in Turkey, encrypted storage, role-based access, access logs, and an isolated backup.

Can you migrate our existing 3CX or FreePBX system? We can if the vendor supports the target server version. Configuring the software stays with the vendor; we prepare the server, back up the settings and move them to the new environment, and handle the network side. You or your carrier redirect the SIP trunk to the new address.

What happens if the internet goes down? If the PBX is in the cloud, calls to the outside may stop when the internet line drops, and we do not promise a fixed time or guarantee. To reduce the impact, we assess a second internet line and an SD-WAN option with you.

Talk to us about IP PBX infrastructure

Tell us which PBX software you use and how many agents and branches you have; we reply within 1 business day.

Request an infrastructure call