Routing Using Redirect Server

6. Advanced Routing Advanced Routing
1

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:

  • 300 Multiple Choices

  • 301 Moved Permanently

  • 302 Moved Temporarily

  • 305 Use Proxy

  • 380 Alternative Service

FreeSBC provides support for various redirection behaviors on signaling protocols that support it.
Please check followink link for configuration of Redirect on FreeSBC; https://docs.telcobridges.com/tbwiki/Use_Cases:SIP_Redirect_to_SIP

2

Is this redirect feature still working on 3.1.27? In our test, FreeSBC relays 302 back to the source device. We have double checked SIP->Header Parameters->Use legacy redirection mode(disabled) and Profiles->Reason Cause Mapping->302->Route retry action(Process call routing).

Thanks,

3

Hi

Redirect feature still works for all of our releases and products. Would you send an email to support@telcobridges.com with more details to get a solution please?

4

Sure. I will contact support at telcobridges for this issue.

Thanks,