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
Our applications can now directly call individual Microsoft Teams users. Those Teams users can be using Microsoft Teams or an authenticated Azure Communication Services Calling SDK endpoint. This feature makes Teams interoperability more complete. You can build custom apps connecting people to:
23
+
- Individual Teams users
24
+
- Teams call queues and Auto Attendant
25
+
- Teams meetings
26
+
27
+
You can use these features in business-2-consumer contact center and meeting applications to keep external customers in highly tailored websites and app experiences. You can also use this feature to keep all employee and agent communication activity in a single hub: Teams.
28
+
29
+
For more information, see [Capabilities for Microsoft Teams users in Azure Communication Services calls](./concepts/interop/guest/calling-capabilities.md).
30
+
31
+
### SMS support for 10 digit long code
32
+
33
+
Ten digit long code (10DLC) for SMS is now in public preview. Support for 10DLC enables enterprises with a trusted and scalable messaging solution to connect with their customers efficiently and compliantly.
34
+
35
+
The 10DLC SMS dedicated messaging channel enables businesses to send messages using local phone numbers. 10DLC offers a unique, registered phone number for your business, enhancing trust and ensuring compliance with carrier regulations. Perfect for transactional alerts, promotional messages, and customer service, 10DLC ensures higher message deliverability while adhering to industry standards.
36
+
37
+
#### Benefits of Using 10DLC SMS
38
+
39
+
-**Improved Deliverability**
40
+
41
+
A 10-digit number ensures higher message deliverability compared to traditional long codes, making it an effective way to ensure your messages reach your customers.
42
+
43
+
-**Local Presence**
44
+
45
+
Using a local 10-digit number provides a more personal and trusted connection with your customers, increasing engagement and response rates.
46
+
47
+
-**Cost-effective**
48
+
49
+
Using a 10-digit number offers a more affordable option compared to short codes, providing businesses with an efficient and cost-effective way to send high-volume messages.
50
+
51
+
-**Versatility**
52
+
53
+
Perfect for various use cases, including transactional messages, customer support, promotions, and marketing campaigns.
54
+
55
+
For more information, see:
56
+
-[SMS Concepts](./concepts/sms/concepts.md)
57
+
-[Apply for 10DLC numbers](./quickstarts/sms/apply-for-ten-digit-long-code.md)
58
+
-[SMS FAQ](./concepts/sms/sms-faq.md)
59
+
60
+
## November 2024
61
+
62
+
### Call Automation troubleshooting improvements
63
+
64
+
We improved notifications to help developers troubleshoot Call Automation. Now, you receive notifications if the CreateCall or Answer APIs fail asynchronously through the new `CreateCallFailed` and `AnswerFailed` events. Along with these events, we provide error codes for various leave and call end scenarios, helping you make informed decisions about what to do next.
65
+
66
+
We also revamped the error code documentation to offer better guidance for handling issues independently. In addition, you can now view Call Automation callback events in Azure metrics.
67
+
68
+
call-automation-view-callback-events.png
69
+
70
+
For more information, see:
71
+
72
+
-[Troubleshooting guide for Call Automation SDK error codes](./resources/troubleshooting/voice-video-calling/troubleshooting-codes.md#call-automation-sdk-error-codes).
73
+
Our docs on how to view Azure Communication Services Callback events via Azure Metrics.
74
+
75
+
## October 2024
76
+
77
+
### Enable advanced noise suppression on web desktop browsers
78
+
79
+
The WebJS Calling SDK now includes background audio noise suppression. This feature improves call quality by reducing background noise and ensuring that the speaker's voice remains clear and understandable.
80
+
81
+
This technology is useful in environments with high levels of ambient noise, such as open offices or public spaces, where extra sounds can interfere with communication. By filtering out ambient noise, noise suppression helps participants concentrate on the conversation without interruptions.
82
+
83
+
Our advanced noise suppression models can manage distracting noises, such as a dog barking and background conversations.
84
+
85
+
For more information, see [Add audio quality enhancements to your audio calling experience](./tutorials/audio-quality-enhancements/add-noise-supression.md).
86
+
87
+
### Extended caller information
88
+
89
+
Incoming call notifications now include the caller line ID (CLID) and calling party name (CNAM). This information can be used to identify the phone number of an incoming call.
90
+
91
+
```javascript
92
+
constincomingCallHandler=async (args: { incomingCall: IncomingCall }) => { constincomingCall=args.incomingCall; // Get information about caller console.log(callerInfo.displayName); console.log(callerInfo.identifier); };
93
+
```
94
+
95
+
For more information, see [CallerInfo interface](/azure/communication-calling/callerinfo), [Manage calls > Receive an incoming call](./how-tos/calling-sdk/manage-calls.md#receive-an-incoming-call), and [Manage calls > Check call properties](./how-tos/calling-sdk/manage-calls.md#check-call-properties).
96
+
97
+
### Remote Mute VoIP meeting participants
98
+
99
+
Conducting disruption free group meetings, virtual appointments, and B2C engagements often require controls to manage noise from inattentive participants. A participant might be driving and speaking to their friends without realizing that their noise and conversation is being relayed to participants in the meeting. The ability to remotely mute a VoIP participant comes handy in such situations. It enables another participant to remotely mute one or more VoIP participants in the call. Participants who are muted can unmute themselves when they need to speak.
100
+
101
+
The ability to remotely mute a participant is now generally available for calls with the following specific functions:
102
+
103
+
- A VoIP user remotely mutes all other VoIP participants in an Azure Communications Services Rooms and group calls using the following API operation:
104
+
105
+
```javascript
106
+
awaitcall.muteAllRemoteParticipants();
107
+
```
108
+
109
+
- A VoIP user remotely mutes one or several VoIP participants in an Azure communications services Rooms and group calls using the following API operation:
110
+
111
+
```javascript
112
+
awaitcall.remoteParticipants[0].mute();
113
+
```
114
+
115
+
In Azure Communication Services Rooms calls, only VoIP users with Presenter role can mute other participants to avoid undesired remote mutes.
116
+
117
+
When a local call participant mutes another participant, it raises the `mutedByOthers` event. This event causes the client to notify the VoIP participant that they're muted.
118
+
119
+
For more information, see [Remote calls > Mute and unmute a call](./how-tos/calling-sdk/manage-calls.md#mute-other-participants).
In addition to server programmability of Rooms and troubleshooting improvements, we also made an array of other improvements to Call Automation that enable more powerful bots and interactive voice response (IVR).
124
+
125
+
- **Hold/Unhold:** Provide developers with the ability to play music while putting participants on hold through supported file formats of WAV and MP3.
126
+
127
+
- **Play multiple audio files:** We enhanced our existing Play and Recognize APIs to support the ability for developers to provide multiple audio files, text, and Speech Synthesis Markup Language (SSML) inputs when requesting a Play or Recognize action.
128
+
129
+
- **Play barge-in:** Developers can provide barge-in capability to the Play action, enabling you to interrupt a current prompt, such as hold music, with a new message such as wait time announcement.
130
+
131
+
- **Play started event:** We enabled a `playStarted` event to let developers know that a play prompt started.
132
+
133
+
- **VoIP to PSTN transfer:** Developers can now transfer VoIP users to PSTN/SIP endpoints. For inbound PSTN calls, the call connection object now contains the PSTN number the user dialed.
134
+
135
+
For more information, see [Call Automation overview](./concepts/call-automation/call-automation.md).
136
+
137
+
### Enhance email communication with inline attachments
138
+
139
+
Email service now offers a public preview of inline image attachments.
140
+
141
+
Email communication is more than just text. It's about creating engaging and visually appealing messages that capture the recipient's attention. One way to engage email recipients is by using inline attachments, which enable you to embed images directly within the email body.
142
+
143
+
Inline attachments are images or other media files that you embed directly within the email content, rather than sending as separate attachments. Inline attachments let the recipient view the images as part of the email body, enhancing the overall visual appeal and engagement.
144
+
145
+
#### Using inline attachments
146
+
147
+
Some reasons to use inline attachments:
148
+
149
+
- **Improved Engagement:** Inline images can make your emails more visually appealing and engaging.
150
+
151
+
- **Better Branding:** Embedding your logo or other brand elements directly in the email can reinforce your brand identity.
152
+
153
+
- **Enhanced User Experience:** Inline images can help illustrate your message more effectively, making it easier for recipients to understand and act on your content.
154
+
155
+
#### Benefits of using CID for inline attachments
156
+
157
+
We use the HTML attribute content-ID (CID) to embed images directly into the email body. Using CID for inline attachments is considered the best approach for the following reasons:
158
+
159
+
- **Reliability:** CID embedding references the image data using a unique identifier, rather than embedding the data directly in the email body. CID embedding ensures that the images are reliably displayed across different email clients and platforms.
160
+
161
+
- **Efficiency:** CID enables you to attach the image to the email and reference it within the HTML content using the unique content-ID. This method is more efficient than base64 encoding, which can significantly increase the size of the email and affect deliverability.
162
+
163
+
- **Compatibility:** Most email clients support CID, ensuring that your inline images are displayed correctly for most recipients.
164
+
165
+
- **Security:** Using CID avoids the need to host images on external servers, which can pose security risks. Instead, the images are included as part of the email, reducing the risk of external content being blocked or flagged as suspicious.
- [Send email with attachments using Azure Communication Services](./quickstarts/email/send-email-advanced/send-email-with-attachments.md)
170
+
- [Send email with inline attachments using Azure Communication Services](./quickstarts/email/send-email-advanced/send-email-with-inline-attachments.md)
171
+
172
+
### Connect multiple custom domains per email resource
173
+
174
+
Developers can now connect multiple custom domains with the same Azure Communication Services resource. This feature enables Developers to manage their Azure Communication Services resources more effectively to support various business applications or customers using different custom domains. This feature is currently in public preview.
175
+
176
+
Some scenarios in which connecting multiple custom domains is useful:
177
+
178
+
- Messaging organizations that need to support multiple custom domains across several applications can use one Azure Communication Services resource to manage and support these applications, reducing resource management efforts.
179
+
180
+
- SaaS service providers can manage many customers with fewer Azure Communication Services resources.
181
+
182
+
email-resource-demo.png
183
+
184
+
> [!NOTE]
185
+
> We enable customers to link up to 100 custom domains to a single communication service resource. All Mail-From addresses configured under these custom domains are accessible for the communication service resource. You can only link verified custom domains.
186
+
187
+
For more information, see [Connect a verified email domain](./quickstarts/email/connect-email-communication-resource.md)
188
+
189
+
## September 2024
190
+
191
+
### Native UI Library customization and accessibility
192
+
193
+
We have a suite of new features for the open source Calling Native UI Library that provide enhanced customization options and improved accessibility for developers building communication experiences on Android and iOS. Developers can use these APIs to make video calling better fit their brand identity, provide improved user experiences, and ensure their services are accessible to a wider audience.
194
+
195
+
#### Empower brands
196
+
197
+
You can now use the Native UI Library to:
198
+
- Change interface colors to match brand themes.
199
+
- Customize call title and subtitle for personalized interactions.
200
+
- Configure the button bar by adding, removing, or modifying action buttons to suit specific business workflows.
201
+
202
+
#### Use cases
203
+
204
+
- **Healthcare Providers**
205
+
206
+
A telemedicine platform can now align in-call interfaces with its brand colors, giving patients a familiar and trustworthy experience. Customizing the call title to display **Telemedicine Session** and adding subtitles like **Dr. Jane Doe** help ensure that patients know exactly whom they’re speaking with. Developers can further tailor the call interface by adding or removing buttons, such as a custom **End Consultation** button.
207
+
208
+
- **Custom Workflows for Customer Support**
209
+
210
+
Enterprises providing customer support through calling can now use customized buttons to streamline the user experience. For example, instead of a generic button layout, they can configure buttons like **Hold**, **Transfer to Supervisor**, or **Open Ticket** to match their specific operational workflows. Custom workflows improve agent efficiency and enhance customer satisfaction.
211
+
212
+
native-ui-custom-workflows.png
213
+
214
+
#### Captions components
215
+
216
+
Accessibility is a key consideration for businesses aiming to reach diverse audiences. Closed captions for Azure Communication Services and Teams interop calls can improve the communication experience for users with hearing impairments. You can also use closed captions in situations where audio clarity may be compromised such as noisy environments.
217
+
218
+
native-ui-closed-captions.png
219
+
220
+
For more information, see Native UI Library tutorials:
221
+
- [Theme the UI Library in an application (adjust colors)](./how-tos/ui-library-sdk/theming.md)
We introduced new functions in bring your own storage (BYOS) for call recording. The enhancements provide customers with the option to download their recordings and receive notifications if recording uploads to their storage fail due to misconfiguration.
229
+
230
+
When the first attempt to upload to a customer’s blob storage fails, status and error codes are provided. These codes address common issues such as:
231
+
232
+
- Managed Identity not enabled
233
+
- Permissions not set up correctly
234
+
- Container does not exist
235
+
- Invalid container name or storage path
236
+
237
+
These error messages help reduce the loss of recordings by providing timely notifications for manual action (such as direct download) and guiding customers to resolve configuration issues for BYOS.
238
+
239
+
For more information, see [Bring your own Azure storage overview](./concepts/call-automation/call-recording/bring-your-own-storage.md).
240
+
18
241
## August 2024
19
242
20
243
### Enhance custom app experiences with Microsoft Teams
0 commit comments