[asterisk-bugs] [JIRA] (ASTERISK-27650) Errors Using Webrtc

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Feb 1 06:07:13 CST 2018


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

Asterisk Team commented on ASTERISK-27650:
------------------------------------------

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

> Errors Using Webrtc
> -------------------
>
>                 Key: ASTERISK-27650
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27650
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_rtp
>    Affects Versions: 15.2.0
>         Environment: WebRTC,Asterisk,SIPml5,Fedora23, Hardware: 8GB RAM, Xeno quad core cpu
>            Reporter: Mahesh Katta
>            Severity: Critical
>              Labels: webrtc
>
> [2018-02-01 11:56:21] WARNING[14584]: db.c:348 ast_db_put: Couldn't execute statment: SQL logic error or missing database
> [2018-02-01 11:56:25] ERROR[4087]: chan_sip.c:4271 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
> Above mentioned errors keep getting in Asterisk CLI. 
> Using web browser chrome64 version via webRTC, callee unable to get caller voice but caller is getting callee audio. What could be the problem, above mentioned errors are creating this issue or something else.



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



More information about the asterisk-bugs mailing list