Skip to content

Commit 5b2dd5e

Browse files
committed
Add link to Mobile Control Point description
1 parent cebcda7 commit 5b2dd5e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communications-gateway/interoperability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Your core mobile network must supply this information to Azure Communications Ga
5151

5252
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.
5353

54-
- Deploying Metaswitch Mobile Control Point (MCP). 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.
54+
- Deploying Metaswitch Mobile Control Point (MCP). 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 the [Metaswitch description of Mobile Control Point](https://www.metaswitch.com/products/mobile-control-point).
5555
- 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.
5656

5757
> [!IMPORTANT]

0 commit comments

Comments
 (0)