You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (Wireshark) or Javascript console log
if you want quick response
What steps will reproduce the problem?
1. Install asterisk 13 using the following guide:
https://kunjans.wordpress.com/2015/01/09/web-sip-client-sipml5-with-asterisk-13-
on-centos-6-6/
2. Use PJSIP as the sip driver, and allow alaw,ulaw,vp8
3. Login with 2 endpoints on SipML5 demo
What is the expected output?
When the call is answered, there is audio and Video flowing.
What do you see instead?
On Chrome I get call terminated when anwering it, and i see this errors in the
Asterisk logs:
WARNING[1844][C-00000010]: res_srtp.c:407 ast_srtp_unprotect: SRTP unprotect
failed with: authentication failure 10
WARNING[1844][C-00000010]: res_srtp.c:407 ast_srtp_unprotect: SRTP unprotect
failed with: authentication failure 110
On FireFox, only audio is working, but the call works without errors.
When I call from a zoiper client, to a SipMl5 endpoint, I see video from SipML5
on the zoiper client. But not the other way around.
What version of the product are you using?
I use the demo of SipML5 r230
On what operating system?
Windows 8.1 64 bit
On what browser:
Chrome 41.0.2272.101 m
FireFox 36.0.4
On what native client:
Zoiper 3.6.25251
Please provide any additional information below.
I have used all kinds of patches, like the opus vp8 patch. But this didnt work
either. It looks like the video stream doesn't add into the html of SipML5.
With working accounts from OnSIP it doesnt work either, only audio. But when I
use JSSIP with OnSIP I have audio and video. That gets me thinking that de
video of SipML5 is broken?
Original issue reported on code.google.com by [email protected] on 2 Apr 2015 at 9:11
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 2 Apr 2015 at 9:11The text was updated successfully, but these errors were encountered: