[asterisk-bugs] [JIRA] (ASTERISK-25484) [patch] autoframing=yes has no effect

Alexander Traud (JIRA) noreply at issues.asterisk.org
Wed Oct 21 08:57:32 CDT 2015


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

Alexander Traud updated ASTERISK-25484:
---------------------------------------

    Comment: was deleted

(was: Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].)

> [patch] autoframing=yes has no effect
> -------------------------------------
>
>                 Key: ASTERISK-25484
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25484
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.6.0
>            Reporter: Alexander Traud
>         Attachments: chan_sip_autoframing.patch
>
>
> When I write {{autoframing=yes}} into my {{sip.conf}} configuration file, Asterisk still does not honor the ptime of the callee. This happens, because the function {{ast_rtp_codecs_payloads_copy}} is called afterwards overwriting the saved framing with {{0}}. This was/is no issue in Asterisk 11.
> Actually, this is worse than using the default {{autoframing=no}} because now in {{/res/res_rtp_asterisk}} the call {{ast_rtp_codecs_get_framing(ast_rtp_instance_get_codecs(instance)}} returns 0 always.



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



More information about the asterisk-bugs mailing list