Routing Script Tutorial: Custom User Context: Difference between revisions
(Created page with "{{DISPLAYTITLE:Custom User Context}} The routing script can'''save per-call information within the call context''', and it can be available if routing is called again later during the call flow. Cases where routing is called multiple times for the same call are: - Call transfer requests - SIP redirect requests - Radius Authorization result - Announcement server with digit collection The routing script can save a recursive hash of attributes here: params[:user_contex...") |
No edit summary |
||
| Line 19: | Line 19: | ||
Note: This feature is available starting from release 2.9.85, 2.10.31 and 3.0.15 (in respective branches 2.9, 2.10 or 3.0) | Note: This feature is available starting from release 2.9.85, 2.10.31 and 3.0.15 (in respective branches 2.9, 2.10 or 3.0) | ||
[[Image:BackToMain.png|thumb|center|400px|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]] | |||
Latest revision as of 11:27, 3 April 2024
The routing script cansave per-call information within the call context, and it can be available if routing is called again later during the call flow.
Cases where routing is called multiple times for the same call are: - Call transfer requests - SIP redirect requests - Radius Authorization result - Announcement server with digit collection
The routing script can save a recursive hash of attributes here:
params[:user_context]
For example
params[:user_context] = { "SomeKey" => "Some value I want to retrieve upon next routing for this call", "OtherVal" => { "subkey" => "subval" } }
Upon first call to routing script, params[:user_context] will be nil. Upon subsequent calls to routing script, it will contain whatever the script had stored upon previous call (or nil if it was not set)
Note: This feature is available starting from release 2.9.85, 2.10.31 and 3.0.15 (in respective branches 2.9, 2.10 or 3.0)
