Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update direct-routing-plan.md #10851

Merged
merged 3 commits into from
Aug 16, 2024
Merged

Update direct-routing-plan.md #10851

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2e39acd
Update direct-routing-plan.md
teddygyabaah Aug 16, 2024
405eea1
Update direct-routing-plan.md
CarolynRowe Aug 16, 2024
617a7ef
Merge branch 'public' into patch-21
CarolynRowe Aug 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Teams/direct-routing-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -354,7 +354,7 @@ Applies to non-media bypass case only. With media bypass, the media flows direct
On the leg between the Cloud media processor and the Teams client, either SILK or G.722 is used. The codec choice on this leg is based on Microsoft algorithms, which take into consideration multiple parameters.

> [!NOTE]
> Media re-targeting isn't supported. During a Direct Routing call, if the SBC sends a new media IP to Direct Routing, although it's negotiated in the SIP signaling, the media is never sent to the new IP address from Direct Routing.
> Media re-targeting isn't supported. During a call, if Direct Routing SBC SIP re-Invite (Offer) contains a new media IP address, port, or transport, media isn't sent from PSTN Hub to the new target. Per RFC 3264 8.3.1, media re-target support is optional (not required).

## Supported Session Border Controllers (SBCs)

Expand Down