[asterisk-bugs] [JIRA] (ASTERISK-27303) [patch] chan_sip: Choppy MoH when channel on hold and bridge is native_rtp

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp closed ASTERISK-27303.
-------------------------------------

    Resolution: Suspended

> [patch] chan_sip: Choppy MoH when channel on hold and bridge is native_rtp
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-27303
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27303
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.17.2, 14.6.2, 15.0.0
>         Environment: Debian Linux
>            Reporter: Vitezslav Novy
>            Assignee: Vitezslav Novy
>            Severity: Minor
>              Labels: patch
>         Attachments: framehook.patch, scenario1-full.log, scenario1.pcap, scenario1-sip.conf, scenario2-full.log, scenario2.pcap, scenario2-sip.conf
>
>
> Scenario:
> answered call A <--> B, both chan_sip, bridged with bridge_native_rtp
> HOLD button is pressed on phone B
> reINVITE with a=sendonly is sent from B to asterisk
> Now there are 2 variants
> 1/ direct media is in action
> asterisk answers to reINVITE with IP address of A as media endpoint but puts A on hold and starts to feed A with MoH
> Phone A receives 2 RTP streams one with MoH from asterisk, one directly from B 
> 2/ media via asterisk
> answer to reINVITE is without problem here
> A is put on hold
> MoH generator started
> function  native_rtp_framehook in bridge_native_rtp.c receives AST_CONTROL_HOLD from channel A and stops the bridge, which is good state
> But immediatelly after that same function recieves AST_CONTROL_UPDATE_RTP_PEER and starts the bridge
> Result is A receives 2 RTP streams, one from MoH genetartor, one from phone B via bridge
>  
>  



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