[asterisk-bugs] [JIRA] (ASTERISK-29138) Asterisk doesn't process ACK on high CPS

[Joshua C. Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252522#comment-252522 ] 

Joshua C. Colp edited comment on ASTERISK-29138 at 10/21/20 6:33 AM:
---------------------------------------------------------------------

The backtrace stated it was in DNS lookup code, and the hostname was one of the parameters.

That FRACK may be fine for you - it really depends on the load of the system and usage. It exists for systems with reasonable usage (at least according to us) where it would never be reached. If you are pushing things extremely, then it could certainly be hit. In that scenario it alone would not indicate an issue.

It's configured used a define in code[1].

You'd need to really dig into the specifics - what object and such - to understand where the FRACK came from.

[1] https://github.com/asterisk/asterisk/blob/master/main/astobj2.c#L574


was (Author: jcolp):
The backtrace stated it was in DNS lookup code, and the hostname was one of the parameters.

That FRACK may be fine for you - it really depends on the load of the system and usage. It exists for systems with reasonable usage (at least according to us) where it would never be reached. If you are pushing things extremely, then it could certainly be hit. In that scenario it alone would not indicate an issue.

It's configured used a define in code[1].

[1] https://github.com/asterisk/asterisk/blob/master/main/astobj2.c#L574

> Asterisk doesn't process ACK on high CPS
> ----------------------------------------
>
>                 Key: ASTERISK-29138
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29138
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.3.0, 17.7.0
>         Environment: CentOS 8 5.8.11-1.el8.elrepo.x86_64
> CentOS 8 4.18.0-193.19.1.el8_2.x86_64
> Ubuntu 5.4.0-51-generic #56-Ubuntu
> Ryzen 2700
> 2 x EPYC 7742
> 10 Gb/s LAN connection
> sipp SIPp v3.6.1-TLS-SCTP-PCAP-RTPSTREAM
> sipp command: sipp -s uac -rtp_echo -nr -trace_msg -trace_err -d 60s -r 75 -l 5000 -i 10.40.1.36 -p 5070 -s 505 10.40.1.58:5060
> Asterisk compiled with default configuration, only selected DONT_OPTIMIZE in menuselect.
>            Reporter: Sergio
>            Assignee: Unassigned
>
> As explained here https://community.asterisk.org/t/pjsip-stack-resends-messages-on-high-cps/86102 on a bit higher load Asterisk seems to fail recognizing the ACK and resends 200 OK during call setup.
> I've attached the core dump, tcpdump, config files and sip/debug logs here https://drive.google.com/drive/folders/1qvg5nNFa32egMss_0SjFubgLaWUBuVmO?usp=sharing
> tcpdump was taken on the machine running asterisk to avoid network issues.
> Issue is consistent, and can be repeated easily.



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