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/analytics/call-logs-azure-monitor.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ The Call Summary Log contains data to help you identify key properties of all Ca
77
77
| operationVersion | The api-version associated with the operation, if the `operationName` was performed using an API. If there is no API that corresponds to this operation, the version represents the version of that operation in case the properties associated with the operation change in the future. |
78
78
| category | The log category of the event. Category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the `properties` blob of an event are the same within a particular log category and resource type. |
79
79
| correlationIdentifier |`correlationIdentifier` is the unique ID for a Call. The `correlationIdentifier` identifies correlated events from all of the participants and endpoints that connect during a single Call, and it can be used to join data from different logs. If you ever need to open a support case with Microsoft, the `correlationID` will be used to easily identify the Call you're troubleshooting. |
80
-
| identifier | This is the unique ID for the user, matching the identity assigned by the Communications Authentication service. You can use this ID to correlate user events across different logs. This ID can also be used to identify Microsoft Teams "Interoperability" scenarios described later in this document. |
80
+
| identifier | This is the unique ID for the user. The identity can be an Azure Communications Services user, Azure AD user ID, Teams anonymous user ID or Teams bot ID. You can use this ID to correlate user events across different logs.|
81
81
| callStartTime | A timestamp for the start of the call, based on the first attempted connection from any Endpoint. |
82
82
| callDuration | The duration of the Call expressed in seconds, based on the first attempted connection and end of the last connection between two endpoints. |
83
83
| callType | Will contain either `"P2P"` or `"Group"`. A `"P2P"` Call is a direct 1:1 connection between only two, non-server endpoints. A `"Group"` Call is a Call that has more than two endpoints or is created as `"Group"` Call prior to the connection. |
@@ -102,7 +102,7 @@ Call Diagnostic Logs provide important information about the Endpoints and the m
102
102
| category | The log category of the event. Category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the `properties` blob of an event are the same within a particular log category and resource type. |
103
103
| correlationIdentifier | The `correlationIdentifier` identifies correlated events from all of the participants and endpoints that connect during a single Call. `correlationIdentifier` is the unique ID for a Call. If you ever need to open a support case with Microsoft, the `correlationID` will be used to easily identify the Call you're troubleshooting. |
104
104
| participantId | This ID is generated to represent the two-way connection between a "Participant" Endpoint (`endpointType` = `“Server”`) and the server. When `callType` = `"P2P"`, there is a direct connection between two endpoints, and no `participantId` is generated. |
105
-
| identifier | This ID represents the useridentity, as defined by the Authentication service. Use this ID to correlate different events across calls and services. |
105
+
| identifier | This is the unique ID for the user. The identity can be an Azure Communications Services user, Azure AD user ID, Teams anonymous user ID or Teams bot ID. You can use this ID to correlate user events across different logs.|
106
106
| endpointId | Unique ID that represents each Endpoint connected to the call, with Endpoint type defined by `endpointType`. When the value is `null`, it means that the connected entity is the Communication Services server. `EndpointId` can persist for the same user across multiple calls (`correlationIdentifier`) for native clients but will be unique for every Call when the client is a web browser. |
107
107
| endpointType | This value describes the properties of each `endpointId`. Can contain `“Server”`, `“VOIP”`, `“PSTN”`, `“BOT”`, or `“Unknown”`. |
108
108
| mediaType | This string value describes the type of media being transmitted between endpoints within each stream. Possible values include `“Audio”`, `“Video”`, `“VBSS”` (Video-Based Screen Sharing), and `“AppSharing”`. |
@@ -408,4 +408,4 @@ Diagnostic log for audio stream from Server Endpoint to VoIP Endpoint 3:
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/pricing.md
-49Lines changed: 0 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,55 +103,6 @@ Note: USA mixed rates to `+1-425` is $0.013. Refer to the following link for det
103
103
104
104
**Total cost for the VoIP + escalation call**: $0.16 + $0.13 = $.29
105
105
106
-
107
-
### Pricing example: A user of the Communication Services JavaScript SDK joins a scheduled Microsoft Teams meeting
108
-
109
-
Alice is a doctor meeting with her patient, Bob. Alice will be joining the visit from the Teams Desktop application. Bob will receive a link to join using the healthcare provider website, which connects to the meeting using the Communication Services JavaScript SDK. Bob will use his mobile phone to enter the meeting using a web browser (iPhone with Safari). Chat will be available during the virtual visit.
110
-
111
-
- The call lasts a total of 30 minutes.
112
-
- When Bob joins the meeting, he's placed in the Teams meeting lobby per Teams policy. After one minute, Alice admits him into the meeting.
113
-
- After Bob is admitted to the meeting, Alice and Bob participate for the entire call. Alice turns on her video five minutes after the call starts and shares her screen for 13 minutes. Bob has his video on for the whole call.
114
-
- Alice sends five messages, Bob replies with three messages.
115
-
116
-
117
-
**Cost calculations**
118
-
119
-
- One Participant (Bob) connected to Teams lobby x 1 minute x $0.004 per participant per minute (lobby charged at regular rate of meetings) = $0.004
120
-
- One participant (Bob) x 29 minutes x $0.004 per participant per minute = $0.116 [both video and audio are charged at the same rate]
121
-
- One participant (Alice) x 30 minutes x $0.000 per participant per minute = $0.0*.
122
-
- One participant (Bob) x three chat messages x $0.0008 = $0.0024.
123
-
- One participant (Alice) x five chat messages x $0.000 = $0.0*.
124
-
125
-
*Alice's participation is covered by her Teams license. Your Azure invoice will show the minutes and chat messages that Teams users had with Communication Services Users for your convenience, but those minutes and messages originating from the Teams client won't be charged.
126
-
127
-
**Total cost for the visit**:
128
-
- User joining using the Communication Services JavaScript SDK: $0.004 + $0.116 + $0.0024 = $0.1224
129
-
- User joining on Teams Desktop Application: $0 (covered by Teams license)
130
-
131
-
### Pricing example: Inbound PSTN call to the Communication Services JavaScript SDK with Teams identity elevated to group call with another Teams user on Teams desktop client
132
-
133
-
Alice has ordered a product from Contoso and struggles to set it up. Alice calls from her phone (Android) 800-CONTOSO to ask for help with the received product. Bob is a customer support agent in Contoso and sees an incoming call from Alice on the customer support website (Windows, Chrome browser). Bob accepts the incoming call via Communication Services JavaScript SDK initialized with Teams identity. Teams calling plan enables Bob to receive PSTN calls. Bob sees on the website the product ordered by Alice. Bob decides to invite product expert Charlie to the call. Charlie sees an incoming group call from Bob in the Teams Desktop client and accepts the call.
134
-
135
-
- The call lasts a total of 30 minutes.
136
-
- Bob accepts the call from Alice.
137
-
- After five minutes, Bob adds Charlie to the call. Charlie has his camera turned off for 10 minutes. Then turns his camera on for the rest of the call.
138
-
- After another 10 minutes, Alice leaves the call.
139
-
- After another five minutes, both Bob and Charlie leave the call
140
-
141
-
**Cost calculations**
142
-
143
-
- One Participant (Alice) called the phone number associated with Teams user Bob using Teams Calling plan x 25 minutes deducted from Bob's tenant Teams minute pool
144
-
- One participant (Bob) x 30 minutes x $0.004 per participant per minute = $0.12 [both video and audio are charged at the same rate]
145
-
- One participant (Charlie) x 25 minutes x $0.000 per participant per minute = $0.0*.
146
-
147
-
*Charlie's participation is covered by his Teams license.
148
-
149
-
**Total cost of the visit**:
150
-
- Teams cost for a user joining using the Communication Services JavaScript SDK: 25 minutes from Teams minute pool
151
-
- Communication Services cost for a user joining using the Communication Services JavaScript SDK: $0.12
152
-
- User joining on Teams Desktop client: $0 (covered by Teams license)
153
-
154
-
155
106
## Call Recording
156
107
157
108
Azure Communication Services allows customers to record PSTN, WebRTC, Conference, SIP Interface calls. Currently Call Recording supports mixed audio+video MP4 and mixed audio-only MP3/WAV output formats. Call Recording SDKs are available for Java and C#. Refer to [this page to learn more](../quickstarts/voice-video-calling/call-recording-sample.md).
0 commit comments