-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akucer. |
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. |
any updates on this? I am searching for something similar at the moment |
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
The text was updated successfully, but these errors were encountered: