Use Cases:SIP Redirect to SIP: Difference between revisions
(Updated redirect file) |
No edit summary |
||
Line 18: | Line 18: | ||
|- | |- | ||
| | | | ||
*[[Toolpack:Call_Routes_Settings_B#Routing_Script|Configure Routing scripts]]. | *[[Toolpack:Call_Routes_Settings_B#Routing_Script|Configure Routing scripts]]. | ||
**'''Routing Scripts''' -> Import Script File | **'''Routing Scripts''' -> Import Script File | ||
***'''File'''-> redirect_routing.rb | ***'''File'''-> [[Media:Redirect_routing.rb.zip|redirect_routing.rb]] | ||
***'''ScriptType'''-> Customer | ***'''ScriptType'''-> Customer | ||
***'''Load on startup''' -> unchecked | ***'''Load on startup''' -> unchecked |
Revision as of 16:29, 22 October 2018
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 -> Allow Recurse [unchecked] Profiles -> Edit Reason Cause Mapping -> 302 Moved temporarily-> Route retry action -> Process Call Routing gateway -> use Script -> Routing Scripts