[asterisk-bugs] [JIRA] (ASTERISK-29183) Audio/Video Codecs: Format parameters get lost.

[Alexander Traud (JIRA)]

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

Alexander Traud updated ASTERISK-29183:
---------------------------------------

    Description: 
In June, a discussion started about a new, still upcoming Advanced Codec Negotiation (ACN; [mailing list|http://lists.digium.com/pipermail/asterisk-dev/2020-June/thread.html], [blog post|https://www.asterisk.org/asterisk-acn-advanced-codec-negotiation/], [wiki entry|https://wiki.asterisk.org/wiki/display/AST/PJSIP+Advanced+Codec+Negotiation]). Because I am leaving the Asterisk platform, just a note that Asterisk has not only problems with format negotiation but also preserving [SDP|https://tools.ietf.org/html/rfc4566] format parameters: {{a=fmtp …}}. Missing parameters heavily affect the overall negotiation, for example to get things working like in ASTERISK-29182 would not be possible at all.

Actually, I hacked format-parameter preserving into Asterisk years ago to get my AMR modules working. Although those hacks went into Asterisk, still scenarios exist which still loose the format parameters ([example|https://github.com/traud/asterisk-amr/issues/8#issuecomment-260714794]). Long story short: As of today, Asterisk was not designed to preserve format parameters in any bridge.

  was:
In June, a discussion started about a new, still upcoming Advanced Codec Negotiation (ACN; [mailing list|http://lists.digium.com/pipermail/asterisk-dev/2020-June/thread.html], [blog post|https://www.asterisk.org/asterisk-acn-advanced-codec-negotiation/], [wiki entry|https://wiki.asterisk.org/wiki/display/AST/PJSIP+Advanced+Codec+Negotiation]). Because I am leaving the Asterisk platform, just a note that Asterisk has not only problems with format negotiation but also preserving [SDP|https://tools.ietf.org/html/rfc4566] format parameters: {{a=fmtp …}}. Missing parameters heavily affect the overall negotiation, for example to get things working like in ASTERISK-29182 would not be possible at all.

Actually, I hacked format-parameter preserving into Asterisk years ago to get my AMR modules working. Although those hacks went into Asterisk, still scenarios exist which still loose the format parameters ([example|https://github.com/traud/asterisk-amr/issues/8#issuecomment-260714794]). Long story short: As of today, Asterisk was not designed to preserve format attributes in any bridge.


> Audio/Video Codecs: Format parameters get lost.
> -----------------------------------------------
>
>                 Key: ASTERISK-29183
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29183
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.15.0, 18.1.0
>            Reporter: Alexander Traud
>
> In June, a discussion started about a new, still upcoming Advanced Codec Negotiation (ACN; [mailing list|http://lists.digium.com/pipermail/asterisk-dev/2020-June/thread.html], [blog post|https://www.asterisk.org/asterisk-acn-advanced-codec-negotiation/], [wiki entry|https://wiki.asterisk.org/wiki/display/AST/PJSIP+Advanced+Codec+Negotiation]). Because I am leaving the Asterisk platform, just a note that Asterisk has not only problems with format negotiation but also preserving [SDP|https://tools.ietf.org/html/rfc4566] format parameters: {{a=fmtp …}}. Missing parameters heavily affect the overall negotiation, for example to get things working like in ASTERISK-29182 would not be possible at all.
> Actually, I hacked format-parameter preserving into Asterisk years ago to get my AMR modules working. Although those hacks went into Asterisk, still scenarios exist which still loose the format parameters ([example|https://github.com/traud/asterisk-amr/issues/8#issuecomment-260714794]). Long story short: As of today, Asterisk was not designed to preserve format parameters in any bridge.



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