SetRemoteDescription failed.

[Ramasundar Kandasamy]

Hi

When i try to set the remote SDP i get the "SetRemoteDescription failed" error. The call is audio only call.

I am using custom built Chromium (24.0.1297.0 (162070)).

Earlier in this discussion i got a hint that "a=fmtp:126 0-15" could cause problem. 

So i modified the original sdp to remove the following lines:

 "a=fmtp:126 0-15"

"a=rtpmap:126 telephone-event/8000"

and modified the 

"RTP/AVPF 8 126" line to "RTP/AVPF 8".

but STILL "SetRemoteDescription failed" is being popped out.

Any hints guys?

Thanks and best regards,

Ram

Here are the original and modified sdps.

_*_*_*_*_*_* original

v=0

o=mrelay 804592592 2 IN IP4 192.168.1.7

s=

t=0 0

a=group:BUNDLE audio video

m=audio 9132 RTP/AVPF 8 126

c=IN IP4 192.168.1.7

a=candidate:1 1 UDP 1 192.168.1.7 9132 typ host

a=candidate:1 2 UDP 1 192.168.1.7 9133 typ host

a=fmtp:126 0-15

a=ice-pwd:mysecret

a=ice-ufrag:root

a=mid:audio

a=rtcp:9133 IN IP4 192.168.1.7

a=rtcp-mux

a=rtpmap:126 telephone-event/8000

a=rtpmap:8 PCMA/8000

a=ssrc:3306320348 cname:JCLKO7XsgTvj5NQz

a=ssrc:3306320348 label:vyxYLwL8cH5I61LJRk6IewMw2r6KpLWL6yBZ00

a=ssrc:3306320348 mslabel:vyxYLwL8cH5I61LJRk6IewMw2r6KpLWL6yBZ

_*_*_*_*_*_* modified 

v=0

o=mrelay 804592592 2 IN IP4 192.168.1.7

s=

t=0 0

a=group:BUNDLE audio video

m=audio 9132 RTP/AVPF 8 

c=IN IP4 192.168.1.7

a=candidate:1 1 UDP 1 192.168.1.7 9132 typ host

a=candidate:1 2 UDP 1 192.168.1.7 9133 typ host

a=ice-pwd:mysecret

a=ice-ufrag:root

a=mid:audio

a=rtcp:9133 IN IP4 192.168.1.7

a=rtcp-mux

a=rtpmap:8 PCMA/8000

a=ssrc:3306320348 cname:JCLKO7XsgTvj5NQz

a=ssrc:3306320348 label:vyxYLwL8cH5I61LJRk6IewMw2r6KpLWL6yBZ00

a=ssrc:3306320348 mslabel:vyxYLwL8cH5I61LJRk6IewMw2r6KpLWL6yBZ

[Ramasundar Kandasamy]

The chromium log says : [7496:2084:0501/214709:VERBOSE1:channel.cc(792)] Failure in SetRemoteContent with  action 2

[Mamadou]

no crypto keys?
no secure media profile (RTP/SAVPF)?

On May 1, 10:17 pm, Ramasundar Kandasamy <kramasun...@yahoo.com>
wrote:

[Vikas]

Hi,

There is no m-line for video as well, probably try removing video from
'a=group:BUNDLE audio video' line. I would suggest you turn on logging
to find the failure. You can generate more logs with the "--enable-
logging --v=1 --vmodule=*libjingle/source/talk/*=3".

/Vikas

[Ramasundar Kandasamy]

Hi,

1. Now i am running chrome with: chrome.exe --enable-logging --v=1 --vmodule=*libjingle/source/talk/*=3

But couldn't see more info than using just --enable-logging --v=1.

2. I removed the "video" from "a=group:BUNDLE audio video" line. Still the same issue. --> [7100:5648:0502/091052:VERBOSE1:channel.cc(792)] Failure in SetRemoteContent with  action 2

Here is the original and modified SDP: https://dl.dropboxusercontent.com/u/2736804/tmp/ErrorCallBack.txt

FUNNY ENOUGH, when i did a small mistake by incompletely deleting a line (line 30 - an empty line), i got the success callback. https://dl.dropboxusercontent.com/u/2736804/tmp/SuccessCallBack.txt

I dont have the media plane yet, since i am using SIPp to test the signalling path first.

This is the piece of relevant code 

_pc.setRemoteDescription(new RTCSessionDescription(remoteDest), 

  function(){

                                                            console.log("remoteSuccess()");

                                                          },

                                          function(err){

                                                            console.log("Err setRemoteDescription " + err);

                                                          }

                                            );

[Ramasundar Kandasamy]

No SRTP yet.

[Mamadou]

SRTP is mandatory and you'll not go far without it.

On May 2, 9:49 am, Ramasundar Kandasamy <kramasun...@yahoo.com> wrote:
> No SRTP yet.

[Vikas]

I tested with your sdp on canary i saw SetRemoteDescription error,
"SetRemoteDescription failed: Called with a SDP without crypto
enabled".

/Vikas

[Ramasundar Kandasamy]

The voice call is working now, even though the SDP error is still thrown. Even with the original (refer my first question in this post) SDP the call is working, despite the fact that the error is still there.

@Vikas: "SetRemoteDescription failed: Called with a SDP without crypto enabled" --> That is because you are using Canary (ie. latest chromium build). My chromium is a older version and it doesn't support encryption.

Thanks

Ram

[Justin Uberti]

Chrome has required encryption since the very first builds with WebRTC.

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ramasundar Kandasamy]

Ok. Then it was my misunderstanding. I will come back with some more info.

[Ramasundar Kandasamy]

We have disabled that for our purpose.