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

[John M (JIRA)]

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

John M commented on ASTERISK-30275:
-----------------------------------

I am attaching a new PCAP with the debug logs as requested.

notice,warning,error,debug,verbose,dtmf
core set verbose 5
core set debug 5
pjsip set logger on
rtp set debug on

This case actually had 2 phantom RTP packets that I also commented on in the PCAP they are the following:

[Oct 27 15:26:58] VERBOSE[62934][C-00000045] res_rtp_asterisk.c: Sent RTP packet to      54.215.108.95:33188 (type 09, seq 022568, ts 2227490808, len 000160)
[Oct 27 15:26:58] VERBOSE[62934][C-00000045] res_rtp_asterisk.c: Sent RTP packet to      54.215.108.95:33188 (type 09, seq 022569, ts 2227490968, len 000160)

This is the first time I have seen 2 instead of 1.

> 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: John M
>            Severity: Major
>         Attachments: capture2.pcapng, capture.pcapng, debug_log_30275.txt, 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)