Enterprise IP Phone

Work from the bottom up, one layer at a time, because each layer depends on the one below it. First check power and link: the screen is lit, the switch port shows link (and, if the phone runs on PoE, PoE is enabled on that port with budget left) and the cable is no longer than 100 meters. Then check that the phone has a valid IP address (no address, or 0.0.0.0, means DHCP failed, often because of a wrong VLAN or DHCP scope) and that its SIP account shows Registered; if not, verify the server address, extension, password and transport, and whether the PBX has banned the phone's IP. If calls ring but the audio is missing, one-way or choppy, look at NAT and firewall settings, RTP ports, codecs, jitter and packet loss. Finally, swap in a known-good phone, or move this phone to a known-good port, to learn whether the fault is in the phone or in the network.

An analog phone carries the voice as an electrical signal over a copper pair to a PBX or the telephone exchange and draws its power from that same line. An IP phone digitizes the voice, sends it as RTP packets over the Ethernet network, sets calls up and ends them with SIP and is powered by PoE or an adapter, so it needs an IP-PBX or another SIP device to work with. In practice a single network cable serves both the phone and the PC, the extension number follows the phone to any network outlet, and features such as HD voice, programmable keys and a shared directory become available. The price is that the phone depends on the network and on power, so the switch and the PBX need a UPS and a properly designed network. Existing analog phones and fax machines can be kept by connecting them through an FXS adapter or gateway.

SIP (Session Initiation Protocol), defined in RFC 3261, is the IETF standard for setting up, changing and ending calls; messages such as REGISTER, INVITE, 180 Ringing, 200 OK, ACK and BYE carry the call signaling, normally on port 5060 (5061 for TLS). The voice itself does not travel inside SIP: the two ends agree on codecs and addresses using SDP inside the SIP messages, and the audio then flows as RTP (RFC 3550) on separate UDP ports, which is why a phone can ring and still have no audio. Because SIP is an open standard, phones, door stations, gateways, IP speakers and PBXs from different makers work together and you are not tied to one PBX brand. Vendor-specific extras, such as special key functions, may still depend on the PBX.

If the phones support direct IP calling, two SIP phones can call each other without a PBX by dialing the other phone's IP address (for example 192.168.1.20); this is enough for two or three phones, or for a door station that rings a single indoor phone. Without a PBX, however, there are no extension numbers, ring groups, voicemail, call recording or outside lines, and every device needs a fixed IP address. As soon as you have more than a handful of phones, need city lines or a SIP trunk, or want central management, use an IP-PBX such as an Asterisk-based system (for example FreePBX or Issabel), which can also run on a small server or a virtual machine. Direct IP calls inside the LAN keep working even when the PBX or the internet link is down.

Yes. KDT Radonium phones use standard SIP 2.0 (RFC 3261) over UDP, TCP or TLS, and KDT lists their compatibility with platforms such as Asterisk, FreePBX and BroadSoft; Issabel is built on Asterisk, and any PBX that follows the SIP standard can register them as extensions. Basic features such as hold, transfer, call forwarding and local conference work with any standard PBX, while server-dependent features such as BLF, call pickup, call parking and the message-waiting indicator must also be configured on the PBX itself. For a trouble-free start, keep at least one common codec enabled on both sides and set the same DTMF method on the phone and on the PBX. As with any interoperability project, test one pilot phone against your own PBX before ordering a large quantity.