mikesimb / sipml5

Automatically exported from code.google.com/p/sipml5
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

setRemoteDescription Error #158

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
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.Its a chrome browser(UE1) to browser(UE2) call (Version 33.0.1750.117 m). For 
signalling I am using SIPML (sip stack) 
2.First session is established ( audio/video connection is established fine).
3.Now UE1 puts call on Hold . During hold UE2 receives offer (INVITE) from UE1, 
Here UE2 is trying to setRemoteDescription ,But its geeting error that is 
described below.

What is the expected output? What do you see instead?
Expected Output : onSetRemoteDescriptionSuccess
Getting Output  : onSetRemoteDescriptionError 
                 Failed to set remote offer sdp: Session error code:                  
                -ERROR_CONTENT. Session error description: Cryptos must be 
                 -empty when DTLS is active.. 

What version of the product are you using? On what operating system?

Google chrome Version 35.0.1859.3 canary SyzyASan & Version 33.0.1750.117 m, OS 
: Windows 7

Please provide any additional information below.

I think this issue is all due to some  fixes in google chrome browser because I 
had tried exactly same implementation on chrome version 30.0.1599.69 & 
31.0.1650.4, there I did not get any error but some other issues were there 
which fixed in new versions. Thats why I am not able to proceed further for 
Resume.

I had also tried with disabling the dtls & crypto with different scenarios but 
on disabling dtls same problem still comes but on disabling crypto browser is 
crashed down. I think due some fixes in chrome we cann't disable any one of 
them otherwise we will get one of these problems. 

I have ateeched chrome://webrtc-internals/ logs also.

Original issue reported on code.google.com by chaudhar...@gmail.com on 27 Feb 2014 at 6:55

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by boss...@yahoo.fr on 18 Apr 2014 at 8:25