@@ -13,3 +13,344 @@ ms.service: azure-communication-services
13
13
ms.subservice : calling
14
14
---
15
15
16
+ # Contents
17
+
18
+ [ 1 Developing [ 1] ( #developing )] ( #developing )
19
+
20
+ [ 1.1 Monitoring [ 1] ( #monitoring )] ( #monitoring )
21
+
22
+ [ 1.2 table 1 [ 1] ( #table-1 )] ( #table-1 )
23
+
24
+ [ 1.3 table 2 [ 1] ( #table-2 )] ( #table-2 )
25
+
26
+ [ 1.3.1 3 sections in [ 2] ( #sections-in )] ( #sections-in )
27
+
28
+ [ Heading no number [ 2] ( #heading-no-number )] ( #heading-no-number )
29
+
30
+ [ Heading no number 2 levels
31
+ [ 2] ( #heading-no-number-2-levels )] ( #heading-no-number-2-levels )
32
+
33
+ # Developing
34
+
35
+ This article
36
+
37
+ - Phone - [ Public
38
+ concepts] ( https://learn.microsoft.com/en-us/azure/communication-services/concepts/telephony/telephony-concept )
39
+
40
+ ## Monitoring
41
+
42
+ Before you
43
+
44
+ - *** “Quoted bold italic”***
45
+
46
+ Call logs will show you important insights on individual calls and your
47
+ overall quality. For more details refer to the [ Call
48
+ Logs] ( https://learn.microsoft.com/en-us/azure/communication-services/concepts/analytics/call-logs-azure-monitor ) .
49
+
50
+ - ** participant<span class =" mark " >EndReason</span >**
51
+
52
+ - You can identify trends leading to unplanned call ends. See our
53
+ > guidance on [ error
54
+ > codes] ( https://learn.microsoft.com/en-us/azure/communication-services/concepts/troubleshooting-info?tabs=csharp%2Cios%2Cdotnet#calling-sdk-error-codes ) .
55
+
56
+ ## table 1
57
+
58
+ ** table**
59
+
60
+ <table >
61
+ <colgroup >
62
+ <col style =" width : 60% " />
63
+ <col style =" width : 39% " />
64
+ </colgroup >
65
+ <thead >
66
+ <tr class =" header " >
67
+ <th ><strong >Call Setup Failures reason</strong ></th >
68
+ <th ><strong >Typical cause</strong ></th >
69
+ </tr >
70
+ </thead >
71
+ <tbody >
72
+ <tr class =" odd " >
73
+ <td >Missing FW Deep Packet Inspection Exemption Rule</td >
74
+ <td >Indicates that network equipment</td >
75
+ </tr >
76
+ <tr class =" even " >
77
+ <td >Missing FW IP Block Exception Rule</td >
78
+ <td >Indicates that network equ</td >
79
+ </tr >
80
+ </tbody >
81
+ </table >
82
+
83
+ table
84
+
85
+ <table >
86
+ <colgroup >
87
+ <col style =" width : 38% " />
88
+ <col style =" width : 14% " />
89
+ <col style =" width : 22% " />
90
+ <col style =" width : 24% " />
91
+ </colgroup >
92
+ <thead >
93
+ <tr class =" header " >
94
+ <th >Type</th >
95
+ <th >Area</th >
96
+ <th >Owner name</th >
97
+ <th >Sign-off</th >
98
+ </tr >
99
+ </thead >
100
+ <tbody >
101
+ <tr class =" odd " >
102
+ <td >PM</td >
103
+ <td >Business</td >
104
+ <td >Alex Magginetti</td >
105
+ <td ></td >
106
+ </tr >
107
+ </tbody >
108
+ </table >
109
+
110
+ Code
111
+
112
+ /\*\*
113
+
114
+ \* Feature for ACS Live Streaming
115
+
116
+ \* @beta
117
+
118
+ \* /
119
+
120
+ export interface CallSurveyFeature extends CallFeature {
121
+
122
+ /\*\*
123
+
124
+ \* Send the end of call survey
125
+
126
+ \* @param survey - survey data
127
+
128
+ \* /
129
+
130
+ submitSurvey(survey?: CallSurvey): void;
131
+
132
+ }
133
+
134
+ Code
135
+
136
+ Sample JSON Object-
137
+
138
+ {
139
+
140
+ "acsResourceId": "d71d19e6-f4e1-4abe-967a-e2a474a27582",
141
+
142
+ }
143
+
144
+ Table black highlight on first row
145
+
146
+ <table >
147
+ <colgroup >
148
+ <col style =" width : 43% " />
149
+ <col style =" width : 10% " />
150
+ <col style =" width : 46% " />
151
+ </colgroup >
152
+ <thead >
153
+ <tr class =" header " >
154
+ <th >JSON Field Name</th >
155
+ <th >Data Type</th >
156
+ <th >Description</th >
157
+ </tr >
158
+ </thead >
159
+ <tbody >
160
+ <tr class =" odd " >
161
+ <td >acsResourceId</td >
162
+ <td >String</td >
163
+ <td >The ACS resource ID uniquely identifies the ACS resource used to
164
+ make the call</td >
165
+ </tr >
166
+ </tbody >
167
+ </table >
168
+
169
+ ## table 2
170
+
171
+ ** table**
172
+
173
+ <table >
174
+ <colgroup >
175
+ <col style =" width : 12% " />
176
+ <col style =" width : 87% " />
177
+ </colgroup >
178
+ <thead >
179
+ <tr class =" header " >
180
+ <th ><strong >Remediation</strong ></th >
181
+ <th ><strong >Guidance</strong ></th >
182
+ </tr >
183
+ </thead >
184
+ <tbody >
185
+ <tr class =" odd " >
186
+ <td ><strong >Network/internet</strong ></td >
187
+ <td ><p ><strong >Congestion</strong >: Work included <a
188
+ href="https://learn.microsoft.com/en-us/microsoftteams/quality-of-experience-review-guide#quality-investigations">Quality
189
+ Poor Stream summary reports</a > to<br />
190
+ <br />
191
+ <strong >QoS</strong >: If increasing bandwidth is impractical or
192
+ cost-prohibitive, consider implementing QoS. This tool is very effective
193
+ at managing congested traffic and can guarantee that media packets on
194
+ the managed network are prioritized above non-media traffic.
195
+ Alternatively, if there's no clear evidence that bandwidth is the
196
+ culprit, consider these solutions:</p >
197
+ <ul >
198
+ <li ><p ><a
199
+ href="https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams">Microsoft
200
+ Teams QoS guidance</a ></p ></li >
201
+ </ul >
202
+ <p ><strong >Perform a network readiness assessment</strong >: A network
203
+ assessment provides details about expected bandwidth usage, how to cope
204
+ with bandwidth and network changes, and recommended networking practices
205
+ for Teams and Skype for Business. Using the preceding table as your
206
+ source, you have a list of buildings or subnets that are excellent
207
+ candidates for an assessment.</p >
208
+ <ul >
209
+ <li ><p ><a
210
+ href="https://learn.microsoft.com/en-us/microsoftteams/prepare-network">Prepare
211
+ your organization's network for Teams</a ></p ></li >
212
+ </ul ></td >
213
+ </tr >
214
+ </tbody >
215
+ </table >
216
+
217
+ ### 3 sections in
218
+
219
+ text
220
+
221
+ #### 4 sections in
222
+
223
+ text
224
+
225
+ ##### 5 sections in
226
+
227
+ # Heading no number
228
+
229
+ text
230
+
231
+ ## Heading no number 2 levels
232
+
233
+ Text
234
+
235
+ table
236
+
237
+ <table >
238
+ <colgroup >
239
+ <col style =" width : 31% " />
240
+ <col style =" width : 35% " />
241
+ <col style =" width : 33% " />
242
+ </colgroup >
243
+ <thead >
244
+ <tr class =" header " >
245
+ <th ><strong >Metric average</strong ></th >
246
+ <th ><strong >Description</strong ></th >
247
+ <th ><strong >User experience</strong ></th >
248
+ </tr >
249
+ </thead >
250
+ <tbody >
251
+ <tr class =" odd " >
252
+ <td >Jitter > ; </td >
253
+ <td >This is the average</td >
254
+ <td >The packe</td >
255
+ </tr >
256
+ </tbody >
257
+ </table >
258
+
259
+ Picture 1 and 2
260
+
261
+ <img src="media/image1.png" style="width:6.5in;height:1.12986in"
262
+ alt="picture 1" /><img src="media/image2.png" style="width:6.5in;height:0.64236in"
263
+ alt="picture 2" />
264
+
265
+ Picture 3
266
+
267
+ <img src="media/image3.png" style="width:5.35673in;height:2.91472in"
268
+ alt="picture 3" />
269
+
270
+ Video – link to embedded Microsoft video:
271
+ < https://www.microsoft.com/en-us/videoplayer/embed/RWGTqQ >
272
+
273
+ Video – “Insert \> online videos” in word. Same vide as above
274
+
275
+ Won’t work since not supported – needs to manually be added later.
276
+
277
+ Video – link to youtube:
278
+
279
+ [ Join your calling app to a Microsoft Teams meeting with Azure
280
+ Communication Services -
281
+ YouTube] ( https://www.youtube.com/embed/FF1LS516Bjw )
282
+
283
+ Video – “Insert \> online videos” in word. Same vide as above
284
+
285
+ <img src="media/image4.jpg" style="width:5in;height:3.75in"
286
+ alt="Video 1: Join your calling app to a Microsoft Teams meeting with Azure Communication Services" />
287
+
288
+ <table >
289
+ <colgroup >
290
+ <col style =" width : 64% " />
291
+ <col style =" width : 35% " />
292
+ </colgroup >
293
+ <thead >
294
+ <tr class =" header " >
295
+ <th ><strong >API Rating Categories</strong ></th >
296
+ <th ><strong >Question Goal</strong ></th >
297
+ </tr >
298
+ </thead >
299
+ <tbody >
300
+ <tr class =" odd " >
301
+ <td ><ol type =" 1 " >
302
+ <li ><p >Overall Call</p ></li >
303
+ </ol ></td >
304
+ <td >Responses indicate how a call participant perceived their
305
+ <strong >overall</strong > call quality.</td >
306
+ </tr >
307
+ </tbody >
308
+ </table >
309
+
310
+ <table >
311
+ <colgroup >
312
+ <col style =" width : 20% " />
313
+ <col style =" width : 11% " />
314
+ <col style =" width : 12% " />
315
+ <col style =" width : 55% " />
316
+ </colgroup >
317
+ <thead >
318
+ <tr class =" header " >
319
+ <th ><strong >API Rating Categories</strong ></th >
320
+ <th ><strong >Cutoff Value*</strong ></th >
321
+ <th ><strong >Input Range</strong ></th >
322
+ <th ><strong >Comments</strong ></th >
323
+ </tr >
324
+ </thead >
325
+ <tbody >
326
+ <tr class =" odd " >
327
+ <td >Overall Call</td >
328
+ <td >2</td >
329
+ <td >1 - 5</td >
330
+ <td >Survey’s a calling participant’s overall quality experience on a
331
+ scale of 1-5 where 1 indicates an imperfect call experience and 5
332
+ indicates a perfect call. The cutoff value of 2 means that a customer
333
+ response of 1 or 2 indicates a less than perfect call experience.</td >
334
+ </tr >
335
+ </tbody >
336
+ </table >
337
+
338
+ <table >
339
+ <colgroup >
340
+ <col style =" width : 15% " />
341
+ <col style =" width : 84% " />
342
+ </colgroup >
343
+ <thead >
344
+ <tr class =" header " >
345
+ <th ><strong >Rating Categories</strong ></th >
346
+ <th ><strong >Optional Tags</strong ></th >
347
+ </tr >
348
+ </thead >
349
+ <tbody >
350
+ <tr class =" odd " >
351
+ <td >Overall Call</td >
352
+ <td >'CallCannotJoin' | 'CallCannotInvite' | 'HadToRejoin' |
353
+ 'CallEndedUnexpectedly' | 'OtherIssues'</td >
354
+ </tr >
355
+ </tbody >
356
+ </table >
0 commit comments