Jump to content

Search the Community

Showing results for tags 'rest api'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Ant Media Connect
    • Dashboard and features
    • Installation & Configuration
    • SDK integration & APIs
    • News & announcements
    • Licensing
    • Hire a consultant
    • Streaming general discussion
    • Applications & plugins

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 2 results

  1. Hello, everybody. The behavior of Ant Media when I am trying to create conference room having the same roomId multiple times via REST API is not entirely clear for me. Steps to reproduce: 1. Open two tabs of the browser with conference demo https://localhost:5443/LiveApp/conference.html 2. Create conference room via REST API: curl -X 'POST' 'https://localhost:5443/LiveApp/rest/v2/broadcasts/conference-rooms' -H 'accept: application/json' -H 'Content-Type: application/json' -d '{ "roomId": "test_room" }' 3. Join the room "test_room" in browser tab #1 4. Repeat create request: curl -X 'POST' 'https://localhost:5443/LiveApp/rest/v2/broadcasts/conference-rooms' -H 'accept: application/json' -H 'Content-Type: application/json' -d '{ "roomId": "test_room" }' 5. Join the room "test_room" in the browser tab #2 What I expect to see: I see two videos (local and remote) in browser tab #1 and two videos (local and remote) in browser tab #2 What I actually see: I see two videos (local and remote) in browser tab #1 and only one video (local) in browser tab #2. Is this behavior the expected one?
  2. Hello, everyone. My use case is the following: I want to specify some meta data for the stream when I create it on the server side via REST API, so I can use it on the client side later. My steps are: 1. Create stream on the server side of my app via REST API by calling POST /v2/broadcasts/create with body {"metaData":"somestreammetadata"}.Then pass streamId of created stream to the client side. 2. On the client side use streamId obtained on previous step to join the conference room by calling WebRTCAdaptor::joinRoom(roomName, streamId). Then start publishing by calling WebRTCAdaptor::publish(streamId). What I expect: When other participants of the conference receive stream info via "roomInformation" event, I see "metaData" that was set on stream creation. What I actually see: When other participants of the conference receive stream info via "roomInformation" event, I see that "metaData" value is null. On the other hand, when I call REST API method GET /v2/broadcasts/{id}, I see correct value in "metaData" field of the stream. What am I doing wrong?
×
×
  • Create New...