Introduction DTMF (dual tone multi frequency) is the signal to the phone company that you generate when you press an ordinary telephone’s touch keys. In the United States, it’s known as a “Touchtone” phone. DTMF has generally replaced loop disconnect (“pulse”) dialling

3CX Phone System can be installed on most versions of Windows. Below is a complete list of supported and unsupported operating systems. Note: Unsupported does not necessarily mean that 3CX will not work, however it does not get tested by our testing team and we will not be able to assist with issues. Some supported Operating Systems might require use of Cassini. 3CX Phone System Version 8 Supported Windows XP Home Editions (Cassini Only) Windows XP Pro (32-bit) (Cassini Only) Windows XP Professional (64-bit) (Cassini Only) Windows Vista Business (32-bit & 64-bit) Windows Vista Ultimate (32-bit & 64-bit) Windows 7 Home Basic/Premium Edition Windows 7 Professional (32-bit & 64-bit) Windows 7 Ultimate (32-bit & 64-bit) Windows 2003 Standard/Enterprise/DataCentre Editions (32-bit & 64-bit) Windows 2003 R2 Standard/Enterprise/DataCentre Editions (32-bit & 64-bit) Windows 2003 Web Edition (Cassini Only) Windows 2003 R2 Web Edition (Cassini Only) Windows 2003 SBS Windows 2003 SBS R2 Windows 2008 Foundation/Standard/Enterprise/DataCentre (32-bit & 64-bit) Windows 2008 R2 Foundation/Standard/Enterprise/DateCentre (64-bit) Windows 2008 Web Edition (Cassini Only) Windows 2008 R2 Web Edition (Cassini Only) Windows 2008 SBS (64-bit) Windows 2008 SBS R2 (64-bit) NOT Supported Windows 2000 and earlier Windows XP Media Centre Edition Windows Vista Home Basic/Premium Edition Windows 7 Starter Edition Windows 2008 for Itanium-based Systems Windows 2008 R2 ServerCore/Storage Previous Versions 3CX Phone System Version 7 Supported Windows XP Professional 32 bit Windows Vista Business 32 bit Windows Vista Business 64 bit Windows 2003 Standard 32 bit Windows 2003 Standard 64 bit Windows 2003 Enterprise 32 bit Windows 2003 Enterprise 64 bit Windows SBS 2003 Windows 2008 Standard 32 bit Windows 2008 Standard 64 bit Windows 2008 Enterprise 32 bit Windows 2008 Enterprise 64 bit Windows SBS 2008

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

Many businesses who are adopting VoIP Software PBX Systems are always looking for a way to cut down costs. That’s where the Intel Atom N270 comes in the picture, which is  designed to deliver performance with minimal power usage. In addition many of our partners have requested the ability to put together a low cost dedicated server based on an Intel Atom.  The Intel Atom N270 can be found in many low cost servers and these can be used to create a low cost dedicated 3CX server.  In this post we take a look at such a device, the Allnet FW8888 and run some bench mark tests against it to see how it performs. Allnet FW8888 Hardware Specifications: CPU: Intel ATOM N270, 1.60 GHz Dual Core (Hyperthreading) North Bridge: Intel 82945GSE, MCH- North bridge Intel 82945GSE, MCH-North bridge South Bridge: Intel 82801GBM, ICH 7M- South bridge Intel 82801GBM, ICH-7M South bridge Expansion: 1xPCI Expansion Card RAM: 2x 1GB DDR Storage: 1x IDE 1x IDE 1x CF 1x CF 2x SATA / Raid 2x SATA / Raid 6 Gigabit LAN controllers: (Yes 6) 1x -Intel 83572EI PCIe GbE Controller miniGBIC (SFP) 3x Intel 82574L PCIe GbE Controller RJ45 2x Intel 825741 PCI GbE Controller RJ45 Housing: 19″ Rack / 1HE 19 “Rack / 1U HDD: 250GB SATA PSU: 230V / ATX / 250W Max We will be focusing on the Atom’s functionality with 3CX, but before doing that, here’s some general information on the Atom’s general performance shown in the Windows Experience Index just to give a quick view of how Windows 7 Enterprise edition rates this device.

Introduction to the 3CX Media Server The 3CX Phone System’s main job is to connect 2 (or more) entities together for transmission of audio between them. However, there are 3 different mechanisms which can be utilized for the delivery of audio streams between 2 endpoints: Bypass Mode (Direct) Proxy Mode (Pass-Through) Transcoding Mode (Bound to Media Server) Audio streams are delivered by the 3CX Media Server. The inbuilt 3CX Media Server can recognize whether the call is an internal call an external call by making a calculation based on the comparison of the 3CX Phone System Local IP address and Subnet mask, it’s interfaces and those of the settings set on the phone or party. This is one of the 3CX Main core services. By Pass – Direct Mode In this mode, media server does not take any part in the RTP stream delivery between two sip entities. Both entities will negotiate with the PBX to send the RTP stream directly to each other.

If the Media Server needs to allocate a port for media transmission, and cannot bind, it will generate a log message such as: MediaServerReporting:InitEndPoint [MS003003] C:179.1: RTCP socket 10.0.0.173:7023 binding failed with error code 10048 This is due to some other application already binding to some ports in the 7000-7499 range. Typically it is the Microsoft DNS server doing this. To check which ports are bound at any point in time, you can run the following command from the DOS prompt: netstat -ano -p UDP Microsoft Windows allows you to define which port ranges will NOT be returned to any application/service that requests a random port number, via the following registry entry: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParametersReservedPorts To ensure correct functionality, you should add the following ranges, without removing whatever the value already contains: 3478-3478  – STUN / Firewall Checker 5000-5000 – MyPhone Interface 5060-5090 – SIP Port for 3CX PhoneSystem and Tunnel Ports 5480-5490 – Management Console, FAX Server, Other 3CX Components 7000-7499 – range of RTP ports for Local Connections 9000-9049 – range of RTP ports for External Connections 10000-10500 – range of RTP ports for Fax (10000-10001) and Tunnel Connections 40000-41000 – Conference, IVR, Parking Orbits If the value already contained “1433-1434”, the end result would look something like this (click on image to enlarge): For more specific instructions regarding this registry entry, refer to: http://support.microsoft.com/kb/812873/

Receiving faxes from VoIP Providers Incoming faxes from VoIP Providers can be quite tricky when compared to receiving of faxes from PSTN, ISDN VoIP Gateways. The main reason for this is NAT. Therefore some tweaks need to be made to the 3CX Fax Service Configuration Files. IMPORTANT: VoIP Provider testing of the 3CX Fax Server was performed in March 2010 and this document was updated with the new information. The NAT changes described in this document apply for the following VoIP Providers: Inphonex, and Actiopl Some VoIP Providers do not need this setting but others will not work without it.  The best thing to do is to leave the configuration unchanged and try with the default configuration files as shipped by 3CX

The following is a complete list of ports that 3CX PhoneSystem uses in a default installation scenario: TCP:80 … If 3CX is installed for IIS, this is the default port number to reach the 3CX Management Console (http:// /management) and the 3CX MyPhone Interface (http:// /myphone) TCP:5000 If 3CX is installed for Cassini, this is the default port number to reach the 3CX MyPhone Interface (http:// :5000) UDP:5060 3CX Phonesystem (SIP) UDP&TCP:5080 UDP&TCP:5081 etc Listener for the 3CX Tunnel Protocol for bridge connections. Each tunneled bridge connection binds to a port number incrementally. UDP&TCP:5090 3CX Tunnel Tunnel UDP:5100 3CX Fax Receiving Service (SIP) TCP:5480 3CX PhoneSystem Database Server (PostgreSQL) TCP:5481 If 3CX is installed for Cassini, this is the default port number to reach the 3CX Management Console (http:// :5481) TCP:5482 3CX PhoneSystem for inter-process communications TCP:5484 3CX IVR vXML Server (both IIS and Cassini install scenarios) TCP:5485 3CX Configuration Server UDP:5486 3CX Assistant Server UDP:7000-7499 Default Range of ports for RTP Media Exchange with devices on the LAN (typically internal extensions, gateways, tunneled connections) UDP:9000-9049 Default Range of ports for RTP Media Exchange with devices on the WAN (typically voip providers, external extensions) UDP:10000 3CX FAX Receiving Service for T.38 UDPTL traffic UDP:40000 3CX Parking Orbit Service (SIP) UDP:40010-40138 3CX Parking Orbit Service (RTP) UDP:40300 3CX Conference place Service (SIP) UDP:40310-40438 Conference place Service (RTP) UDP:40600 3CX IVR Service (SIP) UDP:40610-40866 3CX IVR Service (RTP)

What is a FoIP FoIP – FAX over IP, is the technology used to allow faxing via the computer network. Because Fax is not ideally suited to travel via a normal phone call, the T38 protocol was developed. A FoIP (FAX) call is very similar to a normal VoIP (voice) call. In essence it is a call that transmits FAX data over an IP network. How the 3CX Phone System FAX Server Service receives Faxes 3CX Phone System has a separate fax server service, that acts as a SIP clients and is dedicated to receiving faxes. What is the difference between a FoIP call and a VoIP call?

When is a call internal or external? Calls are decided to be either local or external based on whether the contact IP of an inbound SIP packet is local or not. To check whether the IP is local, 3CX Phone System uses the following process: It queries all IPs assignedto the PC on which it is installed. Using the subnet masks assigned, it checks whether the IP is local ACCORDING to windows. In addition, it also checks a configuration file for a list of local subnets.