[asterisk-bugs] [JIRA] (ASTERISK-21246) rtpkeepalive enabled results in empty RTP packets with a marker bit set, plus a ULAW payload instead of CN

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-21246:
------------------------------------

    Summary: rtpkeepalive enabled results in empty RTP packets with a marker bit set, plus a ULAW payload instead of CN  (was: After  RTP is negotiated (ALAW) between two SIP endpoints; Asterisk starts sending ULAW marker packets to both endpoints )
    
> rtpkeepalive enabled results in empty RTP packets with a marker bit set, plus a ULAW payload instead of CN
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21246
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21246
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Resources/res_rtp_asterisk
>    Affects Versions: 1.8.17.0, 1.8.18.0, 1.8.19.0, 1.8.20.1
>         Environment: ubuntu 10.04
>            Reporter: Peter Katzmann
>            Assignee: Peter Katzmann
>         Attachments: asterisk-21246-rtp-cng-payload-error_1.8.diff, asterisk-21246-rtp-cng-payload-error_1.8_v2.diff, asterisk.conf.tar.gz, CallWithTranscoding, codecchange.0, codecchange.2, codecchange-24032013.bz2, codecchange-24032013-udp.pcap, codecchange.3, codecchange-filtered.pcap.gz, codecchange-patched, codecchange-patched.pcap, filtered1512-2-leg.pcap, filtered1512-2.pcap, myDebugLog, myDebugLog, negiot-switch, vanilla-trace.txt, ws-trace.txt
>
>
> See attached traces
> During call asterisk switches the negotiated codec (alaw) in the rtp to ulaw.
> If there is no renegotiation (like on my snom 720 sometimes), the user has a audible distortion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira