[asterisk-bugs] [JIRA] (ASTERISK-29936) translate: unable to build translation path

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29936:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> translate: unable to build translation path
> -------------------------------------------
>
>                 Key: ASTERISK-29936
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29936
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge, Applications/app_originate, Channels/chan_sip/Video
>    Affects Versions: 18.9.0
>            Reporter: N A
>         Attachments: translatebug.txt
>
>
> When two peers through a ConfBridge and Originate with the h264 codec try to bridge together, the ConfBridge crashes because it's unable to build a translation path. Error is starting codec invalid.
> Before confbridge, the interesting bit is that the write format and read format before are h264, but after the write format is slin/ulaw and the read format is h264. Not sure if that means anything.
> Yes, I know I'm using chan_sip for this, but chan_pjsip crashes if I try to set up a video call so that doesn't really pan out.



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