Redirect

From TBwiki
Revision as of 03:47, 28 January 2016 by Luc Morissette (Talk | contribs)
Jump to: navigation, search

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

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

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

Personal tools