Skip to content

Commit 671bc90

Browse files
committed
2025_01 - Fix monthly broken links - GemmaWakeford
1 parent ba34375 commit 671bc90

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communications-gateway/interoperability-operator-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Your core mobile network must supply this information to Azure Communications Ga
4444
Your core mobile network must also be able to anchor and divert calls into the Microsoft Phone System. You can choose from the following options.
4545

4646
- Using Mobile Control Point (MCP) in Azure Communications Gateway. MCP is an IMS Application Server that queries the Teams Phone Mobile Consultation API to determine whether the call involves a Teams Phone Mobile Subscriber. MCP then adds X-MS-FMC headers and updates the signaling to divert the call into the Microsoft Phone System through Azure Communications Gateway. For more information, see [Mobile Control Point in Azure Communications Gateway for Teams Phone Mobile](mobile-control-point.md).
47-
- Deploying an on-premises version of Mobile Control Point (MCP) from Metaswitch. For more information, see the [Metaswitch description of Mobile Control Point](https://www.metaswitch.com/products/mobile-control-point). This version of MCP isn't included in Azure Communications Gateway.
47+
- Deploying an on-premises version of Mobile Control Point (MCP) from Metaswitch. For more information, see the [Metaswitch description of Mobile Control Point](https://info.metaswitch.com/hubfs/pdfs/MobileControlPoint_How%20it%20Works.pdf). This version of MCP isn't included in Azure Communications Gateway.
4848
- Using other routing capabilities in your core network to detect Teams Phone Mobile subscribers and route INVITEs to or from these subscribers into the Microsoft Phone System through Azure Communications Gateway.
4949

5050
> [!IMPORTANT]

0 commit comments

Comments
 (0)