Actions

Toolpack:Call Routes Settings E: Difference between revisions

No edit summary
No edit summary
Line 58: Line 58:
* '''The routeset definition and digimap files are created.'''
* '''The routeset definition and digimap files are created.'''


{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Add label routing functionality
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Add label routing functionality
Line 72: Line 70:
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}
|}
|STYLE="vertical-align: top"|
 
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Update definition/digitmap files
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Update definition/digitmap files
Line 81: Line 79:
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}
|}
|}


=RADIUS Authorization and Authentication=
=RADIUS Authorization and Authentication=
{|
 
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="240" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization
! width="240" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization
Line 97: Line 93:
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}
|STYLE="vertical-align: top"|
 
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="300" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization (with custom dictionary)
! width="300" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization (with custom dictionary)

Revision as of 15:03, 13 December 2021



[edit]

TelcoBridges provides a wide variety of routing script examples, from which customers can apply directly in their web configuration, according to their needs, by following a few simple steps. Select one of the following examples according to your needs. You may modify it when necessary.

*Flexible NOA: Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.

*Prefix NOA: Remapp Calling/Called NOA according to the prefix of the calling/called number, manipulate calling/called number. For calling number, if it is a privacy call, use the number in P-Asserted-Identity line or Remote-Party-ID line as the calling number to remap the NOA and do the manipulation.


Flexible NOA Prefix NOA


Audio Prompts

Audio Prompts


[edit]

This section assumes:

  • The routing script is already implemented (you just need to add the label routing functionality)
  • The routeset definition and digimap files are created.
Add label routing functionality
Update definition/digitmap files

Return to Web Portal 3.2 Home Page