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

Updated sections related to SBC behavior during transfer. #10918

Open
wants to merge 1 commit into
base: public
Choose a base branch
from
Open

Updated sections related to SBC behavior during transfer. #10918

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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-protocols-sip.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,7 +282,7 @@ This option assumes that the SIP proxy acts as a Transferor and sends a Refer me
- The call is transferred to an external PSTN participant.
- The call is transferred from one Teams user to another Teams user in the same tenant via the SBC.

If the call is transferred from one Teams user to another via the SBC, the SBC is expected to issue a new invite (start a new dialog) for the transfer target (the Teams user) using the information received in the Refer message.
When call transferred from a Teams user to another Teams user or PSTN number via SBC, the SBC is expected on receiving the Refer, issue a new invite (start a new dialog) for Transfer Target (which is a Teams User or PSTN number) towards the SIP Proxy, using the information, received in the Refer message.

To populate the To/Transferor fields for the transaction of the request internally, the SIP proxy needs to convey this information inside the REFER-TO/REFERRED-BY headers.

Expand Down
Loading