Difference between revisions of "One way audio problems"

From Kolmisoft Wiki
Jump to navigationJump to search
(One way audio updated)
 
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
One-way audio is a common VOIP problem and there are many possible causes.
One-way audio is a common VOIP problem, and there are many possible causes.




== Firmware  ==
== 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.  
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.  




Line 10: Line 10:


Particularly if NAT is involved in the call path, configuration of the various devices may be a problem.  
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 appropiately for your envioronment.  
Check to see if all devices are configured appropriately for your environment.
 
If Asterisk is on a public IP, and the phone is inside of a NAT device, you need to configure NAT option for those phones (set NAT to "Yes" on Device settings). Also, turn on qualify to keep the NAT session open.  


Finding the Cause  
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. Interperting the resulting captured packets requires some familarity with how networking and VOIP work.  
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


For example, if the call path is:


  VOIP phone/device --< a >-- firewall --< b >-- sip proxy --< c >-- firewall --< d >-- asterisk


== Troubleshooting Steps ==
== Troubleshooting Steps ==


Start capturing at point A  
Start capturing at point A.
Make a VOIP call that will have one-way audio  
Make a VOIP call that will have one-way audio.
Analyze capture  
Analyze the capture.
If problem found, fix and retest  
If a problem found, fix it and retest.
Otherwise move 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 comple 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 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.
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.




== Links for additional info ==
<br><br>


  http://www.voip-info.org/wiki/view/How+To+Debug+and+Troubleshoot+VOIP
= See also =
  http://www.google.com/search?client=opera&rls=en&q=one-way-audio&sourceid=opera&ie=utf-8&oe=utf-8
* [[One-way audio or not audio at all]]
* https://blog.kolmisoft.com/the-causes-of-no-audio-and-one-way-audio-voip-calls/
* 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

Latest revision as of 15:19, 26 November 2020

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.

If Asterisk is on a public IP, and the phone is inside of a NAT device, you need to configure NAT option for those phones (set NAT to "Yes" on Device settings). Also, turn on qualify to keep the NAT session open.

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.




See also