Redirect - Revision history

Cbilodeau: rebrand

2016-09-09T14:20:19Z

rebrand

Lucas Trottier: /* Configuration */

2016-05-19T13:39:47Z

Configuration

Luc Morissette: Added direct link to redirect configuration

2016-01-28T08:47:42Z

Added direct link to redirect configuration

Atremblay: Fixed link for LNP

2015-04-28T17:37:16Z

Fixed link for LNP

Atremblay: Initial version

2015-04-28T17:34:35Z

Initial version

New page

Some signaling protocols support redirecting calls from one location to another. This is usually done by a redirect server which analyzes incoming call information and then terminates the call while specifying another destination.

Redirections are usually triggered by the following call termination reason codes:
* SIP
** 300 Multiple Choices
** 301 Moved Permanently
** 302 Moved Temporarily
** 305 Use Proxy
** 380 Alternative Service
* SS7
** Q.850 Ported Number (14)
** Q.850 Number Changed (22)
** Q.850 Redirection (23)

== TelcoBridges and redirections ==

[[Web_Portal_Tutorial_Guide_v2.7|TMG-CONTROL 2.7]] and earlier provides basic support for SIP redirection on the NAP from where the outgoing call originated.

[[Web_Portal_Tutorial_Guide_v2.8|TMG-CONTROL 2.8]] and later provides support for various redirection behaviors on signaling protocols that support it. These behaviors are:
*Redirection emission: [[TMG-CONTROL]] can forge a redirection response instead of routing an incoming call using routing scripts.
*Redirection processing: [[TMG-CONTROL]] can process redirection requests through its routing scripts using the specified called or routing numbers. This feature can be used for [[LNP]] "dipping".
*Relay: The [[Tmedia]] or [[Tdev]] unit can be configured automatically relay redirection requests from the outgoing call to the incoming call.
*Drop: The unit can also be configured to drop the request altogether.

== Configuration ==

*[[Web_Portal_Tutorial_Guide_v2.8|Toolpack v2.8]]

@@ Line 15: / Line 15: @@
 == TelcoBridges and redirections ==
-[[Web_Portal_Tutorial_Guide_v2.7|TMG-CONTROL 2.7]] and earlier provides basic support for SIP redirection on the NAP from where the outgoing call originated.
+[[Web_Portal_Tutorial_Guide_v2.7|Tctrl 2.7]] and earlier provides basic support for SIP redirection on the NAP from where the outgoing call originated.
-[[Web_Portal_Tutorial_Guide_v2.8|TMG-CONTROL 2.8]] and later provides support for various redirection behaviors on signaling protocols that support it. These behaviors are:
+[[Web_Portal_Tutorial_Guide_v2.8|Tctrl 2.8]] and later provides support for various redirection behaviors on signaling protocols that support it. These behaviors are:
-*<u>Redirection emission</u>: [[TMG-CONTROL]] can forge a redirection response instead of routing an incoming call using routing scripts.
+*<u>Redirection emission</u>: [[Tctrl]] can forge a redirection response instead of routing an incoming call using routing scripts.
-*<u>Redirection processing</u>: [[TMG-CONTROL]] can process redirection requests through its routing scripts using the specified called or routing numbers. This feature can be used for [[Local Number Portability|LNP]] "dipping".
+*<u>Redirection processing</u>: [[Tctrl]] can process redirection requests through its routing scripts using the specified called or routing numbers. This feature can be used for [[Local Number Portability|LNP]] "dipping".
 *<u>Relay</u>: The [[Tmedia]] or [[Tdev]] unit can be configured automatically relay redirection requests from the outgoing call to the incoming call.
 *<u>Drop</u>: The unit can also be configured to drop the request altogether.

← Older revision		Revision as of 13:39, 19 May 2016
Line 25:		Line 25:
	== Configuration ==		== Configuration ==
	*[[Use_Cases:Redirect_Configuration_A\|Redirect configuration]]		*[[Use_Cases:Redirect_Configuration_A\|Redirect configuration]]
−	*[[Web_Portal_Tutorial_Guide_v2.9\|Toolpack v2.9]]
−	*[[Web_Portal_Tutorial_Guide_v2.8\|Toolpack v2.8]]

@@ Line 19: / Line 19: @@
 [[Web_Portal_Tutorial_Guide_v2.8|TMG-CONTROL 2.8]] and later provides support for various redirection behaviors on signaling protocols that support it. These behaviors are:
 *<u>Redirection emission</u>: [[TMG-CONTROL]] can forge a redirection response instead of routing an incoming call using routing scripts.
-*<u>Redirection processing</u>: [[TMG-CONTROL]] can process redirection requests through its routing scripts using the specified called or routing numbers. This feature can be used for [[LNP]] "dipping".
+*<u>Redirection processing</u>: [[TMG-CONTROL]] can process redirection requests through its routing scripts using the specified called or routing numbers. This feature can be used for [[Local Number Portability|LNP]] "dipping".
 *<u>Relay</u>: The [[Tmedia]] or [[Tdev]] unit can be configured automatically relay redirection requests from the outgoing call to the incoming call.
 *<u>Drop</u>: The unit can also be configured to drop the request altogether.

@@ Line 24: / Line 24: @@
 == Configuration ==
+*[[Use_Cases:Redirect_Configuration_A|Redirect configuration]]
 *[[Web_Portal_Tutorial_Guide_v2.8|Toolpack v2.8]]