[asterisk-bugs] [JIRA] (ASTERISK-22245) WebRTC fails to take calls from Chrome and Mozilla.
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Wed Aug 7 16:41:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208574#comment-208574 ]
Rusty Newton commented on ASTERISK-22245:
-----------------------------------------
This isn't really a bug, it just isn't supported yet.
Until we have code to review, or know that someone is working on it, we won't track it here in the issue tracker. Creating an issue doesn't make the code appear. https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
Feel free to discuss further on the dev list if you have additional comments or questions.
This issue can be re-opened if and when someone starts working on this or has code for it.
> WebRTC fails to take calls from Chrome and Mozilla.
> ---------------------------------------------------
>
> Key: ASTERISK-22245
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22245
> Project: Asterisk
> Issue Type: New Feature
> Security Level: None
> Components: Channels/chan_sip/WebSocket, Core/RTP
> Affects Versions: 11.4.0
> Environment: CentOS 6.4
> Reporter: Alex Zarubin
>
> WebRTC implementations in Chrome and FF nightly send fingerprint with hash type sha-256. Asterisk supports just sha-1 and calls fail. In
> http://lists.digium.com/pipermail/asterisk-dev/2013-January/058221.html
> it is said there is no issue that would trigger sha-256 addition to asterisk, so I'm trying to create one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list