Redirect
From TBwiki
(Difference between revisions)
(Added direct link to redirect configuration) |
(rebrand) |
||
| (One intermediate revision by one user not shown) | |||
| Line 15: | Line 15: | ||
== TelcoBridges and redirections == | == TelcoBridges and redirections == | ||
| − | [[Web_Portal_Tutorial_Guide_v2.7| | + | [[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| | + | [[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>: [[ | + | *<u>Redirection emission</u>: [[Tctrl]] can forge a redirection response instead of routing an incoming call using routing scripts. |
| − | *<u>Redirection processing</u>: [[ | + | *<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>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. | *<u>Drop</u>: The unit can also be configured to drop the request altogether. | ||
| Line 25: | Line 25: | ||
== Configuration == | == Configuration == | ||
*[[Use_Cases:Redirect_Configuration_A|Redirect configuration]] | *[[Use_Cases:Redirect_Configuration_A|Redirect configuration]] | ||
| − | |||
| − | |||
Latest revision as of 09:20, 9 September 2016
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
Tctrl 2.7 and earlier provides basic support for SIP redirection on the NAP from where the outgoing call originated.
Tctrl 2.8 and later provides support for various redirection behaviors on signaling protocols that support it. These behaviors are:
- Redirection emission: Tctrl can forge a redirection response instead of routing an incoming call using routing scripts.
- Redirection processing: Tctrl 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.
