The whole point of provisioning phones is to eliminate the difficulties associated with manually configuring a large number of devices: It is a tedious task It can be very time consuming Possibility of Human Error Retaining a Standard Config Enterprise-Wide Time, Time Zone, DST Settings The goal here is to get all phones to display the correct Time, including the correct adjustment for Time Zone and DST. We can configure all the phones to get the same settings by setting the necessary Custom Parameters to the correct values. Time A phone will first need to obtain its Time Reference – this is always in UTC format. The industry-standard method to deploy this information is for the device (in our case a phone) to query for this using NTP (Network Time Protocol), sending the request to an NTP server. 3CX PhoneSystem comes preconfigured to point all provisioned phones to: pool.ntp.org …but this can obviously be customized should the need arise. Time Zone The next component is the Time Zone.

This document will provide an overview of the more common concepts which need to be kept in mind when configuring 3CX PhoneSystem inside your network infrastructure, including the following topics: NAT Configuration STUN Resolution DNS Resolution in a VoIP environment Custom Configuration for particular network layouts Different types of VoIP Provider Accounts Custom Source Identification for VoIP Provider SIP message exchange NAT Configuration Number one on the VoIP provider configuration check list is the Port forwarding (also known as port publishing) on your NAT device. If your PBX is operating from an average network i.e.

When using a virtualized operating system and 3CX Phone System, you may experience Stuttering voice quality if you have not configured your virtual environment correctly. This article explains how pm timers on the machine may affect hyper v or vmware instances in which the guest os is Windows XP or server 2003. Scenario – Hyper V installation with XP or 2003 guest operating system Problem – In these operating systems, you may encounter a situation where the IVR music files being played have jittery or bad audio. To resolve this problem: Limit your configuration to 1 virtual processor Limit the configuration to use 1 virtual processor in Hyper V Settings, Processor, and set the number of logical processors to 1. If you require 2 virtual processors You will have to modify the Boot.ini file to use the /usepmtimer switch. To do this: Log on to the computer with an account that has administrative credentials

The 3CX Phone System IVR service is based on VXML and therefore integrates with the web server that you have chosen to use with 3CX. If there are problems with the web server integration, the IVR service may return the following error – “Error in the Ivr, Sorry”. This article describes what you can check if you are running IIS. In some cases, other applications running on IIS (Internet Information Services) will modify the 3CX Web settings. Missing Prompts The most likely cause is missing prompts. In this case the error will only happen for certain prompts or menus

With a Beronet Card, and proper configuration, you are able to choose the exact line/port on which you want to dial out. This feature is requested for lines that have different MSN/DID/DDI numbers. In addition it is useful for companies that are sharing a PBX and want to have each company use ‘their’ telephone line so as to ensure transparent billing. This article explains how to configure this using a Beronet Berofix card. For this scenario we will need the line numbers for each ISDN line.

How to configure Secure SiP This is a complete guide that will provide detailed information on how to: 1. Setup 3CX Phone System with Secure SiP (TLS) (In this way the SiP messaging will be encrypted and therefore more secure) 2. Create certificates with Simple CA. 3. Use Microsoft’s inbuilt importer for trusted certificates and 4.

This article describes how to setup Microsoft Exchange 2007/2010 server as a Unified Messaging Server and configure 3CX Phone System to use it for voice mail and auto attendants This guide has been tested with the following components:Exchange 2007 SP1 RU8 and Exchange 2010 RTM 3CX Phone System version 8.0 and above 3CX Phone System must be installed on a separate machine. . . Step 1: Exchange configuration Exchange integration is not available in the free version of 3CX Phone System. Exchange Server 2007/2010 must be installed with “Unified Messaging Role” enabled. For SBS 2008 you need premium user licenses to enable UM for the users. Figure 1:Main exchange server setup=

3CX administrators need to plan ahead on how to construct their 3CX Phone System. Now it is very time consuming to create 1 extension at a time for each user, with their settings and provisioning. There is a very simple way to achieve this – creating a .csv file and importing it. You can create any number of extensions in seconds. Click here to download a sample import file in Microsoft Excel format.

Introduction This article describes how an extension or a gateway line registers itself with the PBX Server to make itself available for making and receiving calls, and how the PBX Server will register itself with a VoIP Provider to make itself available for making and receiving calls. We trace through these steps by reading the server status log. The Server status log can be accessed by going to the 3CX management console and clicking on the Phone System > Server status log. Scenario 1 – Extension Registration Log message 1 [CM504001] (all logging levels) Ext.100: new contact is registered. Contact(s): [sip:100@172.18.130.27:50386;rinstance=aa14540e328cb432] 3CX Phone System has received a registration request from a device as Ext.100, and has accepted the request because the credentials match. Ext.100 has IP address 172.18.130.27, and will be listening for incoming calls from the PBX Server on port 50386

During set-up you are prompted to enter the FQDN of the phone system server OR the SIP domain. This SIP domain is used if you wish to use Direct SIP calls ( more info here ), but it also affects your installation in case you wish to use FQDNs in the phone configuration. If you intend to address the PBX using IP Addresses only, and do not intend to use “Direct SIP”, then all you will need to do is enter the PBX’s Private IP Address in the SIP Domain field. The rest of this document will not apply