| Summary: | ASTERISK-22245: WebRTC fails to take calls from Chrome and Mozilla. | ||||
| Reporter: | Alex Zarubin (az_tth) | Labels: | |||
| Date Opened: | 2013-08-02 14:25:00 | Date Closed: | 2013-08-07 16:40:12 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_sip/WebSocket Core/RTP | ||
| Versions: | 11.4.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | CentOS 6.4 | Attachments: | |||
| Description: | 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. | ||||
| Comments: | By: Rusty Newton (rnewton) 2013-08-07 16:12:55.671-0500 https://bugzilla.mozilla.org/show_bug.cgi?id=797258 Issue in Mozilla tracker concerning this. Looks like they are currently sending SHA-256, but accept SHA-1 and SHA-256. By: Rusty Newton (rnewton) 2013-08-07 16:39:36.894-0500 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. By: Rusty Newton (rnewton) 2013-12-11 17:51:36.803-0600 @Alex there is a patch and revival of this issue in ASTERISK-22961 | ||||