Routing Script Tutorial: Call Diversion Options: Difference between revisions
(Created page with "{{DISPLAYTITLE:Call Diversion Options}} It's possible to control the call flow when a call diversion information is received in the alerting state. Two fields are available: bridge[ :diversion ] and bridge[ :diversion_reason ] The internal release cause TOOLPACK_DIVERT_NOT_ALLOWED is used by gateway application to terminate both legs. bridge[ :diversion ] = :allowed The alert message will not be analyzed and the call will be progressed. Default behavior. bridge[...") |
No edit summary |
||
| Line 21: | Line 21: | ||
If the diversion is not allowed, the redirecting reason will be analyzed and the call will only be dropped for the configured cases. | If the diversion is not allowed, the redirecting reason will be analyzed and the call will only be dropped for the configured cases. | ||
See | See [[Routing_script_tutorial:Mini_Development_Guide#Redirecting_number,_Original_Called_Number_and_Diversion_Reason|Redirecting number reason values]]. | ||
[[Image:BackToMain.png|thumb|center|400px|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]] | |||
Latest revision as of 11:24, 3 April 2024
It's possible to control the call flow when a call diversion information is received in the alerting state.
Two fields are available: bridge[ :diversion ] and bridge[ :diversion_reason ]
The internal release cause TOOLPACK_DIVERT_NOT_ALLOWED is used by gateway application to terminate both legs.
bridge[ :diversion ] = :allowed
The alert message will not be analyzed and the call will be progressed. Default behavior.
bridge[ :diversion ] = :not_allowed
If the alert message indicates that the call is diverted, the call will be released no matter the In-band information to allow early media.
bridge[ :diversion ] = :not_allowed_w_early_media
The call will be released If the alert message indicates that the call is diverted with in-band information to allow early media.
bridge[ :diversion_reason ] = "*"
If the diversion is not allowed, the gateway will drop the call for any redirecting reason.
bridge[ :diversion_reason ] = "0,1,2"
or
bridge[ :diversion_reason ] = "unknown,busy,no_reply"
If the diversion is not allowed, the redirecting reason will be analyzed and the call will only be dropped for the configured cases.
See Redirecting number reason values.
