From cb371342ea832f1e7efd2f38933e0034c200302f Mon Sep 17 00:00:00 2001
From: FilippSe <56016131+FilippSe@users.noreply.github.com>
Date: Mon, 20 Jan 2025 15:20:38 +0200
Subject: [PATCH] Updated sections related to SBC behavior during transfer.

Updated sections related to SBC behavior during transfer.
---
 Teams/direct-routing-protocols-sip.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Teams/direct-routing-protocols-sip.md b/Teams/direct-routing-protocols-sip.md
index 0a093b4de5..2e474d4520 100644
--- a/Teams/direct-routing-protocols-sip.md
+++ b/Teams/direct-routing-protocols-sip.md
@@ -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.