For a normal functioning of Ip Pbx we do not need Internet unless the customer needs remote extensions. As support & some of support components require internet, we advice you to provide internet to server taking necessary precaution as deem fit under your networking policies. The impact of not providing internet is explained in detail in the subsequent question.

Our support is entirely on Internet and it is mandatory to have internet on the server whenever there is a requirement of support.

Some of our customer's provide Static IP with port 80 & 22 open so that we have complete support access and can manage the installation with ease, though we do not insist this being done as it is 100% insecure.

The least we require is connectivity over Anydesk or Teamviever under your supervision for any support requirement which is second best to the previous option .

We also request you to whitelist FTP Port 21 traffic to 'trustcare.in'  , that creates a back up of your settings and voice files which can help you restore when in need though not mandatory. By closing this option, entire data back up is customers responsibility which at best in the event of harddisk crash we will be able to restore to the latest software version with whatever data you have managed to back up. With our server connectivity we will be able to restore the system to the last configured position barring the user private data. You can refer Data Handling Policy to understand what data we back up and what we do not to take an informed decision whether to provide access or not.

Any Ip Phone that is compatible with SIP protocol will work with Com1 Ip Pbx. Though it is impossible to list out thousands of model available in the market today in the world,  we can quote Grandstream, Sangoma, Fanvil, Dinstar &  Akuvox to name a few brands of repute that is available in India and the world.

The preference of softphones varies from each customer and fine tuned over their experience with each of them, nevertheless we  have given the following comparison  of the most popular and widely used softphones to have a reference.

You can connect any PCM/TDM Epabx over PRI / SIP Trunking. We have successfully connected and tested with Matrix, Syntel, Avaya, Alcatel & Samsung.

In most cases we can access trunk from the other system extension and vice versa , also  forward the incoming call over to each other system but final feasibility of such operation is to be practically explored.

With more requirements of Call center applications, Automated dialing, Hospital requirements like Code Red / Code Blue, API integration with the CRM are being explored by corporates and SME's, this integration presents a huge opportunity to protect the existing investment as well as get the new modern requirements be met with Com1 Ip Pbx at a fraction of cost of fully replacing the existing infra.

PJ Sip is a much more advanced SIP protocol that is far more superior as well as less resource intensive. While in com1 we have tested PJ Sip and Beta testing is going on at the background , the expected adoption of PJ Sip is Jan 2022.

WebRTC is the new protocol that does away with the need for a softphone to register SIP extensions and can use a Browser extension to work as a Phone over Https. This gives a complete freedom and flexibility to build a phone in JavaScript and control all phone operation with API's for both Video & Audio communication. We have tested WebRTC and expected adoption is Jan 2022.

Interactive Voice Response (IVR) is an automated phone system technology that allows incoming callers to access information via a voice response system of pre recorded messages without having to speak to an agent. A simple IVR could route calls to the desired extensions, to help customers find answers and perform simple tasks themselves without any hold time by creating menu options via touch tone keypad selection or speech recognition. Com1 Ip Pbx offers multi level IVR with automated options that can help you automate many repetitive tasks with least or nil human intervention.

Static means staying the same.  Yes, static IP addresses don’t change. When the server is connected and configured with static IP, we will be able to reach and access server for any operation at any point of time viz a viz a Dynamic IP which changes every time you switch on/off the modem. 

If customer wants to connect Remote extensions outside the installed premises then it is mandatory to have a static IP or VPN. It is far more easier to support customers who has the system installed over static IP than a support over Anydesk / Teamviewer.

It is imperative to take precaution against huge security risk  that comes with connecting Com1 IP Pbx over Static Ip  including dialing unsolicited premium number ISD calls and stealing of your user data.

There are 2 types of connectivity available. A Simple but Insecure methodology is to connect the server on a Static IP and allow your SIP extensions to register over open internet. Except procuring an internet with static IP for server, there is no other investment to achieve this. Very suitable for SME & small Call centers where being Cost effective scores over security.

On the other hand, if security is more important and infra investment is not a constraint, then creating VPN between the server and remote extensions is the way to go. This is more secure and perils like hacking is handled better in this type of network.

This term is nearly irrelevant when it comes to Ip Pbx technology. In PCM/TDM the terminal equipment's are always connected with the CPU sucking valuable resources including powering the terminal equipment's for dial tone even in Idle condition & other tones like ring back / engaged tone etc whenever the event occurs. In Ip Pbx the system communicates with the server only when the server receives an incoming call / when the dialing is terminated for outgoing from extensions , till then it is just a registration of service and nothing else.

Being the proprietary hardware with design & space constraint , provision for the latest high speed processor or higher capacity RAM or higher capacity storage is virtually impossible in PCM/TDM EPABX. In Ip Pbx since the hardware is equipped with latest processor and high capacity RAM or better hard disk, generally we do not come across a blocking scenario in practical application.

This is very relevant for any PCM/TDM EPABX, as all the hardware is proprietary and the customer is at the mercy of both manufacturer & local dealers capability to handle critical break down. Some of the manufacturer take this as a business opportunity to design redundant Power Supply / Redundant CPU and auto take over as a great design feature and charge a hefty additional cost.

With Com1 Ip Pbx, the hardware is a normal PC/Server. Firstly PC/Server is multiple times more reliable than a PCM/TDM EPABX. Secondly all the spares are locally available and can be made functional in a fraction of the time than PCM/TDM EPABX as at times the spares have to travel from out of station. Thirdly to make it even more simple, every company will have some PC or the other which is not extensively used or with non critical application that can be made functional by loading our software in 1 hour.

As some corporates have this redundancy as a policy, we offer the second redundancy license at 50% cost of original license where customer can buy another set of hardware and use it during failure. We have 2 redundant server installations in Star Health Insurance which was never used for over 5 years.

Any system that is connected to a Static IP can be hacked or will be hacked. Hacking attempt will start in less than 5 minutes of any new server is connected to a Static IP. In a nutshell, this is not a problem of Com1 Ip Pbx or any Ip Pbx but even to PCM/TDM EPABX as well. In the last 8 years we do not have any instances of revenue loss reported by our customers due to protection from our in built Firewall. Yet will we lift our collar , and make a tall claim of no hacking ... a clear 'NO'. More about this subject and precautions are discussed in this link - Network Update & Risk Of Hacking in EPABX

The following table throws some lights on the number series that needs to be avoided. In a nutshell 700 - 999 to be avoided in 3 digits as well as 9000 to 9999 to be avoided in 4 digits. Customers can have combination of 3 digit or 4 digit extension numbers or n digit extension numbers.

In a nutshell, the same can be explained as "Software is as secure as the "Network" in which the same is deployed. Security of the software is more a Network issue than the software issue. The software neither steals your data not allows hackers to hack and make calls to premium numbers to leave a hole on your telecom bills. Our role on this is more a advisory than of being responsible for any breach. It is customers responsibility to provide a secure network on which the software can be deployed. This article throws more light on this subject. Network Update & Risk Of Hacking in EPABX