Skip to content
This repository was archived by the owner on May 6, 2024. It is now read-only.
This repository was archived by the owner on May 6, 2024. It is now read-only.

handling rejected m-lines #42

Description

@fippo

rejected m-lines are currently not handled properly (and it's not completly clear what the spec on this is). See http://www.ietf.org/mail-archive/web/stox/current/msg00318.html

An easy way to do this would be to translate a port 0 to a content without a transport element -- which might fit chromes behaviour of not adding ice candidates for rejected m-lines quite well.

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions