Merge pull request #16298 from MicrosoftDocs/main

Publish main to live, 01/09/25, 3:30 PM PT

Teams/dial-pad-configuration.md

@@ -1,7 +1,7 @@
 ---
 title: Teams dial pad configuration
-author: mkbond007
-ms.author: mabond
+author: sfrancis206
+ms.author: scottfrancis
 manager: pamgreen
 ms.reviewer: cbland
 ms.date: 05/21/2024

Teams/dial-plans-routing-overview.md

@@ -1,7 +1,7 @@
 ---
 title: "Microsoft Teams Dial plans and routing"
-author: CarolynRowe
-ms.author: crowe
+author: sfrancis206
+ms.author: scottfrancis
 manager: pamgreen
 ms.reviewer: roykuntz
 ms.date: 10/02/2023

Teams/direct-routing-analog-devices.md

@@ -1,7 +1,7 @@
 ---
 title: "Direct Routing - Connecting analog devices"
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.reviewer: filippse

Teams/direct-routing-border-controllers.md

@@ -1,9 +1,9 @@
 ---
 title: "Session Border Controllers certified for Direct Routing"
-ms.author: crowe
+ms.author: scottfrancis
 ms.reviewer: FilippSe
 ms.date: 06/12/2024
-author: CarolynRowe
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.topic: article
@@ -92,8 +92,8 @@ Note that we're not accepting new nominations for certification until further no
 ||Cisco Unified Border Element (CUBE) for Catalyst 8000 Edge Platforms|✔|✔|Supported IOS XE Amsterdam 17.3.2 (Recommended 17.6.1a)|✔||
 |[Avaya](https://support.avaya.com/products/P0997/avaya-session-border-controller-for-enterprise/8.1.x)|Avaya Session Border Controller for Enterprise (ASBCE)|✔|✔|Release 8.1.1 or higher (8.1.2 or higher for Media Bypass)|||
 |[Nokia](https://documentation.nokia.com/aces/cgi-bin/chk_access.cgi/3TB30222GBAAACZZA.zip)|Nokia Session Border Controller|✔|✔|23.8|✔||
-|[Italtel](https://www.italtel.com/italtel-provides-direct-routing-sbc-for-microsoft-teams/)|NetMatch-S CI|✔|✔|Supported 5.8 (Recommended the latest version)|✔|✔|
-|[Ericsson](https://www.ericsson.com/en/portfolio/digital-services/cloud-communication/enterprise-communication/business-communication-services-and-enablers/sip-trunking)|vSBC 2.16|✔|||||
+|[Italtel](https://www.italtel.com/italtels-sbc-obtains-microsoft-teams-direct-routing-certification/)|NetMatch-S CI|✔|✔|Supported 5.8 (Recommended the latest version)|✔|✔|
+|[Ericsson](https://www.ericsson.com/en/portfolio/cloud-software-and-services/cloud-communication/enterprise-communication/business-communication-applications-and-enablers/sip-trunking)|vSBC 2.16|✔|||||
 |[Cataleya](https://cataleya.com/cataleya-launches-orchid-cloud-revolutionary-cloud-based-wholesale-voice-business-platform/)|Orchid Link|✔||3.1|||
 |[ULTATEL](https://www.ultatel.com/services/direct-routing-teams-sbc)|Teams SBC|✔|✔|1.6|||
 |[Mitel](https://unify.com/en/solutions/voice-platforms/session-border-controller)|Unify OpenScape Session Border Controller|✔|✔|V10R2.2.0 or higher|||
@@ -124,7 +124,7 @@ The following emergency services providers are certified and supported by Micros
 
 - [Bandwidth Dynamic Location Routing](https://www.bandwidth.com/partners/microsoft-teams-direct-routing/)
 - [Intrado Emergency Routing Service (ERS)](https://www.intrado.com/enterprise-solutions/e911/microsoft-teams)
-- [Inteliquent](https://www.inteliquent.com/services/emergency-services/e911)
+- [Inteliquent](https://sinch.com/news/inteliquent-launches-microsoft-teams-certified-e911-calling/)
 
 ## Support for Local Media Optimization
 
@@ -159,7 +159,7 @@ The following table describes which SBC vendors support [Local Media Optimizatio
 ||AP 3950|9.x|
 ||AP 4900|9.x|
 |[Avaya](https://documentation.avaya.com/en-US/bundle/WorkingWithAvayaSBCEandMicrosoftTeams_r81x/page/About_Avaya_SBCE_and_MS_Teams.html)|Avaya Session Border Controller for Enterprise (ASBCE)|10.1.2 or higher|
-|[Italtel](https://www.italtel.com/italtel-provides-direct-routing-sbc-for-microsoft-teams/)|NetMatch-S CI|5.7 or higher SW version|
+|[Italtel](https://www.italtel.com/italtels-sbc-obtains-microsoft-teams-direct-routing-certification/)|NetMatch-S CI|5.7 or higher SW version|
 |[Enghouse Networks](https://www.enghousenetworks.com/portfolio/network-infrastructure/cloud-native-session-border-controller-sbc/)|Enghouse BorderNet|3.9.2-XY or higher SW version|
 
 ## Direct Routing and analog devices interoperability

Teams/direct-routing-call-notifications.md

@@ -1,7 +1,7 @@
 ---
 title: Manage call notifications for Direct Routing
-author: CarolynRowe
-ms.author: crowe
+author: sfrancis206
+ms.author: scottfrancis
 manager: pamgreen
 ms.date: 10/17/2019
 ms.topic: article

Teams/direct-routing-configure-media-bypass.md

@@ -1,7 +1,7 @@
 ---
 title: "Configure media bypass with Direct Routing"
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.reviewer: 

Teams/direct-routing-configure.md

@@ -2,8 +2,8 @@
 title: "Configure Direct Routing"
 ms.reviewer: filippse
 ms.date: 09/24/2024
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.topic: article

Teams/direct-routing-connect-the-sbc.md

@@ -2,8 +2,8 @@
 title: "Connect your Session Border Controller (SBC) to Direct Routing"
 ms.reviewer: 
 ms.date: 10/03/2023
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.topic: article

Teams/direct-routing-country-codes.md

@@ -1,7 +1,7 @@
 ---
 title: "Direct Routing country codes"
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.reviewer: 
@@ -32,7 +32,7 @@ By using the -MediaRelayRoutingLocationOverride parameter with the New-CsOnlineP
 
 Set-CSOnlinePSTNGateway -Identity sbc1.contoso.com –MediaRelayRoutingLocationOverride DE 
 
-Note that Microsoft only recommends setting this parameter if the call logs clearly indicate that the default assignment of the datacenter for the media path does not use the path closest to the SBC datacenter. 
+Microsoft only recommends setting this parameter if the call logs clearly indicate that the default assignment of the datacenter for the media path doesn't use the path closest to the SBC datacenter. 
 
 ## Country code reference table
 

Teams/direct-routing-enable-users.md

@@ -2,8 +2,8 @@
 title: "Enable users for Direct Routing"
 ms.reviewer: filippse
 ms.date: 08/15/2023
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.topic: article

Teams/direct-routing-health-dashboard.md

@@ -2,8 +2,8 @@
 title: "Health Dashboard for Direct Routing"
 ms.reviewer: nmurav
 ms.date: 05/24/2019
-ms.author: crowe
-author: CarolynRowe
+ms.author: scottfrancis
+author: sfrancis206
 manager: pamgreen
 audience: ITPro
 ms.topic: conceptual
@@ -46,35 +46,35 @@ Health Dashboard provides the following information related to overall health of
 
    The NER measures the ability of networks to deliver calls to the far-end terminal--excluding user actions resulting in call rejections.  If the recipient rejected a call or sent the call to voicemail, the call is counted as a successful delivery. This means that an answer message, a busy signal, or a ring with no answer are all considered successful calls.
 
-   For example, assume Direct Routing sent a call to the SBC and the SBC returns SIP code “504 Server Time-out - The server attempted to access another server in attempting to process the request and did not receive a prompt response”. This response indicates there is an issue on the SBC side, and this will decrease the NER on the Health Dashboard for this SBC.
+   For example, assume Direct Routing sent a call to the SBC and the SBC returns SIP code “504 Server Time-out - The server attempted to access another server in attempting to process the request and didn't receive a prompt response.” This response indicates there's an issue on the SBC side, and this will decrease the NER on the Health Dashboard for this SBC.
 
-   Because the action you take might depend on the number of calls affected, Health Dashboard shows how many calls were analyzed to calculate a parameter. If the number of calls is less than 100, the NER might be quite low, but still be normal.
+   Because the action you take might depend on the number of calls affected, Health Dashboard shows how many calls were analyzed to calculate a parameter. If the number of calls is less than 100, the NER might be low, but still be normal.
 
    The formula used to calculate NER is:
 
    NER = 100 x (Answered calls + User Busy + Ring no Answer + Terminal Reject Seizures)/Total Calls
 
-- **Average call duration** - Information about average call duration can help you monitor the quality of calls. The average duration of a 1:1 PSTN call is four to five minutes.  However, for each company, this average can differ.  Microsoft recommends establishing a baseline for the average call duration for your company. If this parameter goes significantly below the baseline, it might indicate that your users are having issues with call quality or reliability and are hanging up earlier than usual. If you start seeing extremely low average call duration, for example 15 seconds, callers might be hanging up because your service is not performing reliably.
+- **Average call duration** - Information about average call duration can help you monitor the quality of calls. The average duration of a 1:1 PSTN call is four to five minutes. However, for each company, this average can differ. Microsoft recommends establishing a baseline for the average call duration for your company. If this parameter goes significantly below the baseline, it might indicate that your users are having issues with call quality or reliability and are hanging up earlier than usual. If you start seeing extremely low average call duration, for example 15 seconds, callers might be hanging up because your service isn't performing reliably.
 
    Because the action you take might depend on the number of calls affected, Health Dashboard shows how many calls were analyzed to calculate a parameter.
 
 - **TLS connectivity status** - TLS (Transport Layer Security) connectivity shows the status of the TLS connections between Direct Routing and the SBC. Health Dashboard also analyzes the certificate expiration date and warns if a certificate is set to expire within 30 days so that administrators can renew the certificate before service is disrupted.
 
    By clicking the Warning message, you can see a detailed issue description in a popup window on the right and recommendations for how to fix the issue.
 
-- **SIP options status** – By default, the SBC sends options messages every minute. This configuration can vary for different SBC vendors. Direct Routing warns if the SIP options are not sent or are not configured. For more information about SIP options monitoring, and conditions when an SBC can be marked as not functional, see [Monitor and troubleshoot Direct Routing](direct-routing-monitor-and-troubleshoot.md).
+- **SIP options status** – By default, the SBC sends options messages every minute. This configuration can vary for different SBC vendors. Direct Routing warns if the SIP options aren't sent or aren't configured. For more information about SIP options monitoring, and conditions when an SBC can be marked as not functional, see [Monitor and troubleshoot Direct Routing](direct-routing-monitor-and-troubleshoot.md).
 
-- **Detailed SIP options status** - In addition to showing that there is an issue with SIP options flow, the Health Dashboard also provides detailed descriptions of the errors. You can access the description by clicking the “Warning” message. A pop-up window on the right will show the detailed error description.
+- **Detailed SIP options status** - In addition to showing that there's an issue with SIP options flow, the Health Dashboard also provides detailed descriptions of the errors. You can access the description by clicking the “Warning” message. A pop-up window on the right shows the detailed error description.
 
    Possible values for SIP options status messages are as follows:
 
     - Active – The SBC is active--Microsoft Direct Routing service sees the options flowing on a regular interval.
 
-    - Warning, no SIP options - The Session Border Controller exists in the database (your administrator created it using the command New-CsOnlinePSTNGateway). It is configured to send SIP options, but the Direct Routing service never saw the SIP options coming back from this SBC.
+    - Warning, no SIP options - The Session Border Controller exists in the database (your administrator created it using the command New-CsOnlinePSTNGateway). It's configured to send SIP options, but the Direct Routing service never saw the SIP options coming back from this SBC.
 
     - Warning, SIP Messages aren't configured - Trunk monitoring using SIP options isn’t turned on. Microsoft Calling System uses SIP options and Transport Layer Security (TLS) handshake monitoring to detect the health of the connected Session Border Controllers (SBCs) at the application level. You’ll have problems if this trunk can be reached at the network level (by ping), but the certificate has expired or the SIP stack doesn’t work. To help identify such problems early, Microsoft recommends enabling sending SIP options. Check your SBC manufacturer documentation to configure sending SIP options.
 
-- **Concurrent calls capacity** - You can specify the limit of concurrent calls that an SBC can handle by using the New- or Set-CsOnlinePSTNGateway command with the -MaxConcurrentSessions parameter. This parameter calculates how many calls were sent or received by Direct Routing using a specific SBC and compares it with the limit set. Note:  If the SBC also handles calls to different PBXs, this number will not show the actual concurrent calls.
+- **Concurrent calls capacity** - You can specify the limit of concurrent calls that an SBC can handle by using the New- or Set-CsOnlinePSTNGateway command with the -MaxConcurrentSessions parameter. This parameter calculates how many calls were sent or received by Direct Routing using a specific SBC and compares it with the limit set. Note:  If the SBC also handles calls to different PBXs, this number won't show the actual concurrent calls.
 
 ## Detailed information for each SBC
 
@@ -100,7 +100,7 @@ The detailed view shows the following additional parameters:
 
    - Jitter – Is the millisecond measure of variation in network propagation delay time computed between two endpoints using RTCP (The RTP Control Protocol).
 
-   - Packet Loss – Is a measure of packet that failed to arrive; it is computed between two endpoints.
+   - Packet Loss – Is a measure of packet that failed to arrive; it's computed between two endpoints.
 
    - Latency - (Also known as round trip time) is the length of time it takes for a signal to be sent plus the length of time it takes for the acknowledgment of that signal to be received. This time delay consists of the propagation times between the two points of a signal.