Compatible
None
Generally speaking, it is best to stick to the following best practices when deploying a VoIP system on any network:
A number of requirements/questions may be presented about the network.
The following section outlines some common VoIP issues that may arise, and some recommended troubleshooting steps to narrow down the issue.
Consider that voice communication typically happens as two simultaneous UDP streams, one for each direction of communication. These are two separate streams, as opposed to a single two-way stream. If communication in one direction is not making it to the peer, then the symptom is usually that only one party can hear the other's audio.
To address this issue, check the following:
Due to the sensitive nature of VoIP traffic, low voice quality (or "jitter") may be experienced due to interruptions in traffic flow or bandwidth limitations.
To improve voice quality, ensure that the following best practices are in place:
Take note of the "symptoms" exhibited in a poor-quality phone call. Specific traits of the call can help narrow down the issue. Please refer to this cisco guide for a breakdown of different call quality symptoms.
Typically, VoIP equipment will get a dynamic configuration from a TFTP server or other service on the network. This will commonly be levied by a DHCP server, where leases to VoIP endpoints will include voice-specific DHCP options. In the event that the phone fails to connect to the network/get a working configuration, consider the following recommended steps:
The following cisco articles provide additional information not covered in this article, and may be helpful as a reference: