[asterisk-bugs] [JIRA] (ASTERISK-28342) Ast-to-Ast setup using the same rtcpinterval crashes RTCP and audio stream

[Sean Bright (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Bright closed ASTERISK-28342.
----------------------------------

    Resolution: Workaround Available

Thanks [~speeddialdave]. It would be nice to know why connection tracking is causing this problem and if Asterisk is doing something to trigger it, but because we have a workaround (disabling connection tracking for ports Asterisk uses) I think we are safe to close this. We can re-open if someone stumbles on additional information in the future or this becomes a larger problem.

Thanks for following up!

> Ast-to-Ast setup using the same rtcpinterval crashes RTCP and audio stream
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-28342
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28342
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.21.1, 16.2.1
>         Environment: CentOS 7 (7.6-1810 x86_64)
>            Reporter: Speed Dial Dave
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: pjsip
>
> When stress-testing PJSIP and Asterisk 16.2.1 by doing direct calls between two identically configured Asterisk setups (over both WAN and LAN) I noticed a specific error message that kept showing up in the logs:
> res_rtp_asterisk.c: RTCP SR transmission error to 1.2.3.4:12345, rtcp halted Operation not permitted
> This started showing up when my tests reached about 200 simultaneously connected calls between the two Asterisk setups. At this level, after a total of 15k calls, the error showed up about 70-80 times on the Asterisk doing the dialing, and about 10-15 times on the one receiving the calls; at ~350 simultaneous calls the number of errors was much higher. When this error popped up the outgoing audio stream ("us") also dropped out from the affected calls, but the channels didn't crash and the calls kept going and finalized normally without any other apparent error.
> As "operation not permitted"/EPERM should be a permission error I first fiddled around with increasing various ulimits as I thought it was some resource starvation, but without luck. After experimenting with various config changes for Asterisk I at one point had different rtcpinterval (rtp.conf) values on the two machines - one was set to 3000 and the other to 6000 - and this completely cleared the problem. Running my test several times more with the two machines having an rtcpinterval difference of only 500 I couldn't get the error to show up again, even when stepping it up to 600 simultaneous calls.



--
This message was sent by Atlassian JIRA
(v6.2#6252)