Parameter: Use RTP no-anchoring - Revision history

Abrassard at 16:36, 19 January 2018

2018-01-19T16:36:33Z

Abrassard: /* Will "RTP no-anchoring" always be used when enabled in a profile? */

2018-01-19T16:35:51Z

Will "RTP no-anchoring" always be used when enabled in a profile?

Abrassard: /* When will "RTP no-anchoring" be actually used? */

2018-01-19T16:34:44Z

When will "RTP no-anchoring" be actually used?

Abrassard at 16:29, 19 January 2018

2018-01-19T16:29:57Z

Abrassard at 21:52, 18 January 2018

2018-01-18T21:52:49Z

Abrassard: Created page with "The option "Use RTP no-anchoring" is possible only if the option Allow low-delay media relay is enabled first. RTP no-anchoring is a variant of low-delay media relay wher..."

2018-01-18T21:51:58Z

Created page with "The option "Use RTP no-anchoring" is possible only if the option Allow low-delay media relay is enabled first. RTP no-anchoring is a variant of low-delay media relay wher..."

New page

The option "Use RTP no-anchoring" is possible only if the option [[Allow low-delay media relay]] is enabled first.

RTP no-anchoring is a variant of low-delay media relay where the media is relayed directly between the two legs of a call, rather than going through the SBC unit.
This allows greatly reducing IP bandwidth toward the SBC, while still using the SBC for SIP signaling, routing, and other features.

RTP no-anchoring mode is possible within the same conditions that [[Allow low-delay media relay|allow low-delay media relay]].

'''Note''': Make sure to enable this option only on profiles used for calls that can reach each other directly. It may not work if calls are behind NATs, or on separate networks. We recommend to customize the call leg profiles per [[Tmedia_Routing|route]], and to be careful with which routes can use a profile with RTP no-anchoring is enabled.

[[Category: Parameters]]

@@ Line 1: / Line 1: @@
 ===What is "RTP no-anchoring?"===
-RTP no-anchoring is a variant of low-delay media relay where the RTP packets are not "anchored" to the SBC (not going through the SBC).
+RTP no-anchoring is a variant of [[Parameter: Allow low-delay media relay|low-delay media relay]] where the RTP packets are not "anchored" to the SBC (not going through the SBC).
 Instead the RTP path is established directly between the two legs of a call (which send RTP to each other).

@@ Line 19: / Line 19: @@
 *The call does not require IVR functionalities (play file, record to file, tone detection or tone generation).
-TelcoBridges SBCs can dynamically change, during a call, from no-anchoring mode, to transcoding (IVR) mode. Changing mode requires a SIP re-invite (to change the RTP path so it goes or not through the SBC)
+TelcoBridges SBCs can dynamically change, during a call, from no-anchoring mode, to transcoding (IVR) mode. When changing mode, a SIP re-invite is used on both call legs (to change the RTP path so it goes or not through the SBC)
 ===Synonyms of "RTP no-anchoring"===

@@ Line 12: / Line 12: @@
 We recommend to configure "no-anchoring" per [[Tmedia_Routing|route]] (each route may override the NAP's default [[Toolpack:Modify_Profile_Sbc_A|profile]]). Profiles with "RTP no-anchoring" enabled should only be used on routes that are known to bridge call legs that can directly send RTP to each other.
-===When will "RTP no-anchoring" be actually used?===
+===Will "RTP no-anchoring" always be used when enabled in a profile?===
-Enabling this option on a profile does not mean all calls using this profile will use "no-anchoring" mode.
+Not all calls with no-anchoring mode enabled will actually use it.
-In fact, RTP no-anchoring mode is possible if both call legs of a call have the "RTP no-anchoring" option enabled in their assigned [[Toolpack:Modify_Profile_Sbc_A|profile]]. If one of the call legs does not have this option, standard "low-delay" mode will be used (RTP will go through the SBC).
+In fact, RTP no-anchoring mode is possible if
-===Synonyms of "RTP no-anchoring"
+TelcoBridges SBCs can dynamically change, during a call, from no-anchoring mode, to transcoding (IVR) mode. Changing mode requires a SIP re-invite (to change the RTP path so it goes or not through the SBC)
 "RTP no-anchoring" is also sometimes called "Media no-anchoring", "Media pass-around" or "media bypass".
 [[Category: Parameters]]

@@ Line 1: / Line 1: @@
-The option "Use RTP no-anchoring" is possible only if the option [[Parameter: Allow low-delay media relay|Allow low-delay media relay]] is enabled first.
+===What is "RTP no-anchoring?"===
-RTP no-anchoring is a variant of low-delay media relay where the media is relayed directly between the two legs of a call, rather than going through the SBC unit.
+Instead the RTP path is established directly between the two legs of a call (which send RTP to each other).
-This allows greatly reducing IP bandwidth toward the SBC, while still using the SBC for SIP signaling, routing, and other features.
-RTP no-anchoring mode is possible within the same conditions than [[Parameter: Allow low-delay media relay|low-delay media relay]].
+This greatly reduces the IP bandwidth required by the SBC, while the SBC continues to be involved in SIP signaling and call routing.
-'''Note''': Make sure to enable this option only on profiles used for calls that can reach each other directly. It may not work if calls are behind NATs, or on separate networks. We recommend to customize the call leg profiles per [[Tmedia_Routing|route]], and to be careful with which routes can use a profile with RTP no-anchoring is enabled.
+===When should "RTP no-anchoring" be enabled?===
 [[Category: Parameters]]