[asterisk-bugs] [JIRA] (ASTERISK-26050) Negotiation Problem

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26050:
------------------------------------------

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

> Negotiation Problem
> -------------------
>
>                 Key: ASTERISK-26050
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26050
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.9.0
>         Environment: WebRTC
> Ubuntu 16.04
>            Reporter: scgm11
>
> Im having an issue that I think is on sdp negotiation. using webrtc
> basically is one way audio, but this is not nat related, the problem is when I have 2 peers with audio and video capability, when both have this capability the part that answer the call answers with video even when on the initial INVITE theres is no video, but I think is using the capabilities of the peer instead of the offer. as the ice negotiation use different ports for audio and video seems that if I dont answer with video enable I dont have audio.
> I attach a sip log from asterisk.
> Let me know if Im not clear enough.



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