Process redirection to other SIP endpoints
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 |
In NAP Columns, set the following:
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) |
When you Configure Routes, set the following:
|
These settings are set by default, but may be verified if some changes were made in the default configuration:
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 -> default_routing_script