[Home]

Summary:ASTERISK-26224: Asterisk not sending out some rtp packets from ConfBridge App
Reporter:Marco Nicoloso (mnicolos)Labels:
Date Opened:2016-07-21 05:44:15Date Closed:2020-01-14 11:21:05.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Applications/app_confbridge
Versions:11.13.0 Frequency of
Occurrence
Related
Issues:
Environment:Linux CentOS 6.5 x64Attachments:
Description:Starting this thread as Information Request.
Our system, based on Asterisk 11.13 has as much as 100 SIP channels continuously recorded and inside conference app_confbridge.
Users on demand can connect to these conference bridges, hear and talk into conference.
Hardware is correctly dimensioned to hold up to nearly 2000 simultaneous conferences in the confbridge with 2 channels present in each of them.
The effect is that users can hear with their client some short audio breaks  (20ms-60ms) when connected to these conferences. The problem happens quite frequently and we discovered that is not a network problem, as RTP traffic is correctly QoS-prioritized and we have no packet drops.
The problem showed up evidently when we started the registration of channels through Confbridge App. On 1 hour of registration we lose about 70 seconds of samples. (That's about 600000 samples at 8 kHz)
We are using u-law everywhere.
Even when the remote channels are located in very different networks, on the historical VuMeter of our client we can see short audio holes at the same time on those channels.
That's why I am addressing this question...
Could the issue be related to timing source? Can I have an advice on how to solve the issue?
Thanks.
Comments:By: Asterisk Team (asteriskteam) 2016-07-21 05:44:16.200-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) 2016-07-21 05:44:17.180-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.

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].