Difference between revisions of "One way audio problems"
| Line 29: | Line 29: | ||
Otherwise move the capture point to the next point (a, b, c, d, etc) and start over. | Otherwise move the capture point to the next point (a, b, c, d, etc) and start over. | ||
If the problem is intermittent, then a long-term simultanous capture at multiple points can be used to attempt to capture a complete call with the problem. Most capture tools will let you capture only traffic from selected devices, so the volume of captured information can be kept to a reasonable size. If a back-to-back SIP user agent (for example a Session Border Controller) is part | If the problem is intermittent, then a long-term simultanous capture at multiple points can be used to attempt to capture a complete call with the problem. Most capture tools will let you capture only traffic from selected devices, so the volume of captured information can be kept to a reasonable size. If a back-to-back SIP user agent (for example, a Session Border Controller) is part of the call path, then it may be necessary to capture all VOIP traffic at some points to ensure catching the wanted call, since the IP addresses can change when traversing this device. | ||
<br><br> | <br><br> | ||
= See also = | = See also = | ||
* [[One-way audio or not audio at all]] | * [[One-way audio or not audio at all]] | ||
* http://www.voip-info.org/wiki/view/How+To+Debug+and+Troubleshoot+VOIP | * http://www.voip-info.org/wiki/view/How+To+Debug+and+Troubleshoot+VOIP | ||
* http://www.google.com/search?client=opera&rls=en&q=one-way-audio&sourceid=opera&ie=utf-8&oe=utf-8 | * http://www.google.com/search?client=opera&rls=en&q=one-way-audio&sourceid=opera&ie=utf-8&oe=utf-8 | ||
Revision as of 11:02, 27 April 2010
One-way audio is a common VOIP problem, and there are many possible causes.
Firmware
Outdated firmware in routers, VOIP phones, firewalls, etc. can cause one-way audio. Ensure you have the latest updates for all the devices in the call path.
Configuration
Particularly if NAT is involved in the call path, configuration of the various devices may be a problem. Check to see if all devices are configured appropriately for your environment.
Finding the Cause The basic troubleshooting technique is to use a tool like Ethereal to capture SIP and RTP packets at each point in the call path where packets could be lost. Interpreting the resulting captured packets requires some familarity with how networking and VOIP work.
For example, if the call path is:
VOIP phone/device --< a >-- firewall --< b >-- sip proxy --< c >-- firewall --< d >-- asterisk
Troubleshooting Steps
Start capturing at point A. Make a VOIP call that will have one-way audio. Analyze the capture. If a problem found, fix it and retest. Otherwise move the capture point to the next point (a, b, c, d, etc) and start over.
If the problem is intermittent, then a long-term simultanous capture at multiple points can be used to attempt to capture a complete call with the problem. Most capture tools will let you capture only traffic from selected devices, so the volume of captured information can be kept to a reasonable size. If a back-to-back SIP user agent (for example, a Session Border Controller) is part of the call path, then it may be necessary to capture all VOIP traffic at some points to ensure catching the wanted call, since the IP addresses can change when traversing this device.
