[asterisk-bugs] [JIRA] (ASTERISK-27675) Feature Request: Single Codec in Response

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Wed Feb 14 10:57:13 CST 2018


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

Richard Mudgett commented on ASTERISK-27675:
--------------------------------------------

Features requests without patches are not accepted through the issue tracker. Features requests are openly discussed on the mailing lists, forums, and IRC [1]. Please see the Asterisk Issue Guidelines [2] for more information on feature request and patch submission.

[1] http://asterisk.org/community/discuss
[2] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

The asymmetric_rtp_codec option was added to do just this in v13.17.0.

> Feature Request: Single Codec in Response
> -----------------------------------------
>
>                 Key: ASTERISK-27675
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27675
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.15.0
>         Environment: Debian 9
>            Reporter: Carsten Bock
>            Severity: Minor
>              Labels: pjsip
>
> Hi,
> as you may know, we love IMS. And we love using Asterisk (PJSIP) with IMS, as it makes our life easier... :-) Chan_pjsip does a great job!
> However, we have a compatibility issue:
> In our Lab-Setup, we use Asterisk as a B2BUA between VoLTE handsets and the "rest of the world". The VoLTE handsets usually speak AMR-Codecs, while in the rest of the world we use G711/G722. So Asterisk needs to do Transcoding, which it does great.
> In our setup we have:
> disallow=all
> allow=g722
> allow=amr
> allow=amrwb
> allow=ulaw
> allow=alaw
> Call comes in (with AMR / AMRWB) and goes out with G722, AMR, AMRWB, G711. Reply comes in as G722, and reply goes out with AMR and AMRWB. While I believe it is technically correct to reply with both codecs, it confuses our Lab-Samsung Handsets, so we simply get "no audio" instead of anything else.
> If I comment either AMR or AMRWB, the reply contains only one codec and the phone is happy.
> It would be desirable, to have an option to always only have one codec in the reply instead of all compatible ones.
> Of course we've raised the issue with Samsung, but it takes them ages to fix this.
> Thanks,
> Carsten



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



More information about the asterisk-bugs mailing list