Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Communication Services - Call Automation] Raw media access on the server (Rooms Calls) #30647

Open
1 of 6 tasks
yxor opened this issue Aug 5, 2024 · 3 comments
Open
1 of 6 tasks
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Communication - Calling Server customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@yxor
Copy link

yxor commented Aug 5, 2024

  • Package Name: @azure/communication-calling
  • Package Version: any
  • Operating system: Windows
  • nodejs
    • version: latest
  • browser
    • name/version:
  • typescript
    • version:
  • Is the bug related to documentation in

Describe the bug
The raw media access documentation here says that it's possible to access raw call media (audio data in my case) on the server side, but I can't find any code samples or any documentation on this

To Reproduce
Cannot access raw call media on the server side

Expected behavior
I need the ability to access raw call media on the server side

Screenshots
N/A

Additional context
I need to do some real-time processing on the audio data of the call

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Media Services needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 5, 2024
Copy link

github-actions bot commented Aug 5, 2024

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akucer.

@github-actions github-actions bot added the Service Attention Workflow: This issue is responsible by Azure service team. label Aug 5, 2024
@yxor
Copy link
Author

yxor commented Aug 12, 2024

Update: I reviewed the recently published documentation and set up a sample using the Call Automation library to initiate media streaming by passing a URL to a WebSocket server that I configured.

Please note that the call I am trying to stream media from is a Room's call. Here is how I initiate the media streaming:

		const mediaStreamingOptions: MediaStreamingOptions = {
			transportUrl: `${process.env.PUBLIC_CALLING_SERVER_URL}`,
			transportType: "websocket",
			contentType: "audio",
			audioChannelType: "mixed",
			startMediaStreaming: true,
		};
		const response = await callAutomationClient.connectCall(
			{
				id: room.id,
				kind: "roomCallLocator",
			},
			callbackUrl,
			{
				mediaStreamingOptions,
			},
		);

This is the error I received:

 {
  "name": "RestError",
  "code": "8520",
  "statusCode": 405,
  "request": {
    "url": "https://xxxxxxx.unitedstates.communication.azure.com/calling/callConnect
ions/19003b80-646c-4e42-99f2-6b6b3c4b16e7:startMediaStreaming?api-version=2024-06-15
-preview",
    "headers": {
      "content-type": "application/json",
      "accept": "application/json",
      "accept-encoding": "gzip,deflate",
      "user-agent": "azsdk-js-communication-call-automation/1.3.0-beta.1 core-rest-p
ipeline/1.15.2 Node/20.10.0 OS/(x64-Windows_NT-10.0.19045)",
      "x-ms-client-request-id": "0a490dd6-32fd-4e37-9636-c4bd41c7f431",
      "host": "REDACTED",
      "x-ms-date": "REDACTED",
      "x-ms-content-sha256": "REDACTED",
      "authorization": "REDACTED",
      "content-length": "49"
    },
    "method": "POST",
    "timeout": 0,
    "disableKeepAlive": false,
    "streamResponseStatusCodes": {},
    "withCredentials": false,
    "requestId": "0a490dd6-32fd-4e37-9636-c4bd41c7f431",
    "allowInsecureConnection": false,
    "enableBrowserStreams": false
  },
  "details": {
    "error": {
      "code": "8520",
      "message": "MediaStreaming is not supported for connection created with Connec
t interface."
    }
  },
  "message": "MediaStreaming is not supported for connection created with Connect in
terface."
}

Is there a workaround for this? My end goal is to achieve media streaming on the server side for Room calls. Your urgent response would be greatly appreciated.

@yxor yxor changed the title [Communication] Raw media access on the server [Communication Services - Call Automation] Raw media access on the server (Rooms Calls) Aug 12, 2024
@realjesset
Copy link

any updates on this? I am searching for something similar at the moment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication - Calling Server customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

5 participants