Summary:	ASTERISK-29642: Does UDP error causes high peer latency?
Reporter:	Robert Peregrin (robert.peregrin)	Labels:
Date Opened:	2021-09-13 21:55:35	Date Closed:	2021-09-13 21:55:40
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Applications/General
Versions:	16.12.0	Frequency of Occurrence
Related Issues:
Environment:	CentOS Linux 8 (Core)	Attachments:
Description:	We are experiencing very high peer latency between our Media Gateways (running ASTERISK) and Genesys OCS Servers and Opensips Server. The latency is going above 5 seconds and sometimes even reaching 20 seconds. In the worst case, it even become totally disconnected/unreachable. We have done many adjustments in Network side to separate the voice traffic from other traffic but to no avail. Our Network Team has noticed the below errors in Grafana and they are saying that this is the cause of the high peer latency. 1. InErrors - UDP datagrams that could bot be delivered to an application 2. NoPorts - UDP datagrams received on a port with no listener. May we ask for help to check what if the Grafana errors is really related to the peer latency? We are experiencing this issue very frequently. Restart of ASTERISK service does not help. We would appreciate any recommended steps to investigate on the high peer latency.
Comments:	By: Asterisk Team (asteriskteam) 2021-09-13 21:55:40.009-0500 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2021-09-13 21:55:40.963-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].