Microsoft 團隊 PSTN 使用方式報告Microsoft Teams PSTN usage report
Microsoft [團隊管理中心] 中的 [團隊 PSTN 使用方式] 報告可讓您在組織中進行通話和音訊會議活動的概覽。The Teams PSTN usage report in the Microsoft Teams admin center gives you an overview of calling and audio conferencing activity in your organization. 如果您使用自己的電話運營商,您可以查看通話方案的詳細通話活動(如果您使用的是電話語音運營商),以及直接路由。You can view detailed calling activity for Calling Plans if you use Microsoft as your telephony carrier and for Direct Routing if you use your own telephony carrier.
[ 通話方案 ] 索引標籤會顯示資訊,包括使用者在輸入和輸出 PSTN 通話中所花費的分鐘數,以及這些通話的成本。The Calling Plans tab shows information including the number of minutes that users spent in inbound and outbound PSTN calls and the cost of these calls. [ 直接路由 ] 索引標籤會顯示您的資訊,包括 SIP 位址及呼叫開始和結束時間。The Direct Routing tab shows you information including the SIP address and call start and end times. 使用此報告中的資訊,深入瞭解貴組織中的 PSTN 使用量,並協助您調查、規劃及做出業務決策。Use the information in this report to gain insight into PSTN usage in your organization and help you to investigate, plan, and make business decisions.
注意
如果您有 Telstra 或 Softbank 通話方案,就不會在 PSTN 使用狀況報告中看到任何通話詳細資料記錄。If you have a Telstra or Softbank calling plan, you will not see any call detail records in the PSTN usage report. 如需報告需求,請與 Telstra 或 Softbank。Please contact Telstra or Softbank for your reporting needs.
查看 PSTN 使用狀況報告View the PSTN usage report
- 在 Microsoft [團隊管理中心] 的左導覽中,按一下 [分析] & 報告 > 使用方式報告。In the left navigation of the Microsoft Teams admin center, click Analytics & reports > Usage reports. 在 [ 查看報表 ] 索引標籤的 [ 報表] 底下,選取 [ PSTN 使用方式報告]。On the View reports tab, under Report, select PSTN usage report.
- 在 [ 日期範圍] 底下,選取7或28天的預先定義範圍,或設定自訂範圍,然後選取 [ 執行報表]。Under Date range, select a predefined range of 7 or 28 days, or set a custom range, and then select Run report.
解讀報表Interpret the report
通話方案Calling Plans
圖說文字Callout | 描述Description |
---|---|
11 | 您可以在過去7天、28天或您設定的自訂日期範圍中查看趨勢The report can be viewed for trends over the last 7 days, 28 days, or a custom date range that you set |
22 | 每個報告都有產生的日期。Each report has a date for when it was generated. 報告通常會反映來自啟用時間的24到48小時延遲時間。The reports usually reflect a 24 to 48 hour latency from time of activity. |
33 | X 軸是特定報表的已選取日期範圍。The X axis is the selected date range for the specific report. Y 軸是在所選時段內的通話總數目。The Y axis is the total number of calls over the selected time period. 將游標暫留在指定日期上的點上,即可查看該日期的總通話情況。Hover over the dot on a given date to see the total calls on that date. |
44 | 下表提供每個通話的 PSTN 使用量細分。The table gives you a breakdown of PSTN usage per call.
|
5005 | 選取 [ 編輯欄 ] 以新增或移除表格中的欄。Select Edit columns to add or remove columns in the table. |
66 | 選取 [ 篩選 ],依使用者名稱或通話類型篩選報表Select Filter to filter the report by username or call type |
utf-77 | 選取 [ 全螢幕 ],以全螢幕模式查看報告。Select Full screen to view the report in full screen mode. |
型8 | 您可以將報表匯出為 CSV 檔案,以便進行離線分析。You can export the report to a CSV file for offline analysis. 按一下 [ 匯出至 Excel],然後在 [ 下載 ] 索引標籤上,按一下 [ 下載 ] 以在準備好時下載報告。Click Export to Excel, and then on the Downloads tab, click Download to download the report when it's ready. |
直接路由Direct Routing
圖說文字Callout | 描述Description |
---|---|
11 | 您可以在過去7天或28天的趨勢中查看報告。The report can be viewed for trends over the last 7 days or 28 days. |
22 | 每個報告都有產生的日期。Each report has a date for when it was generated. 報告通常會反映來自啟用時間的24到48小時延遲時間。The reports usually reflect a 24 to 48 hour latency from time of activity. |
33 | X 軸是特定報表的已選取日期範圍。The X axis is the selected date range for the specific report. Y 軸是在所選時段內的通話總數目。The Y axis is the total number of calls over the selected time period. 將游標暫留在指定日期上的點上,即可查看該日期的總通話情況。Hover over the dot on a given date to see the total calls on that date. |
44 | 下表提供每個通話的 PSTN 使用量細分。The table gives you a breakdown of PSTN usage per call.
|
5005 | 選取 [ 編輯欄 ] 以新增或移除表格中的欄。Select Edit columns to add or remove columns in the table. |
66 | 選取 [ 全螢幕 ],以全螢幕模式查看報告。Select Full screen to view the report in full screen mode. |
utf-77 | 選取 [ 匯出至 Excel ],將資料下載到以逗號分隔的檔案 (CSV) 進行離線分析,或將它做為帳單系統的輸入。Select Export to Excel to download the data in a comma separated file (CSV) for offline analysis or to use it as input for your billing system. |
來電者/被叫方的欄位考慮Caller/Callee fields considerations
根據呼叫方向,來電者或叫用方程式名稱可以包含非 E164 的號碼。Depending on the call direction, the Caller or Callee names can contain non-E164 numbers.
這些欄位可以來自客戶 SBC (s) 。These fields can come from the customer SBC(s). SBC 可以傳送至直接路由的格式有三種: E. 164 個數字、非 E. 164 個數字和字串。There are three formats that the SBC can send to Direct Routing: E.164 numbers, non-E.164 numbers, and strings.
- 如果使用者使用的是 e. 164 號碼的使用者,則會有164個電話號碼。E.164 phone number from a user who has an E.164 number to a user who also has an E.164 number.
- 從非 E. 164 號碼撥打電話。Call from a non-E.164 number. 使用直接佈線的協力廠商 PBX 相互連接的使用者,就能呼叫小組使用者。A user from a third-party PBX interconnected with Direct Routing makes a call to a Teams user. 在這種情況下,來電者號碼可以是任何非 E. 164 個數字,例如 + 1001。In this case, the caller number might be any non-E.164 number, for example +1001.
- 垃圾郵件者來電,不會顯示數位,只是名稱,例如「內部收入服務」。A spammer calls and doesn't present a number, only a name, for example "Internal Revenue Service". 這個字串將會顯示在報表中。This string will be shown in the reports.
關於共用的相關識別碼About Shared Correlation ID
共用的相關識別碼只會存在於您下載的匯出 Excel 檔案中,並指出兩個或多個通話是相關的。The Shared Correlation ID only exists in the exported Excel file that you download and indicates that two or more calls are related. 下列說明不同的案例,以及共用的相關識別碼存在時。The following explains the different scenarios, and when Shared Correlation ID is present.
- Pstn 使用者1在團隊用戶端上名為「團隊使用者1」的 PSTN 端點上,通話類型 Dr_In,相關識別碼 57f28917-42k5-4c0c-9433-79734873f2ac,無共用的關聯 ID。PSTN User 1 on a PSTN endpoint called Teams User 1 on Teams client, call type Dr_In, correlation ID 57f28917-42k5-4c0c-9433-79734873f2ac, no shared correlation ID.
- 小組使用者1在 PSTN 端點上稱為 PSTN 使用者1的團隊用戶端上,呼叫 type Dr_Out 2c12b8ca-62eb-4c48-b68d-e451f518ff4,無共用的相關識別碼。Teams User 1 on Teams client called PSTN User 1 on a PSTN endpoint, call type Dr_Out 2c12b8ca-62eb-4c48-b68d-e451f518ff4, no shared correlation ID.
- PSTN 使用者1在團隊用戶端上稱為團隊使用者2,呼叫類型 Dr_In f45e9a25-9f94-46e7-a457-84f5940efde9,共用相關識別碼 f45e9a25-9f94-46e7-a457-84f5940efde9。PSTN User 1 on a PSTN endpoint called a Teams User 2 on Teams client, call type Dr_In f45e9a25-9f94-46e7-a457-84f5940efde9, shared correlation ID f45e9a25-9f94-46e7-a457-84f5940efde9.
- 現有的呼叫3,相關 ID 為 "f45e9a25-9f94-46e7-a457-84f5940efde9"。Existing call 3 with correlation ID "f45e9a25-9f94-46e7-a457-84f5940efde9". 在與團隊使用者2通話中的 PSTN 使用者1。PSTN User 1 in a call with Teams User 2. 團隊使用者2已將 (盲人或諮詢式) 呼叫團隊或 PSTN 使用者、呼叫類型 Dr_Out_User_Transfer 45a1da7c-9e97-481a-8a05-3fe19a9a77e0、共用的相關識別碼 f45e9a25-9f94-46e7-a457-84f5940efde9。Teams User 2 transferred (blind or consultative) a call to Teams or PSTN User, call type Dr_Out_User_Transfer 45a1da7c-9e97-481a-8a05-3fe19a9a77e0, shared correlation ID f45e9a25-9f94-46e7-a457-84f5940efde9.
匯出報表Exporting the reports
按一下 [ 匯出至 Excel],然後在 [ 下載 ] 索引標籤上,按一下 [ 下載 ] 以在準備好時下載報告。Click Export to Excel, and then on the Downloads tab, click Download to download the report when it's ready. 匯出程式可能需要幾秒鐘到數分鐘的時間,才能完成,視資料數量而定。Export process can take from a few seconds to several minutes to complete, depending on the quantity of the data.
這會匯出所有使用者的資料,並可讓您進行簡單的排序與篩選,以進行進一步分析。This exports data of all users and enables you to do simple sorting and filtering for further analysis. 匯出的檔案包含無法在線上報表中使用的其他欄位。Exported files contain additional fields that are not available in the online report. 這些都可以用來進行疑難排解和自動化工作流程。These can be used for troubleshooting and automated workflows.
您會收到名為「通話. 匯出」的 zip [identifier]
檔案。zip",且識別碼是匯出的唯一識別碼,可以用來進行疑難排解。You will receive a zip file named "Calls.Export.[identifier]
.zip", with the identifier being an unique ID for the export that can be used for troubleshooting.
如果您同時擁有通話方案和直接路由,匯出的檔案可能會包含這兩個產品的資料。If you have both Calling Plans and Direct Routing, the exported file may contain data for both products. PSTN 使用狀況報告檔案將會有檔案名 "PSTN. [UTC date]
。csv"與直接路由"DirectRouting [UTC date]
。csv"。PSTN usage report file will have filename "PSTN.calls.[UTC date]
.csv" and Direct Routing "DirectRouting.calls.[UTC date]
.csv".
除了 PSTN 和直接路由檔案之外,封存還包含檔案 "parameters.json",以及所選匯出時間範圍和功能。In addition to PSTN and Direct Routing files, the archive contains file "parameters.json", with the selected export time range and capabilities.
匯出的檔案是以逗號分隔的值 (CSV) 格式,符合 RFC 4180 標準。Exported files are in Comma Separated Values (CSV) format, compliant with RFC 4180 standard. 您可以在 Excel 或任何其他符合標準的編輯者中開啟檔案,而不需要任何轉換。The files can be opened in Excel or any other standards-compliant editor without requiring any transformations.
CSV 的第一列包含資料行名稱。The first row of the CSV contains column names. 所有日期都是 UTC,且是 ISO 8601 格式。All dates are UTC and in ISO 8601 format.
已匯出的 PSTN 使用狀況報告Exported PSTN usage report
除非國家/地區專用的規章禁止將資料保留12個月,否則您可以從目前日期開始匯出一年的資料。You can export data up to one year from the current date unless country-specific regulations prohibit retention of the data for 12 months.
# | 名稱Name | (SQL Server) 的資料類型 Data type (SQL Server) | 描述Description |
---|---|---|---|
00 | UsageIdUsageId | uniqueidentifier |
唯一的呼叫識別碼Unique call identifier |
11 | 通話 IDCall ID | nvarchar(64) |
[通話識別碼]。Call identifier. 不保證唯一Not guaranteed to be unique |
22 | 會議 IDConference ID | nvarchar(64) |
音訊會議的識別碼ID of the audio conference |
33 | 使用者位置User Location | nvarchar(2) |
使用者的國家/地區代碼, ISO 3166-1 Alpha-2Country code of the user, ISO 3166-1 alpha-2 |
44 | AAD ObjectIdAAD ObjectId | uniqueidentifier |
在 Azure Active Directory 中呼叫使用者的 ID。Calling user's ID in Azure Active Directory. 對於 bot 呼叫類型 (ucap_in、ucap_out) ,此和其他使用者資訊將會是 null/空。This and other user info will be null/empty for bot call types (ucap_in, ucap_out) |
5005 | UPNUPN | nvarchar(128) |
UserPrincipalName (在 Azure Active Directory 中) 登入名稱。UserPrincipalName (sign in name) in Azure Active Directory. 這通常與使用者的 SIP 位址相同,而且可以與使用者的電子郵件地址相同This is usually the same as user's SIP Address, and can be same as user's e-mail address |
66 | 使用者顯示名稱User Display Name | nvarchar(128) |
使用者的顯示名稱Display name of the user |
utf-77 | 來電顯示Caller ID | nvarchar(128) |
已接收撥入通話通話或撥出通話電話號碼的號碼。Number that received the call for inbound calls or the number dialed for outbound calls. E. 164 格式E.164 format |
型8 | 通話類型Call Type | nvarchar(32) |
通話是 PSTN 輸出或撥入通話,以及撥打電話類型(例如使用者或音訊會議發出的通話)Whether the call was a PSTN outbound or inbound call and the type of call such as a call placed by a user or an audio conference |
99 | 數位類型Number Type | nvarchar(16) |
使用者的電話號碼類型,例如免付費電話號碼的服務User's phone number type, such as a service of toll-free number |
第10 | 國內/國際Domestic/International | nvarchar(16) |
根據使用者的位置,在國家或地區內) 或國際 () 以外的電話撥打電話給國內 (Whether the call was domestic (within a country or region) or international (outside a country or region) based on the user's location |
1111 | 已撥號目的地Destination Dialed | nvarchar(64) |
已撥打國家或地區Country or region dialed |
之間12 | 目的地編號Destination Number | nvarchar(32) |
以 164 格式撥打的號碼Number dialed in E.164 format |
合13 | 開始時間Start Time | datetimeoffset |
呼叫開始時間Call start time |
414 | 結束時間End Time | datetimeoffset |
通話結束時間Call end time |
工資15 | 持續時間秒Duration Seconds | int |
通話的連線時間How long the call was connected |
位16 | 連線費用Connection Fee | numeric(16, 2) |
連接費價格Connection fee price |
11x1717 | 收費Charge | numeric(16, 2) |
支付給帳戶所需通話的金額或成本Amount of money or cost of the call that is charged to your account |
滿18 | 貨幣Currency | nvarchar(3) |
用來計算通話成本的貨幣類型 (ISO 4217) Type of currency used to calculate the cost of the call (ISO 4217) |
合19 | 功能Capability | nvarchar(32) |
通話所用的授權The license used for the call |
已匯出直接路由使用方式報告Exported Direct Routing usage report
您最多可以將資料匯出至五個月 (150 天) 從目前日期開始,除非國家或地區特定的規章禁止保留該期間的資料。You can export data up to five months (150 days) from the current date unless country-specific regulations prohibit retention of the data for that period.
# | 名稱Name | (SQL Server) 的資料類型 Data type (SQL Server) | 描述Description |
---|---|---|---|
00 | IdCorrelationId | uniqueidentifier |
唯一的呼叫識別碼Unique call identifier |
11 | SIP 位址SIP Address | nvarchar(128) |
撥打或接聽電話的使用者或 bot 的位址。The address of the user or bot that made or received the call. 請注意,這實際上是 (UPN,在 Azure Active Directory 中登入名稱) ,這通常與 SIP 位址相同Note that this is actually UserPrincipalName (UPN, sign in name) in Azure Active Directory, which is usually the same as SIP Address |
22 | 顯示名稱Display Name | nvarchar(128) |
使用者或通話 bot 的名稱 (例如,通話佇列或自動語音應答) 在 Microsoft 365 系統管理中心設定The name of a user or a calling bot (for example, Call Queue or Auto Attendant) as set in Microsoft 365 admin center |
33 | 使用者所在國家/地區User country | nvarchar(2) |
使用者的國家/地區代碼, ISO 3166-1 Alpha-2Country code of the user, ISO 3166-1 alpha-2 |
44 | 邀請時間Invite time | datetimeoffset |
當初始邀請是從團隊使用者或 bot 呼叫到 SBC,或從 SBC 直接路由的 SIP Proxy 元件呼叫給團隊或 bot 撥入時When the initial Invite send on outbound from Teams user or bot call to the SBC, or received on inbound to Teams or bot call by the SIP Proxy component of Direct Routing from the SBC |
5005 | 開始時間Start time | datetimeoffset |
SIP proxy 收到最終的回應 (SIP 訊息 "200 確定" ) 從輸出 (小組/Bot 的 SBC 到 PSTN 使用者) ,或者在 SIP Proxy 將邀請傳送給在撥入呼叫 (PSTN 使用者的「團隊結束」) 中的下一個躍點。Time when the SIP proxy received the final answer (SIP Message "200 OK") from the SBC on outbound (Teams/Bot to a PSTN User), or after the SIP Proxy send the Invite to the next hop within Teams backend on inbound call (PSTN User to a Teams/Bot). 對於失敗與未接聽的通話,這可以等於邀請或失敗時間For failed and unanswered calls, this can be equal to invite or failure time |
66 | 失敗時間Failure time | datetimeoffset |
僅存在失敗的 (未完全建立) 通話Only exists for failed (not fully established) calls |
utf-77 | 結束時間End time | datetimeoffset |
僅存在成功 (完全建立) 通話的情況。Only exists for successful (fully established) calls. 通話結束的時間Time when call ended |
型8 | 持續時間 (秒) Duration (seconds) | int |
通話持續時間Duration of the call |
99 | 成功案例Success | nvarchar(3) |
[是/否]。Yes/No. 成功或嘗試Success or attempt |
第10 | 來電者號碼Caller Number | nvarchar(32) |
撥打電話之使用者或 bot 的號碼。Number of the user or bot who made the call. 在輸入時,如果是 PSTN 使用者,就會將它設為「團隊」使用者電話的外部使用者電話號碼。On inbound to a Team user call it will be a PSTN User, on outbound from Teams user call it will be the Teams user number |
之間12 | 被呼叫者號碼Callee Number | nvarchar(32) |
接收通話之使用者或 bot 的號碼。Number of the user or bot who received the call. 在 [輸入至小組使用者] 呼叫它將是 [小組] 使用者,在 [由小組使用者通話的出站] 中,它將是 PSTN 使用者On inbound to a Team user call it will be the Teams user, on outbound from Teams user call it will be the PSTN User |
合13 | 通話類型Call type | nvarchar(32) |
通話類型和方向Call type and direction |
414 | 媒體的 Azure 區域Azure region for Media | nvarchar(8) |
在非旁路通話中用於媒體路徑的資料中心The datacenter used for media path in non-bypass call |
工資15 | Azure 地區以進行信號Azure region for Signaling | nvarchar(8) |
針對旁路與非旁路通話的信號所用的資料中心The datacenter used for signaling for both bypass and non-bypass calls |
位16 | 最終 SIP 代碼Final SIP code | int |
通話結束的程式碼, RFC 3261The code with which the call ended, RFC 3261 |
11x1717 | 最終的 Microsoft 子代碼Final Microsoft subcode | int |
除了 SIP 代碼之外,Microsoft 還提供指示特定問題的子代碼In addition to the SIP codes, Microsoft has own subcodes that indicate the specific issue |
滿18 | 最終 SIP 片語Final SIP Phrase | nvarchar(256) |
SIP 代碼與 Microsoft 子代碼的描述Description of the SIP code and Microsoft subcode |
合19 | SBC FQDNSBC FQDN | nvarchar(64) |
會話邊界控制器的完整功能變數名稱Fully qualified domain name of the session border controller |
2020 | 媒體旁路Media bypass | nvarchar(3) |
[是/否]。Yes/No. 指出是否已針對媒體旁路啟用主幹Indicates if the trunk was enabled for media bypass or not |
日前21 | 共用的相關識別碼Shared correlation ID | uniqueidentifier |
表示兩個或多個通話是相關的Indicates that two or more calls are related |