You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/known-issues.md
+35-20Lines changed: 35 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,18 +11,19 @@ ms.topic: troubleshooting
11
11
ms.service: azure-communication-services
12
12
---
13
13
14
-
# Known issues: Azure Communication Services Calling SDKs
15
-
This article provides information about limitations and known issues related to the Azure Communication Services Calling SDKs.
14
+
# Known issues
15
+
This article provides information about limitations and known issues related to the Azure Communication Services Calling SDKs and Azure Communication Services Call Automation APIs
16
16
17
17
> [!IMPORTANT]
18
18
> There are multiple factors that can affect the quality of your calling experience. Refer to the **[network requirements](./voice-video-calling/network-requirements.md)** documentation to learn more about Communication Services network configuration and testing best practices.
19
19
20
+
## Azure Communication Services Calling SDKs
20
21
21
-
## JavaScript SDK
22
+
###JavaScript SDK
22
23
23
24
This section provides information about known issues associated with the Azure Communication Services JavaScript voice and video calling SDKs.
24
25
25
-
### Refreshing a page doesn't immediately remove the user from their call
26
+
####Refreshing a page doesn't immediately remove the user from their call
26
27
27
28
If a user is in a call and decides to refresh the page, the Communication Services media service won't remove this user immediately from the call. It will wait for the user to rejoin. The user will be removed from the call after the media service times out.
28
29
@@ -35,16 +36,16 @@ If the user rejoins with the same Communication Services user ID, they'll be rep
35
36
If the user was sending video before refreshing, the `videoStreams` collection will keep the previous stream information until the service times out and removes it. In this scenario, the application may decide to observe any new streams added to the collection and render one with the highest `id`.
36
37
37
38
38
-
### It's not possible to render multiple previews from multiple devices on web
39
+
####It's not possible to render multiple previews from multiple devices on web
39
40
This is a known limitation. For more information, see the [calling SDK overview](./voice-video-calling/calling-sdk-features.md).
40
41
41
-
### Enumerating devices isn't possible in Safari when the application runs on iOS or iPadOS
42
+
####Enumerating devices isn't possible in Safari when the application runs on iOS or iPadOS
42
43
43
44
Applications can't enumerate/select mic/speaker devices (like Bluetooth) on Safari iOS/iPad. This is a known operating system limitation.
44
45
45
46
If you're using Safari on macOS, your app won't be able to enumerate/select speakers through the Communication Services Device Manager. In this scenario, devices must be selected via the OS. If you use Chrome on macOS, the app can enumerate/select devices through the Communication Services Device Manager.
46
47
47
-
### Audio connectivity is lost when receiving SMS messages or calls during an ongoing VoIP call
48
+
####Audio connectivity is lost when receiving SMS messages or calls during an ongoing VoIP call
48
49
This problem may occur due to multiple reasons:
49
50
50
51
- Some mobile browsers don't maintain connectivity while in the background state. This can lead to a degraded call experience if the VoIP call was interrupted by an event that pushes your application into the background.
@@ -54,22 +55,22 @@ This problem may occur due to multiple reasons:
54
55
<br/>Browsers: Safari, Chrome
55
56
<br/>Operating System: iOS, Android
56
57
57
-
### Repeatedly switching video devices may cause video streaming to temporarily stop
58
+
####Repeatedly switching video devices may cause video streaming to temporarily stop
58
59
59
60
Switching between video devices may cause your video stream to pause while the stream is acquired from the selected device.
60
61
61
-
#### Possible causes
62
+
#####Possible causes
62
63
Switching between devices frequently can cause performance degradation. Developers are encouraged to stop one device stream before starting another.
63
64
64
-
### Bluetooth headset microphone is not detected therefore is not audible during the call on Safari on iOS
65
+
####Bluetooth headset microphone is not detected therefore is not audible during the call on Safari on iOS
65
66
Bluetooth headsets aren't supported by Safari on iOS. Your Bluetooth device won't be listed in available microphone options and other participants won't be able to hear you if you try using Bluetooth over Safari.
66
67
67
-
#### Possible causes
68
+
#####Possible causes
68
69
This is a known macOS/iOS/iPadOS operating system limitation.
69
70
70
71
With Safari on **macOS** and **iOS/iPadOS**, it is not possible to enumerating/selecting speaker devices through the Communication Services Device Manager since speakers enumeration/selection is not supported by Safari. In this scenario, your device selection should be updated via the operating system.
71
72
72
-
### Rotation of a device can create poor video quality
73
+
####Rotation of a device can create poor video quality
73
74
Users may experience degraded video quality when devices are rotated.
74
75
75
76
<br/>Devices affected: Google Pixel 5, Google Pixel 3a, Apple iPad 8, and Apple iPad X
@@ -78,7 +79,7 @@ Users may experience degraded video quality when devices are rotated.
78
79
<br/>Operating System: iOS, Android
79
80
80
81
81
-
### Camera switching makes the screen freeze
82
+
####Camera switching makes the screen freeze
82
83
When a Communication Services user joins a call using the JavaScript calling SDK and then hits the camera switch button, the UI may become unresponsive until the application is refreshed or browser is pushed to the background by user.
83
84
84
85
<br/>Devices affected: Google Pixel 4a
@@ -87,30 +88,30 @@ When a Communication Services user joins a call using the JavaScript calling SDK
87
88
<br/>Operating System: iOS, Android
88
89
89
90
90
-
#### Possible causes
91
+
#####Possible causes
91
92
Under investigation.
92
93
93
-
### If the video signal was stopped while the call is in "connecting" state, the video will not be sent after the call started
94
+
####If the video signal was stopped while the call is in "connecting" state, the video will not be sent after the call started
94
95
If users decide to quickly turn video on/off while call is in `Connecting` state - this may lead to problem with stream acquired for the call. We encourage developers to build their apps in a way that doesn't require video to be turned on/off while call is in `Connecting` state. This issue may cause degraded video performance in the following scenarios:
95
96
96
97
- If the user starts with audio and then start and stop video while the call is in `Connecting` state.
97
98
- If the user starts with audio and then start and stop video while the call is in `Lobby` state.
98
99
99
-
#### Possible causes
100
+
#####Possible causes
100
101
Under investigation.
101
102
102
-
### Enumerating/accessing devices for Safari on MacOS and iOS
103
+
####Enumerating/accessing devices for Safari on MacOS and iOS
103
104
If access to devices are granted, after some time, device permissions are reset. Safari on MacOS and on iOS does not keep permissions for very long time unless there is a stream acquired. The simplest way to work around this is to call DeviceManager.askDevicePermission() API before calling the device manager's device enumeration APIs (DeviceManager.getCameras(), DeviceManager.getSpeakers(), and DeviceManager.getMicrophones()). If the permissions are there, then user will not see anything, if not, it will re-prompt.
104
105
105
106
<br/>Devices affected: iPhone
106
107
<br/>Client library: Calling (JavaScript)
107
108
<br/>Browsers: Safari
108
109
<br/>Operating System: iOS
109
110
110
-
### Sometimes it takes a long time to render remote participant videos
111
+
####Sometimes it takes a long time to render remote participant videos
111
112
During an ongoing group call, _User A_ sends video and then _User B_ joins the call. Sometimes, User B doesn't see video from User A, or User A's video begins rendering after a long delay. This issue could be caused by a network environment that requires further configuration. Refer to the [network requirements](./voice-video-calling/network-requirements.md) documentation for network configuration guidance.
112
113
113
-
### Using 3rd party libraries to access GUM during the call may result in audio loss
114
+
####Using 3rd party libraries to access GUM during the call may result in audio loss
114
115
Using getUserMedia separately inside the application will result in losing audio stream since a third party library takes over device access from ACS library.
115
116
Developers are encouraged to do the following:
116
117
1. Don't use 3rd party libraries that are using internally GetUserMedia API during the call.
@@ -119,5 +120,19 @@ Developers are encouraged to do the following:
119
120
<br/>Browsers: Safari
120
121
<br/>Operating System: iOS
121
122
122
-
#### Possible causes
123
+
#####Possible causes
123
124
In some browsers (Safari for example), acquiring your own stream from the same device will have a side-effect of running into race conditions. Acquiring streams from other devices may lead the user into insufficient USB/IO bandwidth, and sourceUnavailableError rate will skyrocket.
125
+
126
+
127
+
## Azure Communication Services Call Automation APIs
128
+
129
+
Following are the known issues in the Azure Communication Services Call Automation APIs
130
+
131
+
- The only authentication supported at this time for server applications is using a connection string.
132
+
133
+
- Calls should be make only between entities of the same Azure Communication Service resource. Cross resource communication is blocked.
134
+
135
+
- Calls between Teams' tenant users and Azure Communication Service user or server application entities are not allowed.
136
+
137
+
- If an application dials out to two or more PSTN identities and then quits the call, the call between the other PSTN entities would be dropped.
Copy file name to clipboardExpand all lines: articles/spring-cloud/access-app-virtual-network.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,9 @@ The following procedure creates a private DNS zone for an application in the pri
25
25
26
26
3. Fill out the form on the **Create Private DNS zone** page. Enter **<span>private.azuremicroservices.io</span>** as the **Name** of the zone.
27
27
28
+
>[!NOTE]
29
+
> If you are using Azure China, please replace `private.azuremicroservices.io` with `private.microservices.azure.cn` for the whole documentation, [learn more](/azure/china/resources-developer-guide#check-endpoints-in-azure).
30
+
28
31
4. Select **Review + Create**.
29
32
30
33
5. Select **Create**.
@@ -119,4 +122,4 @@ After the assignment, you can access the private FQDN of your application in pri
119
122
## See also
120
123
121
124
-[Troubleshooting Azure Spring Cloud in VNET](./troubleshooting-vnet.md)
122
-
-[Customer Responsibilities for Running Azure Spring Cloud in VNET](./vnet-customer-responsibilities.md)
125
+
-[Customer Responsibilities for Running Azure Spring Cloud in VNET](./vnet-customer-responsibilities.md)
Copy file name to clipboardExpand all lines: articles/spring-cloud/how-to-deploy-in-azure-virtual-network.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,7 +164,7 @@ This table shows the maximum number of app instances Azure Spring Cloud supports
164
164
| /25 | 128 | 120 | <p> App with 1 core: 500<br> App with 2 cores: 500<br> App with 3 cores: 480<br> App with 4 cores: 360</p> |
165
165
| /24 | 256 | 248 | <p> App with 1 core: 500<br/> App with 2 cores: 500<br/> App with 3 cores: 500<br/> App with 4 cores: 500</p> |
166
166
167
-
For subnets, five IP addresses are reserved by Azure, and at least three IP addresses are required by Azure Spring Cloud. At least nine IP addresses are required, so /29 and /30 are nonoperational.
167
+
For subnets, five IP addresses are reserved by Azure, and at least three IP addresses are required by Azure Spring Cloud. At least eight IP addresses are required, so /29 and /30 are nonoperational.
168
168
169
169
For a service runtime subnet, the minimum size is /28. This size has no bearing on the number of app instances.
Copy file name to clipboardExpand all lines: articles/spring-cloud/vnet-customer-responsibilities.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ By default, Azure Spring Cloud has unrestricted outbound (egress) internet acces
21
21
The following is a list of resource requirements for Azure Spring Cloud services. As a general requirement you should not modify resource groups created by Azure Spring Cloud and the underlying network resources.
22
22
- Do not modify resource groups created and owned by Azure Spring Cloud.
23
23
- By default, these resource groups are named as ap-svc-rt_[SERVICE-INSTANCE-NAME]_[REGION]* and ap_[SERVICE-INSTANCE-NAME]_[REGION]*.
24
+
- Do not block Azure Spring Cloud from updating reseources in these resource groups.
24
25
- Do not modify subnets used by Azure Spring Cloud.
25
26
- Do not create more than one Azure Spring Cloud service instance in the same subnet.
26
27
- When using a firewall to control traffic, *do not* block the following egress traffic to Azure Spring Cloud components that operate, maintain, and support the service instance.
Copy file name to clipboardExpand all lines: articles/synapse-analytics/security/workspace-data-exfiltration-protection.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,9 +29,7 @@ Let us use an example to illustrate data exfiltration protection for Synapse wor
29
29
30
30
>[!IMPORTANT]
31
31
>
32
-
> - Resources in tenants other than the workspace's tenant must not have blocking firewall rules in place for the SQL pools to connect to them. Resources within the workspace’s managed virtual network, such as Spark clusters, can connect over managed private links to firewall-protected resources.
33
-
>
34
-
> - Metastore is disabled in Synapse workspaces that have Managed Virtual Network with data exfiltration protection enabled. You can't use Spark SQL in these workspaces.
32
+
> Resources in tenants other than the workspace's tenant must not have blocking firewall rules in place for the SQL pools to connect to them. Resources within the workspace’s managed virtual network, such as Spark clusters, can connect over managed private links to firewall-protected resources.
0 commit comments