Re: [asterisk-dev] [Code Review] 3454: When Asterisk initiates an ICE-based session, then it must send it's STUN check messages using role "ICE-CONTROLLING". Currently it uses "ICE-CONTROLLED". Though the role conflict get's resolved correctly, it does not conform to http://tools.ietf.org/html/rfc5245#section-5.2

Thu, 26 Jun 2014 11:44:58 -0700 

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3454/
-----------------------------------------------------------

(Updated June 26, 2014, 1:44 p.m.)


Status
------

This change has been discarded.


Review request for Asterisk Developers.


Bugs: ASTERISK-23026
    https://issues.asterisk.org/jira/browse/ASTERISK-23026


Repository: Asterisk


Description
-------

The following patch must be applied to res_rtp_asterisk to make outgoing calls 
to WebRTC capable browsers working. This is necessary due to the following 
issue in role negotiation:
https://code.google.com/p/webrtc/issues/detail?id=2717&can=4&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Status%20Owner%20Summary


Diffs
-----

  http://svn.asterisk.org/svn/asterisk/trunk/res/res_rtp_asterisk.c 412438 

Diff: https://reviewboard.asterisk.org/r/3454/diff/


Testing
-------


Thanks,

Marko Seidenglanz


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to