segment resource type
Namespace: microsoft.graph.callRecords
Represents a portion of a User-User communication or a User-Meeting communication in the case of a Conference call. A typical VOIP call has one segment per session. In certain scenarios, such as PSTN calls, there are multiple segments per session due to additional server-to-server communication required to connect the call.
Methods
No methods exist to directly access segments. Use the Get callRecord
API with $expand=sessions($expand=segments)
or the List session API with
$expand=segments
to get the segments for a callRecord.
Properties
Property | Type | Description |
---|---|---|
callee | microsoft.graph.callRecords.endpoint | Endpoint that answered this segment. |
caller | microsoft.graph.callRecords.endpoint | Endpoint that initiated this segment. |
endDateTime | DateTimeOffset | UTC time when the segment ended. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z |
failureInfo | microsoft.graph.callRecords.failureInfo | Failure information associated with the segment if it failed. |
id | String | Unique identifier for the segment. Read-only. |
media | microsoft.graph.callRecords.media collection | Media associated with this segment. |
startDateTime | DateTimeOffset | UTC time when the segment started. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z |
Relationships
None
JSON representation
The following JSON representation shows the resource type.
{
"callee": {"@odata.type": "microsoft.graph.callRecords.endpoint"},
"caller": {"@odata.type": "microsoft.graph.callRecords.endpoint"},
"endDateTime": "String (timestamp)",
"failureInfo": {"@odata.type": "microsoft.graph.callRecords.failureInfo"},
"id": "String (identifier)",
"media": [{"@odata.type": "microsoft.graph.callRecords.media"}],
"startDateTime": "String (timestamp)"
}
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應