[asterisk-bugs] [JIRA] (ASTERISK-30275) Asterisk sending phantom RTP packet with wrong sequence number

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-30275:
-------------------------------------------

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Can you please also provide the core debug level logs as well.

A packet is being sent outside of the bridged mechanism, which is causing it to use different information. The core debug log may show why exactly it happened.

> Asterisk sending phantom RTP packet with wrong sequence number
> --------------------------------------------------------------
>
>                 Key: ASTERISK-30275
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30275
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_native_rtp
>    Affects Versions: 18.9.0, 18.12.1, 18.15.0
>         Environment: Ubuntu 22.04
> Ubuntu 20.04
>            Reporter: John M
>            Assignee: Unassigned
>            Severity: Major
>         Attachments: capture.pcapng, messages.log, pjsip.conf
>
>
> 1. It only happens on the caller channel.
> 2. The issue only happens when using the bridge_native_rtp.so locally
> 3. The issue doesn’t happen if I set directmedia=yes and native_rtp is remote since Asterisk doesn't pass RTP in this case.
> 4. The issue doesn’t happen if I do noload => bridge_native_rtp.so and use only simple_bridge.
> 5. The issue seems to also only happen during early bridging. If early bridging is not used the issue doesn't seem to happen.
> Issue is detailed here: https://community.asterisk.org/t/asterisk-sending-rtp-with-wrong-sequence-number/94468



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