Use Cases:SIP Redirect to SIP: Difference between revisions
No edit summary |
|||
Line 28: | Line 28: | ||
***In the main class: | ***In the main class: | ||
****include RedirectQuery | ****include RedirectQuery | ||
****before_filter method = redirect_query | ****before_filter :method => :redirect_query | ||
| | | | ||
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_D|Configure NAP]]. When you configure the NAPs, you need these: | *[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_D|Configure NAP]]. When you configure the NAPs, you need these: |
Revision as of 13:30, 21 May 2019
Applies to version(s): v2.8 and above
In this scenario, the incoming call is sent to a SIP redirect server, which returns a 3xx message and a new call is sent to the SIP contacts received.
This is the call flow of such a scenario. A 302 Moved temporarily is returned from the SIP redirect server and new calls are made to the SIP endpoints.
Configure Routing Scripts | Configure NAP | Configure NAP Colums | Configure Routes |
---|---|---|---|
|
You can add more SIP redirect server as needed
This will allow calls to be redirected to any IPs using this SIP transport Server |
Select REDIRECT for each NAP that is a SIP Redirect server and you can prioritize with group (lowest value is highest priority) and weight (to load balance) |
|
Also make sure these settings are applied:
SIP -> Header Parameters -> Use legacy redirection mode [unchecked] ( old naming convention was: Allow Recurse) Profiles -> Edit Reason Cause Mapping -> 302 Moved temporarily-> Route retry action -> Process Call Routing gateway -> use Script -> Routing Scripts